squad-conventions

Enforce zero-dependency and fatal error handling standards for Squad CLI code.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill squad-conventions-jonnymuir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill squad-conventions-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistency and maintainability across the Squad CLI codebase by enforcing strict architectural patterns and preventing the introduction of external dependencies.

Core Features & Use Cases

  • Zero-Dependency Enforcement: Validates that all logic relies exclusively on Node.js built-in modules.
  • Standardized Error Handling: Provides the fatal() pattern for consistent, user-friendly error reporting.
  • Cross-Platform Compatibility: Ensures file system operations use path.join() to maintain Windows, macOS, and Linux support.
  • Use Case: Use this skill to audit new code contributions to ensure they adhere to the zero-dependency constraint and proper error handling patterns before merging.

Quick Start

Use the squad-conventions skill to validate that the current project structure and error handling logic comply with the established codebase standards.

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

You can enforce zero-dependency constraints by validating that all logic relies exclusively on Node.js built-in modules. This prevents external packages and ensures long-term maintainability across the codebase.

What is the best way to standardize error handling for Node.js built-in modules?

Standardize error handling by implementing a fatal() pattern. This provides consistent, user-friendly error reporting across CLI operations without introducing external dependencies.

Does my Node.js file system code need path.join() for cross-platform compatibility?

Yes, file system operations require path.join() to maintain cross-platform compatibility. This ensures your CLI tool works consistently across Windows, macOS, and Linux environments.

How do I audit code contributions for architectural standards and zero dependencies?

Audit code contributions by applying architectural standards during code reviews and project initialization. This validates compliance with zero-dependency constraints and fatal error handling patterns before merging.

Can I use external libraries when developing new agent team features for a CLI?

No, developing new agent team features requires strict adherence to Node.js built-in modules. External libraries are prohibited to maintain the zero-dependency architectural constraint.

Why does a zero-dependency architecture matter for CLI tools?

A zero-dependency architecture ensures consistency and maintainability across the codebase. Relying solely on built-in modules prevents dependency bloat and version conflicts in CLI tools.