plugin87/ux-ui-agent-skills

governance

Govern how the design system evolves — SemVer for tokens/components, the contribution workflow, deprecation policy, and change communication.

First seen Jun 8, 2026

Installation

$ npx skills add plugin87/ux-ui-agent-skills --skill governance

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from plugin87/ux-ui-agent-skills · top by installs.

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

Browse all from plugin87/ux-ui-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 902
License MIT License
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,711 B
  • docs SUMMARY.md 320 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 201 installs

SKILL.md

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.