squad-conventions

Name: squad-conventions
Availability: InStock
Author: acmeleme

Standardize coding conventions for Squad CLI projects and PR reviews.

Updated Nov 11, 2025

Search Tags:#cli #coding #conventions #pattern #best-practices #nodejs #squad

Ready to run

npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill squad-conventions-acmeleme

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill squad-conventions-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

These conventions apply to all work on the Squad CLI tool (create-squad). Squad is a zero-dependency Node.js package that adds AI agent teams to any project. Understanding these patterns is essential before modifying any Squad source code.

Core Features & Use Cases

Establishes consistent patterns for file structure, error handling, and testing to reduce onboarding time and miscommunication.
Guides contributors on best practices for CLI tooling, zero-dependency design, and predictable behavior across environments.
Use case: A new teammate onboarding to Squad can reference these conventions to align contributions with existing code.

Quick Start

Follow these conventions when creating or reviewing Squad code: ensure zero-dependency patterns, consistent error handling with fatal(), and path-safe file operations.

Frequently Asked Questions about squad-conventions

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

FAQPage Schema

What are the coding conventions for the Squad CLI tool?▼

Coding conventions for the Squad CLI standardize file structure, error handling, and testing to ensure consistent zero-dependency Node.js design, explicit fatal error handling, and Windows-safe path operations across team contributions.

How do I handle fatal errors in a zero-dependency Node.js CLI?▼

Handle fatal errors in a zero-dependency Node.js CLI by applying the explicit fatal() error handling convention. This ensures predictable behavior across environments by standardizing how critical failures are caught and reported.

Does the Squad CLI require external dependencies for file operations?▼

The Squad CLI requires zero external dependencies for file operations. It enforces Windows-safe path usage and zero-dependency Node.js design to guarantee predictable behavior across different environments without relying on external packages.

How do I standardize file structure and testing for a Node.js CLI tool?▼

Standardize file structure and testing for a Node.js CLI tool by applying consistent coding conventions. These patterns guide contributors on best practices for CLI tooling, reducing onboarding time and miscommunication across Squad projects.

Why use Windows-safe path operations in Node.js CLI development?▼

Windows-safe path operations are used in Node.js CLI development to ensure predictable behavior across environments. They prevent directory traversal errors and inconsistencies when contributors run or review code on different operating systems.