squad-conventions

Enforce zero-dependency and cross-platform pathing standards for Squad CLI development.

Updated Apr 16, 2026

Search Tags:#architecture #cli #node.js #conventions #squad #zero-dependency

Ready to run

npx skills add https://github.com/Quintenps/contactswap-agents --skill squad-conventions-quintenps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/Quintenps/contactswap-agents/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/Quintenps/contactswap-agents --skill squad-conventions-quintenps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all development on the Squad CLI tool adheres to strict architectural constraints, preventing dependency bloat and maintaining cross-platform compatibility.

Core Features & Use Cases

Zero-Dependency Enforcement: Validates that no external npm packages are added to the project.
Standardized Error Handling: Provides the fatal() pattern for consistent, user-friendly error reporting.
Cross-Platform Pathing: Ensures all file operations use path.join() to maintain Windows, macOS, and Linux compatibility.
Use Case: Use this Skill when adding new features to the Squad CLI to ensure your code matches the existing zero-dependency, test-driven architecture.

Quick Start

Apply the squad-conventions skill to review the current codebase for any violations of the zero-dependency or pathing patterns.

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?▼

Cross-platform file path handling requires using path.join() for all file operations, ensuring your Node.js CLI maintains compatibility across Windows, macOS, and Linux without relying on external path normalization packages.

What is the standard error handling pattern for a zero-dependency Node.js CLI?▼

The standard error handling pattern for a zero-dependency Node.js CLI is the fatal() function, which provides consistent, user-friendly error reporting without requiring external logging frameworks or process management libraries.

How do I maintain architectural standards when adding new features to a CLI tool?▼

Yes, Node.js built-in test runners can fully replace external testing frameworks in a zero-dependency CLI by providing native assertion and test execution capabilities, ensuring code quality without adding npm packages.

Why does my Node.js CLI fail on Windows after adding new file operations?▼

Node.js CLI file operations fail on Windows when hardcoded paths are used instead of path.join(); enforcing platform-agnostic path handling ensures consistent cross-platform behavior across Windows, macOS, and Linux.