What problem does it solve? Design systems fragment as they grow: tokens get renamed without notice, components ship without quality review, and breaking changes land without migration paths. This Skill enforces a consistent governance process so every change is versioned, reviewed, and communicated. ## Core Features & Use Cases - SemVer Classification: Classifies changes as major (breaking renames/removals), minor (additive tokens/components/variants), or patch (fixes and doc tweaks). - Contribution Workflow: Gates new components and tokens behind a real-need check (used in at least 2 places) and a promotion path from product to candidate to core. - Deprecation Policy: Requires a reason, replacement, removal version, migration map, and at least one minor cycle of support before removal in a major release. - Use Case: A designer wants to deprecate an old color token. The Skill walks through marking it deprecated with a replacement, adding a migration table, keeping it working for a minor cycle, and logging the changelog entry. ## Quick Start Ask the assistant to govern a design system change, for example: classify this component rename and set up its deprecation and changelog entry.