Skip to main content
skill CX Codex

component-inventory — Claude Code skill: features and install

component-inventory is a Claude Code skill that maps components to source paths, variants, composition, and known consumers. It supports reuse decisions and drift analysis.

MIT ★ 529 updated 2026-11-17

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ShuaiMXu/happyhands --skill component-inventory -a claude-code
Open on GitHub

What component-inventory does

The skill builds a component inventory from source files, exports, imports, and rendered examples when available. It distinguishes primitives from product patterns, records sources and consumers, and marks variants as observed or inferred. Its output contains structured evidence, findings, suggested updates, and limitations.

Static imports can miss composition that happens at runtime. The skill resolves tsconfig and jsconfig aliases against a source snapshot, but that does not establish that a bundler or runtime uses the same mappings. Consumer traversal stops at 32 edges per path and 256 modules per component; a truncated graph leaves the affected scope incomplete. A path through a barrel shows module reachability, not that a specific component renders on a page.

What it helps with

  • map components to their source files
  • separate primitives from product patterns
  • identify known consumers and analysis limits

Example prompts for the agent

  • Build a component inventory for this project with source paths and known consumers.
  • Separate primitives from product patterns and label variants as observed or inferred.
  • Trace which modules consume these components and report the limits of the analysis.

How to install component-inventory

1Skills CLI (Vercel)

npx skills add ShuaiMXu/happyhands --skill component-inventory -a claude-code

2Manually: put the files in place

~/.claude/skills/component-inventory/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/component-inventory/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about component-inventory

How do I install component-inventory in Claude Code?

Run npx skills add ShuaiMXu/happyhands --skill component-inventory -a claude-code. The skill file is at ~/.claude/skills/component-inventory/SKILL.md.

What does component-inventory do?

It maps components to their source paths, variants, and known consumers. The inventory supports reuse decisions and drift analysis.

Does a consumer path prove that a component renders on a page?

No. A path through a barrel establishes module reachability, not that a particular component renders. Static imports can also miss runtime composition.

Source text

SKILL.md · MIT
---
name: component-inventory
description: "Build a component inventory with source paths, variants, composition and known consumers."
---

# Component Inventory

Create the component map needed for reuse decisions and drift analysis.

## Required evidence

- component sources
- exports and imports
- rendered examples when available

## Decisions

- Record source and consumers
- Separate primitives from product patterns
- Mark inferred variants observed

## Boundary

Static imports may miss runtime composition.

Version 0.6.0 resolves explicit tsconfig/jsconfig paths and baseUrl against the recorded source snapshot, including local JSONC extends, referenced projects and nested project scope. Keep configInputs hashes with every resolved alias. This lookup is not proof that a bundler/runtime applies the same mapping. Missing package bases, absolute config paths, overlapping scopes, truncated snapshots, missing targets and ambiguous module candidates remain needs-inspection records. Do not execute target configuration files or silently infer a package config from installed dependencies.

Transitive consumer traversal is bounded to 32 edges per path and 256 modules per component. A consumerGraphTruncated flag means the affected scope is incomplete; inspect or narrow the source scope before proposing a complete review.

Use consumerEvidence file/line references and potentialConsumers paths to inspect affected modules. A transitive path through a barrel is module reachability, not proof that a particular exported component is rendered. Do not label those pages reviewed or add them to a confirmed capture plan automatically. Preserve moduleResolutionIssues for aliases, missing or ambiguous modules and dynamic expressions; absence of a resolved edge is not evidence of no consumers. Type-only declarations and commented examples are not runtime consumers. CommonJS require candidates still need binding inspection.

Return structured evidence, findings, proposed updates and limitations. Use `needs-evidence` when required inputs or professional review are missing. Never invent an Experience Score or promote a project observation into a universal rule.

© ShuaiMXu · MIT · ShuaiMXu/happyhands

Similar skills

All skills for Frontend and UI →
component-family-consistency dembrandt component-family-consistency is a Claude Code skill that keeps buttons, fields, badges, and related UI elements visually aligned. It activates on component-library work and design-system reviews. CX Codex +1 1,000installs component-spec Owl-Listener component-spec is a Claude Code skill that documents library components, including their props, states, variants, and accessibility. It activates when defining a component for a design system. CX Codex +1 2,500installs component-canvas ibelick component-canvas builds a full-screen canvas where your project's components show up as they actually behave, with pan, zoom and variant comparisons. Useful when you need the whole design system in one view. CX Codex +1 1,800installs ai-component-metadata thedesignproject The ai-component-metadata Claude Code skill creates structured metadata for design system components used in AI-generated interfaces. It runs during component analysis and records how each component should be composed and used. CX Codex +1 ★ 107repo stars ux-component Laith Aljunaidy ux-component — a slash command from the ux plugin that forwards the call to /ux-design --component to generate a single UI component. It is a temporary alias, removed in 4.1. CX Codex +1 ★ 110repo stars component-docs arla6ka component-docs is a Claude Code skill that writes one UI component’s docs from code, stories, and real call sites. It responds to requests about component usage and states. CX Codex +1 582installs

From the same set34

The whole set →
content-design-reviewer content-design-reviewer is a Claude Code skill that checks interface labels and guidance for clarity and consistency. It ties findings to a user task and its outcome. CX Codex +1 ★ 529repo stars interaction-reviewer interaction-reviewer is a Claude Code skill that reviews interaction flow and control behavior. It detects missing feedback, unnecessary steps, and unsafe UI state transitions. CX Codex +1 ★ 529repo stars information-architecture-reviewer information-architecture-reviewer is a Claude Code skill that audits navigation and content hierarchy against user tasks. It identifies dead ends and ambiguous labels along target flows. CX Codex +1 ★ 529repo stars foundation-extractor Foundation-extractor is a Claude Code skill that builds an inventory of design tokens and component sources. It maps existing design elements in a repository before proposing foundation updates. CX Codex +1 ★ 529repo stars visual-qa-evaluator Visual-qa-evaluator is a Claude Code skill that prepares evidence for visual QA and regression analysis. It supports matching interface states to evaluate design changes. CX Codex +1 ★ 529repo stars brand-foundation-extractor brand-foundation-extractor is a Claude Code skill that gathers candidate brand principles, voice cues, and visual assets from project files and rendered content. It keeps each finding tied to its source. CX Codex +1 ★ 529repo stars token-contrast-auditor The token-contrast-auditor skill for Claude Code verifies color pair contrast against WCAG standards. It runs during project analysis to check design tokens and CSS styles. CX Codex +1 ★ 529repo stars pattern-library-curator pattern-library-curator is a Claude Code skill that gathers accepted interface solutions into a project pattern library. It checks recurring decisions for evidence before they are treated as reusable patterns. CX Codex +1 ★ 529repo stars

Project sponsors

Companies that keep this analytics open