- 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:` was not a field Claude Code reads - unknown frontmatter keys are # ignored without an error, so these six were auto-invocable the whole time they # were marked user-only. This is the field that actually does it.
- disable-model-invocation
- true
Skill: Governance
Requirements
This skill needs the full UX/UI Agent Skills kit: the gates, the references and
the design-system library. Install it with npx [email protected] init
or as the Claude Code plugin. npx [email protected] add copies the skill folder and
nothing else. Installed that way, this skill runs in guidance-only mode: no gate
runs, so it gives no verdict.
Step 0: is the kit here? Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSING, open your reply with: "Guidance-only mode: the UX/UI Agent Skills kit is not installed here, so no gate ran and nothing below is measured." Then work from this file and general practice, under three rules. Do not guess or cite the contents of a kit file you could not open. State no measured number (no contrast ratio, no N/N, no "passes WCAG"): write "not verified" where one would go. End with a lineSkipped (kit not installed):that names every gate script this file tells you to run, then the install command above.
Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules.
Steps
- Read
${CLAUDE_SKILL_DIR}/../../../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_SKILL_DIR}/../../../.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 (
${CLAUDE_SKILL_DIR}/../../../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.