What problem does it solve? Writing a design-system document from scratch often produces generic boilerplate, half-specified components, and vague accessibility claims that designers and engineers cannot build from. This Skill supplies the method and quality bar for producing a complete, grounded design-system document from a product's direction. ## Core Features & Use Cases - DTCG token architecture: Defines design tokens in the W3C DTCG format across primitive, semantic, and component tiers, with intent-based naming and alias-swap theming for light/dark and multi-brand. - Full component catalog: Sizes the catalog to the product archetype and specs every component with anatomy, states, variants, usage rules, and accessibility under one consistent API vocabulary. - Numeric accessibility: Bakes WCAG 2.2 AA thresholds (contrast ratios, focus appearance, target size, keyboard support) directly into token and component specs. - Amend mode: Edits an existing design system as a scoped, semver-versioned delta with deprecate-then-migrate handling instead of regenerating the whole document. - Use Case: Given a PRD for a new SaaS product, produce a markdown design-system document covering principles, tokens, a component catalog, patterns, i18n conventions, voice, and governance that a UI engineer can implement directly. ## Quick Start Use authoring-design-system to create a design-system document from my product PRD, covering tokens, components, and WCAG 2.2 AA accessibility.