Agent Skills › plugin87/ux-ui-agent-skills › governance

governance

GitHub

管理设计系统的演进治理，包括版本控制、贡献流程、废弃策略及变更沟通。用于组件/Token的添加、升级或废弃决策，确保系统一致性并防止碎片化。

.claude/skills/governance/SKILL.md plugin87/ux-ui-agent-skills

触发场景

用户想要添加或提升新组件/Token时需要决定版本号升级幅度时执行组件或Token的废弃操作时建立或调整贡献流程时

安装

npx skills add plugin87/ux-ui-agent-skills --skill governance -g -y

更多选项

非标准路径

npx skills add https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/governance -g -y

不安装直接使用

npx skills use plugin87/ux-ui-agent-skills@governance

指定 Agent (Claude Code)

npx skills add plugin87/ux-ui-agent-skills --skill governance -a claude-code -g -y

安装 repo 全部 skill

npx skills add plugin87/ux-ui-agent-skills --all -g -y

预览 repo 内 skill

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

SKILL.md

Frontmatter

{
    "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.",
    "disable-model-invocation": true
}

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

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