design-system-governance
Define how a design system evolves: ownership models, contribution lifecycle, semantic versioning as a contract, deprecation policy, and quality gates.
- Installs
- 174
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/podo/design-agent-skills --skill design-system-governance- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads design-system-governance automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
design-system-governance
<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->Catalogue stub — full skill: Owl-Listener/designer-skills
Decision tree
-
Is the full skill already installed?
- Global:
f=~/.agents/skills/design-system-governance/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" - Project:
f=.agents/skills/design-system-governance/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" installed→ the skill is installed asdesign-system-governance, invoke it and proceedpointer→ go to step 2
- Global:
-
Detect scope, then install:
[ -e ~/.agents/skills/design-system-governance ] && echo "global" || echo "project"Global:
npx skills add Owl-Listener/designer-skills --skill design-system-governance -g -yProject:
npx skills add Owl-Listener/designer-skills --skill design-system-governance -yClaude Code: send a command as a chat message starting with
!to run it without leaving the conversation.
Claude Code plugin route:
/plugin marketplace add Owl-Listener/designer-skills
/plugin install design-systems@designer-skills
Heads-up
- License: MIT
Invoke after install
- Skill name:
design-system-governance - Trigger phrases: "design system governance", "design system contribution model", "component versioning policy", "design system deprecation"
What it does
The Owl-Listener design-system-governance skill: the three ownership models (centralized / federated / hybrid) with trade-offs, the contribution lifecycle (request → triage → design → review → build → release → communicate), semver as a consumer contract, a deprecation process with migration guidance, and the quality bar a component must clear to enter the system.
When NOT to use
- Authoring tokens themselves → use
design-tokens-skill - Driving adoption of an existing system → use
design-system-adoption(a separate skill in the same Owl-Listener repository; this stub does not install it)
FAQ
What does the design-system-governance skill do?
Define how a design system evolves: ownership models, contribution lifecycle, semantic versioning as a contract, deprecation policy, and quality gates.
How do I install design-system-governance?
Run npx skills add https://github.com/podo/design-agent-skills --skill design-system-governance in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/design-system-governance/ (personal) or .claude/skills/design-system-governance/ (project).
Which AI agents can use design-system-governance?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is design-system-governance safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains design-system-governance?
It is published by podo in podo/design-agent-skills. It has 174 recorded installs.
More from podo/design-agent-skills
distinctive-frontend
podo/design-agent-skills
Generates distinctive interfaces that avoid generic AI aesthetics, using extreme typography, cohesive themes (Cyberpunk, Brutalist, Vaporwave, Nordic Minimalism), orchestrated staggered animations, and layered backgrounds. Originally published as Koomook/claude-frontend-skills; installed from a verbatim mirror.
taste-skill
podo/design-agent-skills
Anti-slop frontend art direction (tasteskill v2). Deals researched design directions for a page or app screen from a library built from curated gallery sites, enforces a strict no-generic-AI-UI house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Works in any web stack.
emilkowalski-skill
podo/design-agent-skills
Emil Kowalski's design engineering skills. Creator of Sonner, Vaul, and animations.dev. Covers the animation decision framework, custom easing curves, component interaction principles, and typography rules, plus skills to review, audit, and improve motion, performance, and native-feeling mobile web UI.
ui-craft
podo/design-agent-skills
Design engineering skill for AI coding agents: opinionated rules for how interfaces should look, move, and feel, a required discovery phase before coding, domain references, three style variants (minimal, editorial, dense-dashboard), and an anti-slop approach that flags generic patterns such as centered hero sections, Inter-only typography, and three-column card grids. Covers premium UI taste, component patterns, and design-engineering workflows.
color-expert
podo/design-agent-skills
A large color-science knowledge base applied to UI/UX design. Covers OKLCH/OKLAB color spaces, palette generation, accessibility contrast ratios, color naming, pigment mixing, and historical color theory. By meodai, creator of color-names.
apple-hig-skills
podo/design-agent-skills
Apple Human Interface Guidelines as agent skills covering iOS, macOS, visionOS, watchOS, and tvOS. From raintree-technology, makers of the Apple HIG compliance website.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.