Agent skill

Component Reuse

by bitovi in bitovi/ai-enablement-prompts

Ensure existing UI components are reused before creating new ones.

MITAuto-check passed

Install Component Reuse

skills CLI
$ npx skills add bitovi/ai-enablement-prompts --skill component-reuse -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitovi/ai-enablement-prompts component-reuse --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/react/skills/component-reuse .claude/skills/component-reuse && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
component-reuse
GitHub stars
121
Token cost
~662 tokens
SKILL.md length
260 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Ensure existing UI components are reused before creating new ones.

  • Works in 5 steps: Extract Component Names → Search for Exact Names → Search for Variations → …
  • SKILL.md covers When to Use, Purpose, Workflow and Common Mistakes, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Component Reuse is an agent skill from bitovi/ai-enablement-prompts. Ensure existing UI components are reused before creating new ones. Must run BEFORE any UI implementation. Audits the codebase for matching components and reports whether to REUSE, WRAP, or CREATE.

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Prompts Bitovi uses for software development. The licence is MIT.

Example prompts

  • “/component-reuse”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Extract Component Names
  2. Search for Exact Names
  3. Search for Variations
  4. Output Audit Table
  5. Take Action

What it can do on your machine

Read from SKILL.md and the folder at commit df229b1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Component Reuse loads about 662 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 260 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~662

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitovi/ai-enablement-prompts at commit df229b1, republished under its MIT licence (© bitovi). 260 words, ~662 tokens.

