squad-conventions

Enforce zero-dependency rules in a Node.js CLI project by codifying standards to use Node.js built-ins only and validating changes to prevent accidental npm runtime dependency additions before pull requests.

Ensure Windows-safe path construction in Node.js by using path.join() for all file operations, which prevents cross-platform breakage caused by hardcoded path separators in CLI development.

The fatal() error pattern works for Node.js CLI user-facing errors by standardizing error handling alongside ANSI color constants, ensuring consistent formatting and safe exits across CLI operations.

Yes, you can use node:test to verify idempotent init behavior in a Node.js CLI by writing tests that validate init and upgrade flows run safely without duplicating files or state across multiple executions.

Node.js CLI tests fail when checking project conventions if changes violate zero-dependency rules, use hardcoded path separators instead of path.join(), or skip the required fatal() error pattern.

No, you do not need external testing dependencies to validate Squad CLI conventions because the standards prescribe using node:test as the test runner and Node.js built-ins to maintain zero runtime dependencies.