component-audit

Audit design system component libraries for usage, complexity, duplication, and coverage gaps.

155|7|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/murphytrueman/design-system-ops --skill component-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-audit
Source: https://github.com/murphytrueman/design-system-ops/tree/main/skills/component-audit
Command: npx skills add https://github.com/murphytrueman/design-system-ops --skill component-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the silent accumulation and drift within component libraries, which can lead to bloat, duplication, and outdated components, ultimately slowing down development and increasing maintenance overhead.

Core Features & Use Cases

  • Comprehensive Auditing: Analyzes component libraries across usage signals, complexity distribution, duplication, and coverage gaps.
  • Actionable Insights: Produces a prioritized list of findings and recommendations for remediation.
  • Dependency Mapping: Generates a composition dependency graph to understand the impact of changes.
  • Use Case: A design system lead can use this Skill to identify components that are rarely used, find redundant components that can be consolidated, and discover missing components that teams are building locally, providing a clear roadmap for library improvement.

Quick Start

Use the component-audit skill to assess the health of my design system's component library.

Frequently Asked Questions about component-audit

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

FAQPage Schema
How do I audit a design system component library for health and identify duplication?

To audit a design system component library for health, analyze usage signals, complexity distribution, duplication, and coverage gaps to generate actionable remediation recommendations and a composition dependency graph.

Can I pull component data automatically from Figma, npm, and Storybook for a library audit?

Yes, you can pull component data automatically from Figma, npm, Storybook, and documentation platforms to assess library health, identify coverage gaps, and discover missing components teams are building locally.

What is component library drift and how does a dependency graph help with impact analysis?

Component library drift is the silent accumulation of bloat and outdated components. A composition dependency graph maps these relationships to understand the impact of changes and prioritize remediation efforts.

What is the best way to find redundant components in a design system?

The best way to find redundant components is to audit the library for duplication and usage signals, producing a prioritized list of findings that identifies components for consolidation to reduce maintenance overhead.

Does a component audit work for identifying missing components in documentation platforms?

Yes, auditing component coverage gaps works with documentation platforms to discover missing components that teams are building locally, providing a clear roadmap for library improvement and documentation alignment.

Why does component library bloat slow down development and increase maintenance overhead?

Component library bloat slows development because silent accumulation and drift create duplication and outdated components, increasing maintenance overhead and requiring a comprehensive audit to identify and resolve.