squad-conventions

Document and enforce coding conventions for the Squad project.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill squad-conventions-quaid-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/quaid-app/quaid --skill squad-conventions-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns contributors around a single set of conventions to ensure consistency, readability, and maintainability across the Squad codebase.

Core Features & Use Cases

  • Zero-dependency patterns that keep Squad tooling lightweight and portable.
  • Clear error handling and naming conventions to improve debugging and reviews.
  • Structured file and project layout guidance for onboarding and collaboration.
  • Use Case: when starting a new Squad feature, reference these patterns to scaffold code and reviews.

Quick Start

Review the squad-conventions SKILL.md and align your changes with the defined patterns before submitting a pull request.

Frequently Asked Questions about squad-conventions

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

FAQPage Schema
How do I enforce coding conventions across a Node.js project?

Squad conventions standardize Node.js coding patterns by specifying file layout, naming, and error handling requirements, ensuring consistent source work, tests, and CLI tooling during development and review.

What coding standards help align contributors during code reviews?

Coding standards that align contributors during reviews include clear error handling, structured naming conventions, and defined file layout patterns, which improve debugging and maintainability across collaborative codebases.

Do I need dependencies to maintain coding patterns for CLI tooling?

No, you do not need dependencies to maintain coding patterns for CLI tooling; the squad conventions specify zero-dependency patterns to keep Node.js project tooling lightweight and portable.

How do I structure a Node.js project layout for better onboarding?

Structure a Node.js project layout for onboarding by applying defined file and project layout guidance, ensuring new contributors follow consistent patterns for source work, tests, and documentation.

Why do we need zero-dependency patterns in Node.js development?

Zero-dependency patterns are needed in Node.js development to keep Squad CLI tooling lightweight and portable, preventing bloat while maintaining consistent coding standards across the project.