squad-conventions

Enforce zero-dependency conventions by mandating every routine uses Node.js built-in modules exclusively, avoiding external runtime dependencies. This ensures predictable execution and maintainability across the Squad codebase.

Windows-safe file path handling requires using path.join() for all path construction to ensure cross-platform compatibility. This prevents path resolution errors when moving code between Windows and Unix-based environments.

Safe error handling for Node.js CLI applications is implemented using a standardized fatal() reporting function. This provides consistent guardrails for failures and uniform color-coded UX feedback during execution.

Node.js built-in tooling fully supports CLI development without external dependencies by leveraging built-in modules for file management, recursive copy, and directory creation. The Squad conventions prescribe this zero-dependency approach for all CLI tasks.

Project init overwrites happen when idempotency controls are missing. The Squad conventions implement skip-existing behavior during initialization and controlled overwrites specifically for Squad-owned files to prevent data loss.

A specific folder structure is required for Node.js CLI skill definitions. The conventions prescribe using a .squad/ directory for state, templates/ for templates, and *.skill*/ folders to organize all skill definitions.