Claude
Skill
governance
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 s
Virus-scanned
Reviewed automatically before listing.
Download
plugin87-ux-ui-agent-skills-.claude_skills_governance-278e9d9.zip · 1 KB
Install
skills CLI
npx skills add https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/governance
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install plugin87-ux-ui-agent-skills@llmmart
Git
git clone https://github.com/plugin87/ux-ui-agent-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole plugin87/ux-ui-agent-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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.mdstyle); 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.pypasses; contrast re-checked if colors changed.
Files (ux-ui-agent-skills)
-
SKILL.md 1.7 KB
--- name: governance description: 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. invocation: user --- # Skill: Governance Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules. ## Steps 1. Read `workflows/governance.md` (SemVer table, contribution workflow, deprecation policy, change comms). 2. 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). 3. 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). 4. 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. 5. 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.