squad-conventions

Enforce standard conventions for Squad CLI tooling projects.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/londospark/citrust --skill squad-conventions-londospark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/londospark/citrust/tree/main/.squad-templates/skills/squad-conventions
Command: npx skills add https://github.com/londospark/citrust --skill squad-conventions-londospark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad conventions provide a single source of truth for patterns and best practices, reducing drift and onboarding time for contributors across Squad CLI tooling.

Core Features & Use Cases

  • Establishes zero-dependency patterns and Node.js built-ins usage to simplify maintenance.
  • Documents error handling, color constants, file structure, and cross-platform considerations to avoid drift across projects.
  • Use Case: A contributor can reference these conventions before implementing new Squad CLI features to ensure alignment with project standards.

Quick Start

Consult these conventions before starting any Squad CLI work to ensure consistency.

Frequently Asked Questions about squad-conventions

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

FAQPage Schema
What are Node.js CLI coding standards for maintaining zero dependencies?

Node.js CLI coding standards for zero dependencies require using built-in modules exclusively to simplify maintenance. This approach enforces consistent patterns across CLI tooling, reducing drift and onboarding time for contributors.

How do I structure SKILL.md YAML frontmatter and content sections?

To structure SKILL.md content, include YAML frontmatter with name and description fields, followed by problem statements, feature sections, and a concise Quick Start guide to ensure clear documentation.

Does the Squad CLI tooling support cross-platform compatibility and built-in test runners?

Squad CLI tooling supports cross-platform compatibility and built-in test runners as core conventions. These standards ensure CLI tools operate consistently across different environments without external testing dependencies.

What is the best way to handle errors in Node.js CLI projects?

The best way to handle errors in Node.js CLI projects is by applying safe error handling conventions. Documenting these patterns across projects prevents drift and maintains consistent user experiences.

Why do my Node.js CLI tooling patterns suffer from project drift across contributors?

Node.js CLI tooling patterns suffer from project drift without a single source of truth for conventions. Establishing standard practices for file structure, error handling, and documentation reduces this drift.