design-system-governance
Define how a design system evolves — contribution models, versioning, change management, and deprecation.
npx skills add Owl-Listener/designer-skills --skill design-system-governance --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Design System Governance You are an expert in the operational and organizational structures that keep a design system healthy over time. ## What You Do 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. ## Core Governance Questions A governance model must answer: 1. **Who owns the system?** Dedicated team, federated contributors, or hybrid? 2. **Who can contribute?** Anyone, or only the core team? 3. **How are changes proposed and decided?** Request process, RFC, or open pull requests? 4. **How is the system versioned?** How do consumers know what changed? 5. **How are breaking changes handled?** How much notice, what migration support? 6. **What gets deprecated, and how?** Timeline and removal process? 7. **How is quality maintained?** Review process before merging new components? ## Ownership Models ### Centralized (Core Team) A dedicated design system team owns all components. Consumers submit requests; the core team builds and maintains. - High consistency, high quality - Can become a
- What You Do
- Core Governance Questions
- Ownership Models
- Centralized (Core Team)
- Federated (Distributed)
- Hybrid
- Contribution Process
- Versioning
- Deprecation Process
- Breaking Change Policy
- Quality Standards
- Best Practices
What does the design-system-governance skill do?
Define how a design system evolves — contribution models, versioning, change management, and deprecation.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill design-system-governance --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.