Design system governance
Skill Dragoon0x/everything-design-taste/skills/design-system-governance
Design system contribution models, decision-making processes, and system maintenance.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill design-system-governanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 249 tokens by cl100k_base, as published. Nobody here has run it
Design System Governance
Governance Models
Centralized
- Dedicated design system team owns everything.
- Product teams request components through a queue.
- Pros: consistency, quality. Cons: bottleneck, disconnected from product needs.
Federated
- Product teams contribute components.
- Design system team reviews, approves, and maintains.
- Pros: diverse input, faster. Cons: inconsistent quality without strong review.
Community
- Anyone can contribute.
- RFC process for new components.
- Design system team as curators, not gatekeepers.
Contribution Process
- Proposal: Need identified, RFC written.
- Review: Design system team + stakeholders evaluate.
- Build: Contributor builds to system standards.
- QA: Design + code review, accessibility audit.
- Document: Usage guidelines, props, examples.
- Release: Versioned, communicated, integrated.
Health Metrics
- Adoption rate: % of product using system components.
- Override rate: Custom styles overriding system values.
- Contribution rate: Components contributed by product teams.
- Bug rate: Issues in system components vs custom.
- Satisfaction: Developer and designer NPS.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.