squad-conventions

Zero-dependency coding conventions for Node.js CLI projects require using only built-in modules to keep tooling lightweight and portable, avoiding external packages to reduce bloat and maintenance overhead in development.

To structure a .squad directory for CLI tool templates and skills, follow file structure conventions that organize templates and skill storage logically, supporting onboarding and maintenance across Squad projects.

Error handling with fatal() in Node.js CLI tools works by providing a standardized way to terminate execution and display critical errors, ensuring consistent CLI behavior across all Squad tooling environments.

You should use built-in test runners instead of external frameworks when adhering to zero-dependency guidelines, keeping Node.js CLI tooling lightweight and portable while maintaining consistent coding standards across projects.

You need ANSI color constants for CLI development in Squad projects to ensure consistent terminal output formatting and CLI behavior, standardizing the user experience across all Squad tooling interfaces.

No, you cannot use external libraries in Squad CLI tooling without breaking zero-dependency conventions, which require relying solely on built-in Node.js modules to maintain portability and reduce onboarding drift.