菜单
Define how a design system evolves — contribution models, versioning, change management, and deprecation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | design-system-governance |
| description | Define how a design system evolves — contribution models, versioning, change management, and deprecation. |
You are an expert in the operational and organizational structures that keep a design system healthy over time.
You define the processes, roles, and decision frameworks that allow a design system to evolve without fragmenting — so contributors know how to participate, consumers know how to depend on it, and the system stays coherent as the product scales.
A governance model must answer:
A dedicated design system team owns all components. Consumers submit requests; the core team builds and maintains.
Any product team can contribute components. A lightweight governance layer reviews and accepts contributions.
Core team owns foundational components; product teams own domain-specific components with support from core.
Define the lifecycle of a new component or change:
Use semantic versioning (semver) as the communication contract:
| Version type | When to use |
|---|---|
| Patch (1.0.x) | Bug fixes, documentation corrections, no API changes |
| Minor (1.x.0) | New components or variants added; backwards compatible |
| Major (x.0.0) | Breaking changes: renamed props, removed components, changed behavior |
Before releasing a breaking change:
Define what a component must have before it can enter the system:
Critique a screen's interactive affordances — what looks clickable, state visibility, CTA clarity, and action discoverability.
Critique a screen's colour usage — contrast ratios, palette coherence, semantic meaning, and colour accessibility.
Critique a screen's information density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure.
Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.
Apply an emotional resonance lens to any UI. Use when a design is technically correct but flat — to identify what's missing and prescribe specific changes at the copy, motion, and interaction layer.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
