squad-conventions

Codify Squad CLI development conventions for consistent structure, testing, and error handling.

3|5|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill squad-conventions-ronniegeraghty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.agents/skills/squad-conventions
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill squad-conventions-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad projects often diverge in structure and practices, leading to onboarding friction and maintenance gaps. This skill codifies a centralized set of conventions to align teams around a consistent CLI development base.

Core Features & Use Cases

  • Zero-dependency patterns and tooling guidance for Squad CLI projects.
  • Clear guidance on testing, error handling, and Windows-friendly init flows.
  • Structured file organization and copy-pattern practices to simplify collaboration and upgrades.

Quick Start

Follow the conventions in this skill when creating or updating Squad projects 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 standardize Nodejs CLI conventions across multiple development teams?

Standardize Nodejs CLI conventions by applying a centralized set of rules for zero-dependency patterns, testing, and error handling. This ensures consistent structure and simplifies collaboration across all Squad projects.

What are zero-dependency patterns for CLI development and when are they needed?

Zero-dependency patterns in CLI development require building tools without external runtime packages. They are needed to minimize maintenance gaps, ensure Windows compatibility, and create idempotent initialization flows for Squad projects.

How do I ensure Windows compatibility and idempotent init flows in a Nodejs CLI project?

Ensure Windows compatibility and idempotent init flows by following explicit Squad conventions for structured file organization, scripts, and copy-pattern practices. This prevents onboarding friction during initialization.

Do I need external testing libraries to implement standard CLI error-handling conventions?

No, you do not need external testing libraries. The conventions define requirements for zero-dependency patterns, meaning error handling and testing structures are standardized without relying on external dependencies.

What is the best way to structure file organization and scripts for a Squad CLI project?

The best way to structure files and scripts is to follow the codified Squad conventions. This provides explicit guidance on structured file organization, references, and asset copy-patterns to simplify upgrades and collaboration.