What problem does it solve? Teams exporting architecture write-ups, runbooks, reports, and handoffs often produce inconsistent documents with ad-hoc colors, skipped heading levels, and wrong file formats. This Skill centralizes the house style so every delivered artifact follows the same palette, heading hierarchy, capitalization, and format-selection rules. ## Core Features & Use Cases - Five-role color palette: Ink, Muted, Accent, Warn, and Fail hex values with strict usage rules so color carries meaning rather than decoration. - Heading and capitalization standards: One H1 matching the filename, no skipped levels, depth capped at H3, sentence case everywhere, and a mandatory provenance line on exports. - Format routing: Decision table mapping reader needs to PDF, DOCX, HTML, or Markdown, with explicit routing to generator skills like doc-builder and anthropic-office-skills, including degraded-path handling when doc-builder or Microsoft Word is missing. - Use Case: When asked to export an architecture review as a PDF for a client, the Skill selects PDF, applies the palette and heading rules, routes generation to doc-builder with the configured brand theme, and relays any branding errors verbatim. ## Quick Start Apply the house style to export this architecture write-up as a branded PDF using the configured docs.theme.
