dragoon0x/everything-design-taste

design-system-governance

Design system contribution models, decision-making processes, and system maintenance.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill design-system-governance

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,435 B
  • docs SUMMARY.md 117 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

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

  1. Proposal: Need identified, RFC written.
  2. Review: Design system team + stakeholders evaluate.
  3. Build: Contributor builds to system standards.
  4. QA: Design + code review, accessibility audit.
  5. Document: Usage guidelines, props, examples.
  6. 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.