squad-conventions

Standardize Node.js CLI project conventions by enforcing zero-dependency rules, path-safe operations with path.join, and idempotent initialization to reduce ambiguity and onboarding friction.

Zero-dependency rules for Node.js command-line tools require all tooling to rely exclusively on Node.js built-ins, simplifying setup and reducing risk across Squad projects.

Ensure cross-platform compatibility for Windows in Node.js CLI development by applying path-safe operations via path.join and following explicit compatibility checks defined in standard conventions.

Yes, you can apply Squad conventions to existing Node.js projects to guide code structure, testing practices, and error handling while enforcing zero-dependency rules and documenting anti-patterns.

The best way to document anti-patterns in a Node.js CLI codebase is to enforce explicit anti-pattern documentation within standard conventions, providing a single source of truth for new contributors.

You need idempotent initialization for command-line tools to ensure predictable, maintainable code structure and prevent duplicate side effects when setting up Squad projects.