What problem does it solve? Teams building multiple interfaces often repeat visual decisions and drift into inconsistent components, tokens, and accessibility behavior. This Skill structures the creation, evolution, and documentation of a shared design system so product surfaces stay coherent. ## Core Features & Use Cases - Token Architecture: Defines layered primitive, semantic, and component tokens with theming via semantic role remapping and explicit contrast requirements. - Component Contracts: Specifies purpose, anatomy, variants, states, keyboard and assistive-technology behavior, and API defaults for each shared component. - Governance & Migration: Treats token and API changes as compatibility-sensitive, documents breaking changes, and plans incremental migration paths. - Use Case: When three product teams each maintain their own button styles, use this Skill to inventory the duplication, define a semantic token layer, and publish a single accessible button contract with a migration plan. ## Quick Start Audit our existing UI components and propose a semantic token architecture and component contract for a shared design system.
