squad-conventions

To enforce zero-dependency coding conventions, restrict your Node.js application to built-in modules only, avoiding external package dependencies. This approach ensures a consistent, secure, and lightweight environment for CLI tool development.

The best way to standardize error handling in Node.js CLI applications is by using a standardized fatal() function. This ensures user-friendly error messages and maintains system stability across the codebase.

Yes, you can use the Node.js test runner without adding external dependencies by utilizing node:test and node:assert/strict. This provides a straightforward testing environment while maintaining zero-dependency operation.

Yes, the Squad coding conventions ensure cross-platform compatibility across Windows, macOS, and Linux. The established patterns and file structure are designed to operate predictably across all supported operating systems.

When maintaining a zero-dependency Node.js codebase, avoid anti-patterns such as adding npm dependencies and overwriting user state during initialization. The established conventions specifically list these patterns to prevent codebase maintenance issues.

You can recursively copy files and directories without external packages by following the robust copy pattern defined in these coding conventions. This pattern leverages Node.js built-ins to ensure safe and predictable file operations.