squad-conventions

You can enforce consistent coding standards by codifying unified Squad conventions for error handling, file operations, and repository structure across your Node.js codebases. This ensures predictable behavior and maintainability across Windows and Unix environments with zero runtime dependencies.

The best way to handle CLI errors with zero dependencies is using a standardized fatal() pattern for user-facing errors. This approach relies only on Node.js built-ins to provide clean failure modes and predictable behavior across your team's tooling.

You prevent file overwrites by implementing init idempotency and following specific copy pattern guidance for safe file operations. This ensures setup and upgrade processes avoid overwriting existing user state and maintain safe, idempotent behavior.

No, this Squad conventions skill has a zero-dependency design and requires no external runtime packages. It relies exclusively on Node.js built-ins, allowing you to bootstrap projects and maintain tooling without managing additional external dependencies.

You avoid platform-specific path bugs by using robust path handling via path.join and enforcing Windows compatibility conventions. This ensures safe, predictable file operations across both Windows and Unix environments within your Node.js codebase.

You should avoid unsafe file operations, non-idempotent setup scripts, and introducing external runtime dependencies. The skill provides anti-pattern warnings and governance to prevent these unsafe changes and maintain reliable, standardized repository structures.