design-system-audit

Audit design system usage across projects to detect drift and coverage gaps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mengblom/dex-ghx --skill design-system-audit-mengblom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-system-audit
Source: https://github.com/mengblom/dex-ghx/tree/main/.claude/skills/_available/design/design-system-audit
Command: npx skills add https://github.com/mengblom/dex-ghx --skill design-system-audit-mengblom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design systems drift over time, causing inconsistent UI patterns, duplicated custom components, and declining adoption across teams.

Core Features & Use Cases

  • Component usage scanning: Reviews project folders to measure which design-system components are used and where custom implementations replace them.
  • Gap and coverage identification: Detects repeated missing patterns, requested components, and areas where the design system is incomplete.
  • Consistency and adoption tracking: Assesses standard adherence, quantifies adoption rates, and surfaces barriers to using the system.

Quick Start

Run the /design-system-audit command to scan your projects for design-system usage, gaps, inconsistencies, and actionable improvement recommendations.

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 across multiple projects?▼

A design system audit reviews project folders to measure component usage and detect custom implementations replacing standard ones. It surfaces adoption metrics, coverage gaps, and consistency issues to quantify standard adherence across product teams.

What causes design system drift and inconsistent UI patterns?▼

Design system drift happens when teams duplicate custom components instead of using standard ones, causing inconsistent UI patterns. A component audit identifies missing patterns and adoption barriers to restore cross-team consistency.

How do I identify missing component coverage in my design system?▼

Scanning project folders for repeated custom implementations and requested patterns identifies missing component coverage. The audit detects incomplete design system areas and outputs gap findings with prioritized recommendations for improvement.

Can I track UI consistency and component usage across cross-team project folders?▼

You can track UI consistency by reviewing project and component reference folders to assess standard adherence. The audit quantifies component adoption rates and surfaces consistency issues across cross-team implementations.

What is the best way to prioritize design system improvements based on usage data?▼

Prioritizing design system improvements uses an evidence-oriented audit output analyzing adoption metrics and gap findings. This generates prioritized recommendations based on measured component usage and detected coverage gaps.