{skill-name}

Codifies Squad file structures, naming conventions, and onboarding guidelines for projects.

Updated Feb 22, 2026

Search Tags:#templates #documentation #onboarding #patterns #conventions #best-practices #squad

Ready to run

npx skills add https://github.com/londospark/citrust --skill skill-name-londospark

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: {skill-name}
Source: https://github.com/londospark/citrust/tree/main/.squad-templates
Command: npx skills add https://github.com/londospark/citrust --skill skill-name-londospark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad projects often drift from agreed-upon conventions. This skill codifies core patterns to keep teams aligned.

Core Features & Use Cases

Establishes standard file structure and naming conventions for Squad assets and templates.
Documents core patterns like error handling, path handling, and copy utilities to ensure consistent implementation.
Facilitates onboarding by providing a single reference for new contributors and squad members.

Quick Start

Review this skill to align your contributions with Squad conventions before starting work.

Frequently Asked Questions about {skill-name}

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

FAQPage Schema

How do I standardize squad conventions across multiple projects?▼

Squad onboarding is handled by providing a single reference for new contributors. This reference codifies core patterns like error handling and path handling, ensuring new members align with established conventions before starting work.

How do I enforce frontmatter requirements and section patterns in documentation?▼

To enforce frontmatter requirements and section patterns in documentation, you apply standardized conventions to template maintenance and code reviews. This ensures consistent authoring and tooling across all Squad-enabled workflows.

What's the best way to document core patterns like error handling for a development squad?▼

Documenting core patterns like error handling for a development squad involves codifying these patterns into a shared skill. This establishes standard file structures and ensures consistent implementation across the team.

Does this approach to template maintenance work for all Squad-enabled workflows?▼

Yes, this approach to template maintenance works across all Squad-enabled workflows. It applies standardized naming rules and example usage to ensure consistent authoring and tooling throughout the project lifecycle.

Why does my project drift from agreed-upon conventions during development?▼

Projects often drift from agreed-upon conventions due to a lack of codified standards. By establishing a single reference for file structures, patterns, and contribution guidelines, teams can keep contributions aligned.