Design System Audit: Assessing Maturity, Consistency, and Adoption
Conduct a comprehensive audit of an existing design system to assess its maturity level, identify inconsistencies, measure adoption, and create an improvement roadmap.
Evaluate a design system across multiple dimensions (completeness, consistency, adoption, documentation, governance) to identify gaps and prioritize improvements.
At a glance
Access
Free prompt
Open to copy — no account or payment needed.
Prompt objective
Evaluate a design system across multiple dimensions (completeness, consistency, adoption, documentation, governance) to identify gaps and prioritize improvements.
Real use case
A company launched a design system 18 months ago but isn't sure if it's actually helping. Some teams use it, others don't. Components are inconsistently implemented. They need an objective assessment of the design system's health.
Customize these fields first
Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.
Prompt
Conduct a comprehensive design system audit for [DESIGN SYSTEM NAME] at [COMPANY NAME]. **Audit Dimensions (score 1-5 each):** 1) **Component Completeness:** - Inventory of existing components vs. needed components - Coverage: what % of UI is covered by system components? - Missing components that teams are building custom - Component variants: are all needed states/sizes covered? 2) **Design-Code Consistency:** - Visual comparison: Figma components vs. coded components - Token alignment: are the same values used in design and code? - Behavioral consistency: do components behave the same way? - Gap analysis: list of inconsistencies 3) **Documentation Quality:** - Each component has: description, usage guidelines, do's/don'ts, code examples - Documentation is up-to-date (last updated date) - Searchability and navigation - Onboarding experience for new users 4) **Adoption Metrics:** - % of products using the design system - % of screens built with system components vs. custom - Usage frequency per component - Teams actively contributing vs. only consuming 5) **Governance and Process:** - Clear contribution process - Versioning and release management - Communication channels - Decision-making authority **Scoring Framework:** - Level 1 — Ad hoc: components exist but no system - Level 2 — Foundational: core components documented - Level 3 — Established: good adoption, active maintenance - Level 4 — Optimized: high adoption, strong governance - Level 5 — Leading: industry benchmark, external contributions **Output:** - Current maturity level with justification - Gap analysis by dimension - Prioritized improvement roadmap (quick wins, medium-term, strategic) - Adoption growth plan - Quarterly audit schedule Include audit checklist, scoring rubric, and report template.
Open directly in an AI — the text is pre-filled:
How to use this prompt
- 1Replace the key placeholders first: DESIGN SYSTEM NAME, COMPANY NAME.
- 2Replace any bracketed placeholders like [this] with your own context.
- 3Add extra background information when you want more tailored results.
- 4Combine multiple prompts in one conversation when you need a richer output.
- 5Save your best-performing prompts so they are easy to reuse later.
Next best step
Open the guide first, then branch only if you still need more.
A starter guide to the first prompt categories and patterns worth using when you need better output without prompt guesswork.
If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.
Related prompts
View allReview a design handoff for missing interaction states
A component state matrix and designer/developer decision list. Start with your own evidence and finish with a reviewable next step.
Best for
Produce a component state matrix and designer/developer decision list from the supplied inputs.
UI Component Library with Inventory and Prioritization
Comprehensive audit of required components, organized by category, with a prioritized build roadmap.
Best for
Conduct a UI inventory and determine which components to build first for the design system, maximizing impact with minimal initial effort.
Multi-Platform Design Tokens with Figma-to-Code Synchronization
Design token architecture that works across Figma, React, React Native, and CSS, with automated synchronization pipeline.
Best for
Implement a design token system that serves as the single source of truth between design and code, eliminating visual inconsistencies across platforms.
Design System Documentation in Storybook with Live Examples
A screen/component specification with layout, copy, states, accessibility checks and acceptance criteria. Includes required inputs, evidence checks and a concrete next step.
Best for
Complete “Design System Documentation in Storybook with Live Examples” with a screen/component specification with layout, copy, states, accessibility checks and acceptance criteria that can be checked against the supplied evidence.
Explore other prompt categories
Move sideways into adjacent libraries when the current category is not the full answer.
Every prompt here is free. The course teaches the thinking behind them.
Copy as many prompts as you like. When you want to move from single prompts to a repeatable AI workflow, Learn AI in 30 Days walks through it, one day at a time.
Buy the course once ($20), or choose US$100 once or six monthly payments of US$20 (US$120 total) access.