mcpField
G
governance

governance

github.com/plugin87Design & UI3.0k486 installsUpdated 1d ago
Repository

About governance

governance is a design-system skill for applying versioning, contribution, and deprecation policies as a system evolves. It guides change classification and the checks required before changes are complete.

Key features

  1. 01Classifies changes by SemVer level
  2. 02Sets criteria for promoting components and tokens
  3. 03Defines deprecation periods and migration maps
  4. 04Updates file references and changelogs
  5. 05Checks token validity and color contrast

Use cases

  1. 01Determine the release level for a design-system change
  2. 02Plan token or component deprecation and migration
  3. 03Review a proposed component before adding it to the core

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill governance

After installing, type/governancein Claude Code to confirm it loaded.

Details

From the project README

Skill: Governance

Step 0: is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

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

Steps

  1. Read ${CLAUDE_SKILL_DIR}/../../../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_SKILL_DIR}/../../../.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 (${CLAUDE_SKILL_DIR}/../../../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 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_tokens.py passes; contrast re-checked if colors changed.

Comments

Markdown supported