governance
Govern how the design system evolves — SemVer for tokens/components, the contribution workflow, deprecation policy, and change communication. Use wh…
它会碰到什么
扫了多少1 个文本文件，2 KB
它会碰到什么不碰外部（只输出文字）
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
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.mdstyle); 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.pypasses; contrast re-checked if colors changed.
想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。