Download SKILL.mdSave it as .claude/skills/component-reuse/SKILL.md (or your agent's skills folder).
name
component-reuse
description
Ensure existing UI components are reused before creating new ones. Must run BEFORE any UI implementation. Audits the codebase for matching components and reports whether to REUSE, WRAP, or CREATE.

Skill: Component Reuse Audit

A gate skill that enforces checking for existing components before creating new ones.

When to Use

BEFORE any UI implementation task. This skill must run before:

  • Creating a new component
  • Building a new page or feature
  • Implementing a Figma design

Purpose

Prevent duplicate components by auditing what already exists.

Workflow

Step 1: Extract Component Names

From the design or requirements, list every UI element needed:

  • Buttons, inputs, selects, checkboxes
  • Cards, tables, lists, badges
  • Dialogs, modals, popovers
  • Layout containers, navigation elements
Step 2: Search for Exact Names
bash
# Search for each component by name
find src/components -name "*.tsx" | head -50
grep -rn "export.*Button\|export.*Card\|export.*Dialog" src/components/ --include="*.tsx"
Step 3: Search for Variations

Look for alternate names and similar components:

bash
# Search for button variants
grep -rn "Button\|Btn\|ActionButton\|SubmitButton" src/components/ --include="*.tsx"

# Search for card variants
grep -rn "Card\|Panel\|Tile\|Container" src/components/ --include="*.tsx"
Step 4: Output Audit Table

Create a decision table:

Needed ComponentFound MatchLocationDecision
Button✅ Buttonsrc/components/ui/ButtonREUSE
StatusBadge⚠️ Badge (partial)src/components/ui/BadgeWRAP — extend with status colors
Timeline❌ None—CREATE
Step 5: Take Action

For each decision:

  • REUSE: Import and use the existing component directly
  • WRAP: Create a thin wrapper around an existing component that adds the missing functionality
  • CREATE: Only create a new component if nothing similar exists

Common Mistakes

  • ❌ Creating a new StatusBadge when Badge exists and can accept a variant prop
  • ❌ Building a custom dialog when the UI library provides one
  • ❌ Copying a component instead of importing it
  • ❌ Skipping this audit because "it's faster to just build it"

Quality Checklist

  • Every UI element in the design has been audited
  • All existing components in src/components/ have been checked
  • UI library components (shadcn, MUI, etc.) have been checked
  • Decision table is complete with REUSE/WRAP/CREATE for each element
  • No REUSE or WRAP was incorrectly marked as CREATE

© bitovi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/react/skills/component-reuse of bitovi/ai-enablement-prompts.

Open the folder on GitHubat commit df229b1

Compare with similar skills

Component Reuse next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Component Reuse compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Component Reuse this skillbitovi/ai-enablement-prompts121—~662Automated safety check: PassMIT
Reuse Checkpolarsource/polar10k—~1.2kAutomated safety check: PassMIT
Ripwire Reuse Firstredhat-et/ripwire2.4k—~1.3kAutomated safety check: NotesApache-2.0
Ensure Pipelines Hostmicrosoft/power-platform-skills972—~23kAutomated safety check: NotesMIT
Code Reusespinspire/pocketbase-sveltekit-starter511—~2.5kAutomated safety check: NotesMIT
Ensure All Tests Pass After Code ChangesZaxbyHub/opencode-swarm490—~314Automated safety check: PassMIT

Similar skills

  • Reuse Check

    polarsource/polar

    Check a diff for code that reinvents something Polar already has — a kit helper, a shared Pydantic type, a repository method, an Orbit component, an existing model property.

    10k GitHub stars~1.2k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Ripwire Reuse First

    redhat-et/ripwire

    About to write ONE symbol (even a 'quick' one-liner) or add a dependency: reuse before you reinvent.

    2.4k GitHub stars~1.3k tokensUpdated today
    Auto-check: notes
  • Ensure Pipelines Host

    microsoft/power-platform-skills

    Official

    Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs.

    972 GitHub stars~23k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Code Reuse

    spinspire/pocketbase-sveltekit-starter

    A skill your agent uses when building a UI component, PocketBase hook, page, or app feature and there is proven code to copy from the reference repos.

    511 GitHub stars~2.5k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check: notes
  • ensure all tests pass after code changes. An agent skill from ZaxbyHub/opencode-swarm.

    490 GitHub stars~314 tokensUpdated today
    Auto-check passed
  • Ensure Quality

    gambitph/Stackable

    Local quality gate for the current worktree: review for risk/correctness (break, leak, undo intent), standards, spec, and anti-slop; then test, document, lint.

    350 GitHub stars~1.5k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from bitovi/ai-enablement-prompts

All 40 skills in this repo
  • Component Registry

    bitovi/ai-enablement-prompts

    Track reusable UI components and unextracted patterns. An agent skill from bitovi/ai-enablement-prompts.

    121 GitHub stars~597 tokensUpdated 27 days ago
    Auto-check passed
  • Computed Styles

    bitovi/ai-enablement-prompts

    Extract and compare computed CSS styles between a baseline URL and a dev/Storybook URL using Playwright MCP evaluate calls.

    121 GitHub stars~2.4k tokensUpdated 27 days ago
    Auto-check passed
  • Create Plugin

    bitovi/ai-enablement-prompts

    A skill your agent uses when the user asks to "create a plugin", "add a plugin", "make a new plugin", "build a plugin", or wants to package skills into an installable plugin for this marketplace.

    121 GitHub stars~2k tokensUpdated 27 days ago
    Auto-check passed
  • Create React Modlet

    bitovi/ai-enablement-prompts

    Create React components, hooks, or utilities following the modlet pattern.

    121 GitHub stars~2.1k tokensUpdated 27 days ago
    Auto-check passed
  • Create Skill

    bitovi/ai-enablement-prompts

    A skill your agent uses when the user asks to "create a skill", "add a skill", "make a new skill", "build a skill", or wants to automate a repeated workflow into a reusable prompt.

    121 GitHub stars~1.6k tokensUpdated 27 days ago
    Auto-check passed
  • Create Skill

    bitovi/ai-enablement-prompts

    Create new Agent Skills for this project. An agent skill from bitovi/ai-enablement-prompts.

    121 GitHub stars~1.7k tokensUpdated 27 days ago
    Auto-check passed

Questions about Component Reuse

What does Component Reuse do?

Ensure existing UI components are reused before creating new ones. Component Reuse is an agent skill from bitovi/ai-enablement-prompts. Ensure existing UI components are reused before creating new ones.

How do I install Component Reuse in Claude Code?

Run `npx skills add bitovi/ai-enablement-prompts --skill component-reuse -a claude-code`. Or copy the skill folder (plugins/react/skills/component-reuse in bitovi/ai-enablement-prompts) into .claude/skills/component-reuse in your project. Claude Code loads it when a task matches its description.

How do I install Component Reuse in Codex?

Run `npx skills add bitovi/ai-enablement-prompts --skill component-reuse -a codex`. Or copy the skill folder (plugins/react/skills/component-reuse in bitovi/ai-enablement-prompts) into .agents/skills/component-reuse in your project. Codex loads it when a task matches its description.

Can I use Component Reuse in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitovi/ai-enablement-prompts --skill component-reuse -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/component-reuse, .gemini/skills/component-reuse, .github/skills/component-reuse and .opencode/skills/component-reuse in your project.

What does Component Reuse need to run?

SKILL.md names no scripts, command-line tools or credentials: Component Reuse is instructions for the agent only.

Does Component Reuse access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Component Reuse safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Component Reuse use?

Component Reuse is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Component Reuse use?

About 662 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Component Reuse?

Skills that share tags, products or a category with Component Reuse: Reuse Check (polarsource/polar, 10k stars), Ripwire Reuse First (redhat-et/ripwire, 2.4k stars), Ensure Pipelines Host (microsoft/power-platform-skills, 972 stars) and Code Reuse (spinspire/pocketbase-sveltekit-starter, 511 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Component Reuse?

bitovi (a GitHub organization) maintains it in bitovi/ai-enablement-prompts, which has 121 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on September 11, 2026.

Source: bitovi/ai-enablement-prompts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.