squad-conventions

Coding standards for a zero-dependency Node.js CLI require using only Node.js built-in modules, avoiding external runtime packages, and following explicit patterns for error handling and project structure to ensure maintainability.

Handle cross-platform file paths in a Node.js CLI by using Windows-safe path handling techniques and idempotent initialization flows, ensuring the tooling operates consistently across multi-OS environments without drift.

You need standardized conventions for CLI project structure and error handling to establish a single source of truth for tooling maintenance, reducing onboarding time and preventing configuration drift across multiple projects.

You cannot use external npm packages for runtime operations when developing Squad CLI tooling because the conventions enforce a zero-dependency rule, restricting development to Node.js built-in modules only.

The best way to standardize initialization and upgrade flows for CLI dev tooling is to implement idempotent processes that apply explicit patterns for file structure and initialization, ensuring consistent cross-platform behavior.