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
npx skills add ShuaiMXu/happyhands --skill component-inventory -a claude-codeWhat 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-code2Manually: put the files in place
~/.claude/skills/component-inventory/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/component-inventory/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill component-inventory -a codex2Manually: put the files in place
.agents/skills/component-inventory/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill component-inventory -a cursor2Manually: put the files in place
.cursor/skills/component-inventory/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ShuaiMXu/happyhands skills/product-design/component-inventory2Manually: put the files in place
.github/skills/component-inventory/SKILL.md1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill component-inventory -a gemini-cli2Platform CLI
gemini skills install https://github.com/ShuaiMXu/happyhands --path skills/product-design/component-inventoryManually: put the files in place
.devin/skills/component-inventory/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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