squad-conventions

To enforce zero runtime dependencies, restrict your code to use only Node.js built-in modules instead of external packages. This convention ensures a lightweight, maintainable codebase with no installed dependency overhead.

To handle user-facing errors consistently, implement a dedicated `fatal()` function for critical failures. This pattern standardizes error messaging and exits the process cleanly without throwing uncaught exceptions.

You can and should use the Node.js built-in test runner for CLI tool development. Mandating this built-in runner eliminates external testing dependencies, aligning with a zero-dependency project convention.

The best way to structure files for a Node.js CLI using built-in modules is to adhere to a standardized project layout. Following a defined file structure convention ensures seamless integration and maintains Windows compatibility.

You do not need external testing frameworks to run tests for a zero-dependency Node.js CLI. Conventions mandate using the Node.js built-in test runner, ensuring the testing environment remains lightweight and dependency-free.

Your Node.js CLI code needs to follow Windows compatibility standards to ensure cross-platform functionality. Enforcing specific file structure and compatibility rules prevents platform-specific path and execution errors.