squad-conventions

Enforce standardized conventions and patterns across the Squad codebase.

2|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sytone/botnexus --skill squad-conventions-sytone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/sytone/botnexus --skill squad-conventions-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Squad codebase suffers from inconsistent practices as it grows; this Skill defines a standard set of conventions to unify tooling, testing, and project structure.

Core Features & Use Cases

  • Zero dependencies: Squad emphasizes built-in Node.js utilities to minimize external burden.
  • Cross-platform compatibility: Windows, macOS, and Linux support through safe path handling and init flows.
  • Structured project layout: Prescribed directories and templates ensure consistency across repos and teams.
  • Init and upgrade rules: Idempotent initialization and controlled upgrades to protect user state.
  • Clear guidelines for tests and tooling: Standard test runners and error-handling patterns to improve reliability.

Quick Start

Follow these conventions when working on Squad CLI tooling to ensure zero dependencies and cross‑platform compatibility.

Frequently Asked Questions about squad-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What coding standards help maintain consistency in a growing Node.js CLI codebase?

Standardized coding conventions for Node.js CLI projects maintain consistency by prescribing project structure, frontmatter requirements, and cross-platform guidelines. This ensures tooling, tests, and templates remain uniform across teams as the codebase grows.

How do I structure a Node.js CLI project to ensure cross-platform compatibility?

To ensure cross-platform compatibility in Node.js CLI projects, apply safe path handling and use built-in utilities. Standard conventions dictate directory layouts and initialization flows that support Windows, macOS, and Linux without requiring external dependencies.

Do I need external dependencies for Node.js CLI testing and tooling?

No, Node.js CLI testing and tooling can operate with zero external dependencies. Standard conventions emphasize using built-in Node.js utilities to minimize external burden while applying standard test runners and error-handling patterns for reliability.

What is the best way to manage initialization and upgrades for CLI tools without breaking user state?

The best way to manage CLI tool initialization and upgrades is using idempotent initialization and controlled upgrade rules. Standard conventions enforce these patterns to protect user state during updates and maintain project structure consistency.

Why does my Squad CLI project structure lack consistency across different repositories?

Squad CLI project structure lacks consistency when standardized conventions are not applied. Enforcing prescribed directories, templates, and frontmatter requirements unifies tooling and contribution workflows, ensuring maintainability across repositories.