
Design System Audit & Gap Analysis
Audit design systems for consistency gaps and generate data-backed improvement roadmaps
What You Can Do
You can systematically evaluate your design system's health using structured frameworks that assess component consistency, design token usage, documentation completeness, and developer adoption. The skill generates prioritized gap analysis reports that quantify issues—like duplicate components, token sprawl, or implementation friction—and translates findings into executive-ready roadmaps with business cases for remediation. You'll move beyond subjective design assessments to data-backed improvement strategies.
Features
catalog all components across Figma and codebase, identify redundant or near-duplicate patterns
audit token naming conventions, usage patterns, and orphaned tokens; flag tokens defined but unused
compare design system spec vs. actual product usage; identify components shipped but not adopted by teams
evaluate coverage, accuracy, and accessibility of design system docs; identify missing guidance
evaluate system architecture for multi-product/platform support; flag structural limitations
convert audit findings into phased improvement plan with effort estimates and ROI justification
generate exec summaries and team-specific reports explaining audit results and business impact
pinpoint where developers abandon the system; suggest UX/process improvements to increase compliance
Example Output
Audit Finding: Component Duplication
- Button component exists in 3 versions (ButtonPrimary, Button_Filled, CTAButton) across 2 product codebases
- Estimated dev time waste: ~12 hours/quarter maintaining variants
- Recommendation: Consolidate to single Button with variant prop system
- Priority: High | Effort: 2 weeks | ROI: 15% velocity recovery
Token Health Report
- 287 color tokens defined, 203 actively used (71% utilization)
- 84 orphaned tokens creating maintenance burden
- Token naming inconsistent (some camelCase, some kebab-case)
- Remediation: Archive unused tokens, standardize naming, implement token linting
Developer Adoption Gap
- 65% of shipped components use design system
- Custom Button implementations found in 3 product teams
- Root cause: DS Button missing specific accessibility feature needed by payment module
- Action: Extend DS Button component, deprecate custom implementations
What's Included
- SKILL.md instruction file: complete audit workflow and framework definitions
- Design System Audit Checklist: comprehensive evaluation criteria across components, tokens, docs, and adoption
- Gap Analysis Template: structured format for documenting inconsistencies with severity ratings
- Remediation Roadmap Framework: prioritization matrix for converting findings into phased improvement plan
- Stakeholder Report Templates: exec summary, team-specific reports, and business case language
Who It's For
- Design system leads — conducting regular health checks and planning refactoring initiatives
- Design ops managers — measuring design system ROI and communicating value to leadership
- Senior product designers — inheriting or scaling design systems across multiple products
- Engineering managers — understanding implementation friction and adoption barriers
- Product managers — prioritizing design system investment against feature development
Best For
- Auditing mature or legacy design systems for hidden technical debt
- Quantifying design system ROI and building business cases for investment
- Identifying component duplication and token inconsistency across codebases
- Assessing developer adoption gaps and barriers to design system usage
- Planning design system refactors with prioritized, phased roadmaps







