component-reuse-planner — Claude Code skill: how to install
component-reuse-planner is a Claude Code skill that decides whether to reuse, extend, or create UI components. The decision relies on the governed project inventory and approved states.
MIT ★ 529 updated 2026-11-17
npx skills add ShuaiMXu/happyhands --skill component-reuse-planner -a claude-codeWhat component-reuse-planner does
The skill evaluates proposed UI changes against a governed component inventory to prevent drift. It prioritizes approved components and treats observed codebase instances as candidates. A new component is introduced only when existing semantics do not fit, because matching names alone do not establish equivalence.
When updating a shared component, the workflow determines direct consumers and applicable variant states. Output includes structured evidence, findings, proposed updates, and limitations. If required inputs or reviews are absent, the skill outputs a needs-evidence status without inventing scores or universal rules.
What it helps with
- decide whether to extend or create a UI component
- identify direct consumers of a shared component
- verify proposed changes against the component inventory
- prevent UI drift across existing interface variants
Example prompts for the agent
- Check the component inventory to decide if we need a new modal button.
- Analyze changes to Button and list all affected consumers.
- Evaluate whether to reuse or extend the product card component.
How to install component-reuse-planner
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill component-reuse-planner -a claude-code2Manually: put the files in place
~/.claude/skills/component-reuse-planner/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/component-reuse-planner/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill component-reuse-planner -a codex2Manually: put the files in place
.agents/skills/component-reuse-planner/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill component-reuse-planner -a cursor2Manually: put the files in place
.cursor/skills/component-reuse-planner/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ShuaiMXu/happyhands skills/product-design/component-reuse-planner2Manually: put the files in place
.github/skills/component-reuse-planner/SKILL.md1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill component-reuse-planner -a gemini-cli2Platform CLI
gemini skills install https://github.com/ShuaiMXu/happyhands --path skills/product-design/component-reuse-plannerManually: put the files in place
.devin/skills/component-reuse-planner/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-reuse-planner
How to install component-reuse-planner in Claude Code?
Run npx skills add ShuaiMXu/happyhands --skill component-reuse-planner -a claude-code in your terminal.
What does component-reuse-planner do?
It checks proposed UI changes against the component inventory to decide whether to reuse, extend, or build a new component.
What inputs does component-reuse-planner require?
The skill requires the component inventory, approved and deprecated states, and recorded findings from the code.
Source text
SKILL.md · MIT
--- name: component-reuse-planner description: "Decide whether a proposed change should reuse, extend or introduce a component using the governed project inventory." --- # Component Reuse Planner Reduce component drift while preserving legitimate variants. ## Required evidence - selected finding - component inventory - approved and deprecated states ## Decisions - Prefer approved components - Treat observed components as candidates - Propose a new component only when existing semantics do not fit - For a changed shared component, identify its concrete consumers and applicable variants/states. Use source-bound root instance capture evidence where available; a parent screenshot does not certify descendants. Propose missing captures through the existing scoped plan confirmation instead of inventing coverage or adding markers solely to pass a check. ## Boundary Name similarity alone does not prove component equivalence. 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