Documents coding conventions and patterns for the Squad CLI codebase.
npx skills add https://github.com/codebytes/btt --skill squad-conventions-codebytes
Please help me install this Agent Skill. Skill: squad-conventions Source: https://github.com/codebytes/btt/tree/main/.copilot/skills/squad-conventions Command: npx skills add https://github.com/codebytes/btt --skill squad-conventions-codebytes
fs, path, os, child_process) with no npm dependencies. - Error Handling & Testing Patterns: Defines the fatal() error pattern, ANSI color constants, and the node:test built-in test runner conventions. - File Structure & Init Semantics: Explains the .squad/ directory ownership model, skip-if-exists init idempotency, and upgrade overwrite rules. - Use Case: Before editing index.js or adding a feature to the create-squad package, load this Skill to ensure your changes use path.join(), avoid new dependencies, and route errors through fatal(). ## Quick Start Review the Squad codebase conventions before modifying any source file in the create-squad package.High-intent search queries and answers about installing and using this skill.
All user-facing errors go through the fatal(msg) function, which prints a red ✗ prefix and exits with code 1. Never throw unhandled exceptions or print raw stack traces; a global uncaughtException handler calls fatal() as a safety net.
No. Squad is a zero-dependency package and this is a hard constraint, not a preference. Everything must use Node.js built-ins like fs, path, os, and child_process, and nothing may be added to dependencies in package.json.
Squad uses the Node.js built-in test runner with node:test and node:assert/strict, with no external test frameworks. Tests live in the test/ directory and run via npm test, which executes node --test test/.
Yes, Squad must work on Windows, macOS, and Linux. Always use path.join() for file paths and never hardcode forward or backward slash separators. All tests must pass on every platform.
The init flow uses a skip-if-exists pattern to guarantee idempotency and never overwrite user-owned state like .squad/ content. Only the upgrade flow overwrites files, and only Squad-owned ones such as templates and the coordinator prompt.
CommunityToolkitRun local squad sessions to validate template changes and capture evidence.
Agent-ClubhouseBuild a plugin and install it into the local Clubhouse plugins directory.
aram-devdocsDispatch five parallel agents to analyze pending code changes for security, performance, and architecture issues.
jonnymuirEnforce zero-dependency and fatal error handling standards for Squad CLI code.