authoring-design-system

Start from a design-system template's section structure, identify the product archetype from the PRD and user-flows, then fill each section with researched, decision-complete content. Define intent-named DTCG tokens, spec every component with six parts, and set numeric WCAG 2.2 AA accessibility thresholds.

DTCG is the W3C Design Tokens Community Group format expressing tokens as typed JSON with $type and $value fields plus curly-brace aliasing. It organizes tokens into primitive, semantic, and component tiers so theming works by re-pointing semantic aliases rather than forking components.

Amend it as a scoped, versioned delta: make the minimal in-place edit to the affected tokens or components plus their ripple, bump semver, and add a changelog entry. Deprecate breaking changes in a minor release before removing them in a major, never regenerate the whole system.

Target WCAG 2.2 Level AA with numeric thresholds: text contrast at least 4.5:1, UI contrast at least 3:1, visible and unobscured focus indicators, 24x24 pixel target sizes, full keyboard operability, and reduced-motion support. Bake these into token and component specs rather than auditing later.

Governance can be fully omitted only when the system has a single maintainer, a single consumer, and no versioned external release. Above that threshold, document versioning, changelog, deprecation and migration policy, contribution model, ownership, and adoption guidance.

Do not use it to review a finished design system, define per-screen wireframe layouts, produce high-fidelity coded prototypes, or ship a coded component library. It produces the textual design-system document that precedes those downstream activities.