design-system-audit

Audit design system usage and identify component coverage gaps across projects.

1|Updated Jun 28, 2026
One-click install
npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill design-system-audit-whmathews15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-audit
Source: https://github.com/whmathews15/DEX-Personal-Operating-System/tree/main/.claude/skills/_available/design/design-system-audit
Command: npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill design-system-audit-whmathews15

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams detect when design system usage is drifting, where custom UI patterns are being reinvented, and which gaps are slowing consistent product delivery.

Core Features & Use Cases

  • Usage Scan: Reviews project files for component mentions and repeated UI patterns.
  • Gap Detection: Identifies missing components, common custom implementations, and coverage holes.
  • Consistency Check: Compares real project usage against design system standards and highlights deviations.
  • Use Case: A product team preparing a quarterly design review can use this Skill to see which components are adopted most, which gaps are recurring, and what should be added to the roadmap.

Quick Start

Run the design-system-audit skill on your project workspace to identify design system usage, consistency issues, and the highest-priority components to build next.

Frequently Asked Questions about design-system-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit design system adoption and find custom UI patterns?

To audit design system adoption, scan project files for component mentions and compare usage against design system standards to identify custom UI patterns, coverage holes, and inconsistent implementations across your product repositories.

What is design system drift and how do I detect inconsistent components?

Design system drift occurs when teams reinvent custom UI patterns instead of using standard components. You detect it by scanning project content for component mentions, measuring adoption metrics, and comparing real usage against established design system standards.

Can I measure component coverage gaps across multiple product repositories?

Yes, you can measure component coverage gaps by scanning project content across product and design repositories to identify missing components, repeated custom implementations, and coverage holes, then summarizing adoption metrics and priority recommendations.

How do I identify which components to add to my design system roadmap?

Identify roadmap priorities by auditing project files for recurring custom UI patterns and coverage gaps, then summarizing which missing components are slowing consistent product delivery and recommending the highest-priority items to build next.

What's the best way to prepare a quarterly design system consistency review?

Prepare a quarterly design system consistency review by scanning project workspaces to measure component adoption, spot custom implementations, identify coverage gaps, and summarize consistency issues alongside prioritized recommendations for the roadmap.