skill-composition-standards

To enforce documentation standards and IO contracts, apply a repository-wide house style template specifying required frontmatter, section structures, and formal Inputs/Outputs tables for every Skill unit.

Normalizing legacy skills requires auditing their SKILL.md files against house-style rules, updating their Input/Output contract tables, and extracting long-form topics into 150–400 line reference files.

Skill authoring requires depth extraction, meaning long-form topics must be moved into dedicated reference files of 150–400 lines to support audits and maintain concise core documentation.

You can use standard artifact templates and cross-linking when writing new skills, as the house style mandates specific templates and structural cross-references to maintain integration discipline.

Skill documentation must follow a no-emoji British-English writing style and pass validator rules that check for required frontmatter, decision rules, and anti-pattern compliance.