Component Audit

by murphytrueman

Component Audit is a Data skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22

View source on GitHub Download repo ZIP

claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills

Install in seconds

Install Component Audit

Copy Component Audit into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/component-audit ~/.claude/skills/component-audit

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/component-audit/SKILL.md in murphytrueman/design-system-ops
Installs to: ~/.claude/skills/component-audit
Collection: One of 25 skills cataloged from this repository
Category: Data — 796 skills

What Component Audit does

Component Audit audits a design system component library for usage, complexity, duplication, and coverage gaps. Use it to assess what exists, what is unused, and where the library needs cleanup or expansion.

Component Audit is cataloged under Data on DirSkills. Component Audit comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Excerpt

Component audit

A skill for auditing a design system's component library across four dimensions: usage signals, complexity distribution, duplication, and coverage gaps. Produces an inventory with tiered findings and a prioritised action list.

Context

Component libraries accumulate silently. New components arrive through contributions. Old components persist because nobody wants to be the one who removes them. Variants proliferate because each edge case adds one more. The result is a library that grows in mass without growing proportionally in value.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Component Audit

What else does murphytrueman publish alongside Component Audit?
Component Audit is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Accessibility Per Component and Adoption Report. Each one is a separate skill with its own page in this directory, installs the same way Component Audit does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.
How does Component Audit compare to other Data skills?
Component Audit ranks #742 by stars among the 796 Data skills in this catalog. The most-starred ones next to it are Benchmark Methodology, Jupyter Notebook and Solana. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Component Audit against them. Open each page to compare what they document and how they install.