squad-conventions

Enforce coding patterns for Squad CLI projects using Node.js built-ins.

66|41|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/olivomarco/vbd-copilot --skill squad-conventions-olivomarco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill squad-conventions-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Core conventions and patterns used in the Squad codebase to ensure consistency, safety, and maintainability across projects.

Core Features & Use Cases

  • Zero-dependency patterns and use of Node.js built-ins to keep environments lightweight.
  • Standardized error handling with the fatal() pattern to provide clean user-facing errors.
  • Prescribed file structure, Windows compatibility, and cross-platform guidance to support diverse teams.
  • ANSI color constants and consistent UI primitives to deliver predictable CLI output.

Quick Start

Apply these conventions when starting or updating a Squad project to ensure consistency.

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 CLI project?

Standardized error handling in CLI development uses a fatal() pattern to provide clean user-facing errors. This codifies consistent error-handling conventions, ensuring reliable and predictable outputs without crashing the application unexpectedly.

What is the zero-dependency pattern for Node.js built-ins in CLI development?

The zero-dependency pattern for Node.js built-ins keeps environments lightweight by relying solely on native runtime features. This approach eliminates external package dependencies, ensuring cross-platform compatibility and safer CLI project execution.

How do I standardize CLI output with ANSI color constants?

To standardize CLI output with ANSI color constants, apply consistent UI primitives that deliver predictable terminal formatting. This enforces a uniform visual structure across all project commands and user-facing messages.

Does this convention framework support Windows compatibility for CLI tools?

Yes, this convention framework supports Windows compatibility for CLI tools by prescribing cross-platform guidance and file structures. It ensures zero-dependency Node.js built-ins operate consistently across diverse team environments.