squad-conventions

Enforce shared coding conventions across the Squad codebase.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a single, shared set of conventions for Squad code to improve consistency, readability, and maintainability across the project.

Core Features & Use Cases

  • Zero-dependency standard: Guidelines to avoid runtime dependencies and rely on Node.js built-ins.
  • Consistent error handling: Uses a centralized fatal() pattern and standardized messaging.
  • Platform-agnostic tooling: Enforces cross-platform path handling, color constants, and safe I/O patterns.
  • Onboarding and maintenance: Provides a stable baseline for onboarding contributors and auditing the codebase.

Quick Start

Follow these conventions when contributing to Squad code to ensure consistency, safety, and cross-platform compatibility.

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 coding standards in a Node.js CLI project?

Enforce zero-dependency coding standards by applying guidelines that avoid runtime dependencies and rely strictly on Node.js built-ins. This ensures the CLI core remains lightweight and maintainable.

What is the best way to standardize error handling across a Node.js codebase?

Standardize error handling across a Node.js codebase by using a centralized fatal() pattern for messaging. This provides a consistent approach to critical failures across CLI tooling and tests.

How do you ensure cross-platform compatibility for CLI tooling in Node.js?

Ensure cross-platform compatibility for CLI tooling by enforcing cross-platform path handling, using ANSI color constants, and following safe I/O patterns. This prevents platform-specific failures.

Do I need external libraries to implement consistent file structure and naming conventions?

No external libraries are needed to implement file structure and naming conventions. The Skill specifies a zero-dependency standard, relying entirely on Node.js built-in modules for structural consistency.

Why establish shared coding conventions for a software development squad?

Establish shared coding conventions for a software development squad to improve consistency, readability, and maintainability across the project. This baseline streamlines onboarding and codebase auditing.

Can I use these coding standards for onboarding new contributors to a CLI project?

Yes, you can use these coding standards for onboarding new contributors to a CLI project. The shared baseline provides stable guidelines for naming, error handling, and structure to ensure safe contributions.