squad-conventions

Document zero-dependency conventions for Squad CLI development patterns.

2|1|Updated Mar 25, 2026

Search Tags:#cli #patterns #conventions #nodejs #coding-standards #squad #zero-dependency

Ready to run

npx skills add https://github.com/PlagueHO/plagueho.learn --skill squad-conventions-plagueho

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes coding and project-convention practices across the Squad codebase to reduce onboarding time and prevent drift.

Core Features & Use Cases

Zero-dependency guidelines keep Squad tooling lightweight and portable.
Patterns for error handling, file structure, and ANSI color constants ensure consistent CLI behavior.
Use Case: When starting a new Squad project, teams follow this guide to align templates, tests, and contributor experience.

Quick Start

Follow these conventions when creating or updating Squad tooling to ensure consistency and maintainability.

Frequently Asked Questions about squad-conventions

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

FAQPage Schema

What are zero-dependency coding conventions for Node.js CLI projects?▼

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.

How do I structure a .squad directory for CLI tool templates and skills?▼

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.

How does error handling with fatal() work in Node.js CLI tools?▼

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.

When should I use built-in test runners instead of external frameworks?▼

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.

Do I need ANSI color constants for CLI development in Squad 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.

Can I use external libraries in Squad CLI tooling without breaking conventions?▼

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.