Claude-skill-registry design-system-audit

Review design system usage and gaps

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/design-system-audit" ~/.claude/skills/majiayu000-claude-skill-registry-design-system-audit && rm -rf "$T"
manifest: skills/data/design-system-audit/SKILL.md
source content

Purpose

Audit design system health, identify gaps, and track adoption.

Usage

  • /design-system-audit
    - Full design system review

Steps

  1. Scan for design system usage:

    • Search 04-Projects/ for component mentions
    • Identify which components are used frequently
    • Find custom implementations (should use system)
  2. Identify gaps:

    • Patterns appearing in multiple places
    • Requested components
    • Missing design system coverage
  3. Check consistency:

    • Are teams using system components?
    • Custom implementations vs. system
    • Deviation from standards
  4. Track adoption:

    • % of projects using design system
    • Common reasons for not using
    • Barriers to adoption
  5. Recommend improvements:

    • Components to add
    • Documentation needs
    • Adoption initiatives

Output Format

# Design System Audit

**Date:** [Today]
**Projects reviewed:** [Count]

## Adoption Metrics
- Design system usage: [X]%
- Most used components: [List]

## Gaps Identified
1. [Pattern/Component needed] - Appears in [X] projects
2. [Gap description]

## Consistency Issues
- [Issue]: [Projects affected]

## Recommendations
1. Build [Component] - Priority: [High/Medium/Low]
2. [Recommendation]

## Roadmap Suggestions
- [Component] - Justification: [Why needed]