skills.rest
robpitcher
robpitcherCOMMUNITY
Explore all skills by this author →
GitHub

squad-conventions

Standardize Squad CLI project conventions for Node.js tooling and templates.

Updated Apr 14, 2026
Search Tags:#conventions#error-handling#nodejs#coding-standards#squad#windows-compatibility#init-idempotency
One-click install
npx skills add https://github.com/robpitcher/eShopOnWeb --skill squad-conventions-robpitcher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/robpitcher/eShopOnWeb/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/robpitcher/eShopOnWeb --skill squad-conventions-robpitcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent conventions across Squad tooling lead to fragmentation, higher maintenance costs, and steeper onboarding curves. This Skill standardizes patterns to ensure reliability and clarity in CLI development.

Core Features & Use Cases

  • Zero-dependency patterns: all tooling relies on Node.js built-ins, avoiding external packages.
  • Deterministic file handling: idempotent init flows and safe copy patterns to prevent accidental overwrites.
  • Standardized error handling: uniform fatal-style messaging with clear exit behavior.
  • Cross-platform compatibility: Windows-friendly path handling and environment awareness.
  • File structure guidance: recommended organization with .squad/ templates and clear templates. Use cases: teams adopting Squad CLI conventions for new features, upgrades, and contributor onboarding.

Quick Start

Follow the Squad conventions when adding or updating Squad CLI code: ensure zero dependencies, implement idempotent init flows, and apply the standard error handling and file-structure guidelines.

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 zero-dependency tooling?▼

Node.js CLI coding standards for zero-dependency tooling require relying strictly on Node.js built-ins, avoiding external packages to reduce maintenance overhead and ensure consistent execution.

How do I implement idempotent init flows for deterministic file handling?▼

To implement idempotent init flows for deterministic file handling, apply safe copy patterns that prevent accidental overwrites and ensure file operations remain consistent across repeated executions.

Does Node.js CLI tooling require Windows compatibility for path handling?▼

Node.js CLI tooling requires Windows compatibility for path handling by implementing environment awareness and Windows-friendly path patterns to prevent file operation failures across different operating systems.

What is the best way to standardize error handling in Node.js CLI applications?▼

The best way to standardize error handling in Node.js CLI applications is applying uniform fatal-style messaging with clear exit behavior to ensure predictable failure modes and consistent user feedback.

Why do I need standardized conventions for CLI project maintainability?▼

You need standardized conventions for CLI project maintainability to prevent fragmentation, reduce onboarding curves, and ensure consistent patterns across tooling upgrades and feature additions.

Related Skills

Explore More Software Engineering Skills→
webmaxruwebmaxru
49

squad-conventions

Enforce and document Squad CLI coding conventions for Node.js tooling.

Community
Advanced
veerababumanyamveerababumanyam

project-structure

Enforce standardized project structure and coding conventions across the RawDrive monorepo.

Community
Basic
christianhellechristianhelle
413

squad-conventions

Document and enforce Squad conventions for JavaScript/Node.js codebases.

Community
Intermediate
tumblecat44tumblecat44
1

get-api-docs

Fetch latest API documentation for external libraries using the chub CLI.

Community
Basic