squad-conventions

To handle fatal errors without external dependencies, implement a standardized `fatal()` pattern for all user-facing errors. This convention ensures consistent error reporting across the Squad CLI while maintaining a zero runtime dependency rule by using Node.js built-ins only.

Best practices for structuring a cross-platform Node.js CLI tool include enforcing zero runtime dependencies, using the Node.js built-in test runner, and ensuring Windows compatibility. Adhering to specific file structures and idempotent initialization ensures project consistency and maintainability.

No, you do not need external testing frameworks for Node.js CLI development. The Squad CLI conventions enforce using the Node.js built-in test runner exclusively, eliminating the need for external dependencies and preventing package bloat while maintaining standardized testing.

To standardize CLI output formatting using only Node.js built-ins, apply specific ANSI color constants defined in the project conventions. This approach enforces the zero-dependency rule while providing consistent terminal styling across Windows, macOS, and Linux environments.

Node.js CLI initialization fails on subsequent runs if the process is not idempotent. Following Squad CLI conventions, initialization must be designed to be idempotent, ensuring repeated executions produce consistent results without causing errors or duplicating file structures.