squad-conventions

Use a standardized `fatal()` function to handle user-facing errors in your Node.js CLI. This convention ensures consistent error reporting while maintaining a zero-dependency codebase by relying strictly on Node.js built-ins.

Write tests for your Node.js CLI using the built-in Node.js test runner. This convention enforces zero external dependencies by standardizing on the native test runner for all testing requirements within the project.

The best code standards for a zero-dependency Node.js CLI include enforcing native built-ins, standardizing error handling with `fatal()`, ensuring Windows compatibility, and maintaining initialization idempotency for AI agent team integrations.

No, the Squad CLI conventions strictly enforce a zero-dependency policy. You must use only Node.js built-ins for implementation and testing, preventing any external package bloat during setup or development.

Structure files according to the documented conventions and maintain initialization idempotency to ensure safe, repeated executions. This approach guarantees maintainable AI agent team integrations within the Node.js CLI environment.

Your Node.js CLI needs Windows compatibility to ensure cross-platform execution and maintainable AI agent team integrations. The conventions mandate this compatibility alongside initialization idempotency for consistent behavior.