squad-conventions

Enforce Squad CLI conventions for zero-dependency, safe file operations, and error handling.

9|1|Updated Jul 21, 2025

Search Tags:#cli #cross-platform #conventions #error-handling #nodejs #squad #zero-dependencies

Ready to run

npx skills add https://github.com/usepowershell/PoshMcp --skill squad-conventions-usepowershell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill squad-conventions-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad conventions prevent accidental regressions, platform incompatibilities, and unsafe user-facing behavior by prescribing patterns for zero-dependency design, error handling, and file management across the create-squad CLI codebase.

Core Features & Use Cases

Zero-dependency enforcement: Ensures runtime relies only on Node.js built-ins and flags any new external runtime dependencies.
Safe error and UX patterns: Standardizes the fatal() pattern for user-facing errors, ANSI color constants, and suppression of raw stack traces.
Cross-platform and init safety: Validates use of path.join for Windows compatibility, idempotent init/upgrade behavior, and safe recursive copy semantics for templates and team state.

Quick Start

Use the squad-conventions skill to audit proposed CLI changes and report any violations of Squad's zero-dependency, file-structure, and error-handling conventions.

Frequently Asked Questions about squad-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce zero-dependency constraints in a Node.js CLI?▼

Enforce zero-dependency constraints in a Node.js CLI by auditing code changes to ensure runtime relies exclusively on Node.js built-ins, preventing any new external runtime dependencies from being introduced into the package.

What is the best way to handle fatal CLI errors without exposing stack traces?▼

Handle fatal CLI errors safely by standardizing the fatal() pattern for user-facing errors, applying ANSI color constants, and suppressing raw stack traces to prevent unsafe or confusing output for CLI users.

How do I ensure cross-platform path compatibility in a Node.js CLI?▼

Ensure cross-platform path compatibility in a Node.js CLI by validating the consistent use of path.join for file operations, which prevents platform incompatibilities and ensures safe execution on Windows environments.

How do I make CLI initialization and upgrade flows idempotent?▼

Make CLI initialization and upgrade flows idempotent by validating that init and upgrade behaviors can be run repeatedly without causing duplicate files or corrupting existing team state, ensuring safe recursive copy semantics.

Does the squad-conventions skill work for CI and pull request reviews?▼

Yes, the squad-conventions skill works for CI and pull request reviews by applying its validation rules to evaluate proposed changes to templates, agents, and team state, preventing accidental regressions in the codebase.