squad-conventions

Document zero-dependency coding conventions for the Squad CLI codebase.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/mlinnen/mr-pumpkin --skill squad-conventions-mlinnen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/mlinnen/mr-pumpkin/tree/main/.squad/skills/squad-conventions
Command: npx skills add https://github.com/mlinnen/mr-pumpkin --skill squad-conventions-mlinnen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and enforces core conventions and patterns across the Squad codebase to ensure consistency, readability, and maintainability.

Core Features & Use Cases

  • Establishes zero-dependency coding standards for the Squad CLI.
  • Documents Node.js project structure, error handling, and file organization.
  • Guides contributors on consistent patterns for testing, naming, and documentation.

Quick Start

Follow these conventions when contributing to the Squad CLI project to maintain zero-dependency 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 coding standards in a Node.js CLI project?

Zero-dependency coding standards standardize the Node.js CLI codebase by enforcing that all patterns are implemented without external dependencies. This approach ensures consistency, readability, and maintainability across all modules and tests.

What are zero-dependency conventions and when do I need them for Node.js utilities?

Zero-dependency conventions are documented rules requiring Node.js utilities and modules to operate without external packages. You need them when standardizing a codebase to improve maintainability and reduce reliance on third-party libraries.

How do I document Node.js project structure and error handling patterns?

Document Node.js project structure and error handling patterns by defining them in a central conventions file. This guides contributors on consistent file organization, naming, and testing approaches across the repository.

Can I use external libraries while following these coding standards for Squad CLI development?

No, you cannot use external libraries under these coding standards. The conventions explicitly enforce a zero-dependency pattern, requiring all utilities and modules to be implemented without external packages.

What is the best way to standardize testing and naming conventions across a Node.js repository?

The best way to standardize testing and naming conventions is to establish explicit coding standards documented within the repository. This provides clear guidance for contributors and ensures uniform patterns across all development efforts.