DS
Design System Audit
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-design
Audit a design system for consistency, coverage, and quality. Use when asked to audit a design system, review a component library, assess design token coverage, or evaluate the health of a shared design system. Produces a structured audit with a health score, component coverage gaps, token inconsistencies, accessibility issues, and a prioritised remediation roadmap.
📚 Based on Atomic Design — Brad Frost
🗣 Say this to your agent
“Audit our design system for consistency and coverage”“Review our component library and identify gaps”“Assess the health of our shared design system”“Run a design system audit before we do a rebrand”“What's wrong with our design system and what should we fix first?”
What to give it
▸Design system name — and what product(s) it serves
▸Audit scope — component library / design tokens / documentation / contribution process / all of the above
▸Current tooling — Figma / Storybook / Zeroheight / custom / combination?
▸Team using it — how many designers and engineers, how many products?
▸Known pain points — what do teams complain about most?
▸Governance model — centralised team / federated contributors / no dedicated team?
▸Goal of the audit — improve adoption / prepare for a rebrand / onboard new teams / justify investment?
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Coverage gaps are identified by comparing the design system to actual production UI, not assumed
✓Accessibility issues cite specific WCAG criterion and affected components
✓Adoption barriers are backed by evidence (interviews, survey, usage data) — not assumed
✓Remediation roadmap has effort estimates and is sequenced by impact
✓Both Figma and code (Storybook/implementation) are assessed — not just Figma
✓Stakeholders from design, engineering, and product have reviewed the audit
⚠️ What it refuses to do
Do not assess only the Figma library without checking the code implementation — Figma-code drift is one of the most common and costly design system failures
Do not score adoption without interviewing teams — audit tool metrics miss the human reasons teams build custom components instead of using the system
Do not treat all component gaps equally — prioritise gaps based on how many production screens rely on custom implementations, not alphabetically
Do not recommend adding more components without first auditing documentation quality — an undocumented component is often worse than no component
Do not schedule remediation without a named owner per initiative — design system improvements without ownership consistently stall
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="design-system-audit"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Design System Audit is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog