governance

Original：🇺🇸 English

Translated

Govern how the design system evolves — SemVer for tokens/components, the contribution workflow, deprecation policy, and change communication. Use when the user wants to add/promote/deprecate a component or token, decide a version bump, set up a contribution process, or keep the system from fragmenting.

19installs

Sourceplugin87/ux-ui-agent-skills

Added on2026-09-12

NPX Install

npx skill4agent add plugin87/ux-ui-agent-skills governance

SKILL.md Content

View Translation Comparison →

Skill: Governance

Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules.

Steps

Read
```
workflows/governance.md
```
(SemVer table, contribution workflow, deprecation policy, change comms).
Classify the change: major (breaking — renamed/removed token or prop, changed anatomy/default), minor (additive — new token/component/variant/optional prop), patch (fix — contrast/bug/doc/value tweak in tolerance).
For a new component/token: confirm it serves a real, repeated need (≥ 2 places) before promoting product → candidate → core. Design it to the full quality bar (
```
.claude/rules/components.md
```
→ Component Quality Bar).
For a deprecation: mark with reason + replacement + removal version; keep working ≥ 1 minor cycle; provide a migration map (
```
design-systems/crosswalk.md
```
style); remove only in a major.
Wire any new file into
```
CLAUDE.md
```
(File Reference Map + relevant table/router) and add a changelog entry.

Verification (definition of done)

Change has a SemVer level and a changelog entry.
Removals have a deprecation window, a replacement, and a migration table.
New spec meets the 8-state + a11y + token-mapping bar and is reachable via the router.
```
python3 scripts/validate_tokens.py
```
passes; contrast re-checked if colors changed.