How do I install the Governance skill?

Run npx skillmds@latest add plugin87/governance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Governance safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Governance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Governance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Governance?

plugin87 (@plugin87) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Governance by plugin87 — Agent Skill

Name: Governance
Rating: 4.2 (5 reviews)
Author: plugin87

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 system from fragmenting.

plugin87 bd08d65 1.7 KB Updated Sep 9, 2026

File contents

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.

Frequently asked questions