Agent skill

Component Registry

by bitovi in bitovi/ai-enablement-prompts

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

MITAuto-check passed

Install Component Registry

skills CLI

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

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

GitHub CLI

$ gh skill install bitovi/ai-enablement-prompts component-registry --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-registry .claude/skills/component-registry && 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/

Paste into Claude Code

Install the "component-registry" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/react/skills/component-registry into .claude/skills/component-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-registry", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/react/skills/component-registry

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add bitovi/ai-enablement-prompts --skill component-registry -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install bitovi/ai-enablement-prompts component-registry --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "component-registry" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/react/skills/component-registry into .agents/skills/component-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-registry", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add bitovi/ai-enablement-prompts --skill component-registry -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install bitovi/ai-enablement-prompts component-registry --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "component-registry" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/react/skills/component-registry into .cursor/skills/component-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-registry", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/bitovi/ai-enablement-prompts.git --path plugins/react/skills/component-registry

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add bitovi/ai-enablement-prompts --skill component-registry -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install bitovi/ai-enablement-prompts component-registry --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "component-registry" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/react/skills/component-registry into .gemini/skills/component-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-registry", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install bitovi/ai-enablement-prompts component-registry

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add bitovi/ai-enablement-prompts --skill component-registry -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "component-registry" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/react/skills/component-registry into .github/skills/component-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-registry", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add bitovi/ai-enablement-prompts --skill component-registry -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install bitovi/ai-enablement-prompts component-registry --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "component-registry" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/react/skills/component-registry into .opencode/skills/component-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "component-registry", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: component-registry
GitHub stars: 121
Token cost: ~597 tokens
SKILL.md length: 136 words
Files: 1
Skills in repo: 40
Repo updated: Sep 11, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Works in 5 steps: Run the scan commands above → Update usage counts for existing entries → Add new patterns discovered → …
Auditing components
SKILL.md covers Purpose, Registry Location, Registry Format and Maintenance Workflow, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Component Registry is an agent skill from bitovi/ai-enablement-prompts. Track reusable UI components and unextracted patterns. Maintains a REGISTRY.md inventory of extracted components and patterns that need extraction. Use when auditing components, planning extractions, or checking what components exist.

Its SKILL.md is about 600 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.

When your agent uses it

Auditing components
Planning extractions
Checking what components exist

Example prompts

“/component-registry”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Run the scan commands above
Update usage counts for existing entries
Add new patterns discovered
Remove patterns that have been extracted
Prioritize extraction candidates (High = 5+ uses, Medium = 3-4 uses)

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 markdown and 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 Registry loads about 597 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 136 words of instructions outside code blocks.

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

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). 136 words, ~597 tokens.

Download SKILL.mdSave it as .claude/skills/component-registry/SKILL.md (or your agent's skills folder).

name: component-registry
description: Track reusable UI components and unextracted patterns. Maintains a REGISTRY.md inventory of extracted components and patterns that need extraction. Use when auditing components, planning extractions, or checking what components exist.

Skill: Component Registry

Maintain a living inventory of UI components and patterns in the project.

Purpose

The component registry tracks:

✅ Extracted components — reusable components that exist in the shared components directory
⚠️ Needs extraction — patterns used in multiple places that should be extracted
Usage counts — how many times each component/pattern is used

Registry Location

Store the registry at .github/skills/component-registry/REGISTRY.md or a project-appropriate location.

Registry Format

markdown

# Component Registry

## ✅ Extracted Components

| Component | Location | Usage Count | Description |
|-----------|----------|-------------|-------------|
| Button | src/components/ui/Button | 24 | Primary action button with variants |
| Card | src/components/ui/Card | 12 | Content card container |

## ⚠️ Needs Extraction

| Pattern | Found In | Count | Priority |
|---------|----------|-------|----------|
| Status badge | JobList, UserList, Dashboard | 8 | High |
| Search input | JobsPage, UsersPage | 4 | Medium |

Maintenance Workflow

Scanning for Patterns

Run these commands to find common patterns:

bash

# Find repeated button patterns
grep -rn "className.*btn\|<button" src/ --include="*.tsx" | wc -l

# Find repeated card patterns  
grep -rn "className.*card\|className.*rounded.*shadow" src/ --include="*.tsx" | wc -l

# Find repeated form input patterns
grep -rn "className.*input\|<input" src/ --include="*.tsx" | wc -l

# Find repeated badge/tag patterns
grep -rn "className.*badge\|className.*tag\|className.*pill" src/ --include="*.tsx" | wc -l

Updating the Registry

Run the scan commands above
Update usage counts for existing entries
Add new patterns discovered
Remove patterns that have been extracted
Prioritize extraction candidates (High = 5+ uses, Medium = 3-4 uses)

Integration with Other Skills

extract-ui-component: Use to extract patterns marked ⚠️
implement-feature: Check registry before building new UI
component-reuse: Enforce reuse of ✅ components

Files

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

Open the folder on GitHubat commit df229b1

Compare with similar skills

Component Registry 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 Registry compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Component Registry this skillbitovi/ai-enablement-prompts	121	—	~597	Automated safety check: Pass	MIT	27 days ago
Wiki Maintaineropenclaw/openclaw	392k	1 repos	~462	Automated safety check: Pass	MIT	today
Obsidian Vault Maintaineropenclaw/openclaw	392k	2 repos	~262	Automated safety check: Pass	MIT	today
Openclaw PR Maintaineropenclaw/openclaw	392k	—	~2.2k	Automated safety check: Pass	MIT	today
Open Source Maintainer Assistantslopus/happy	24k	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Maintainer Reviewopenai/openai-agents-python	30k	—	~8.9k	Automated safety check: Pass	MIT	today

Similar skills

Wiki Maintainer
openclaw/openclaw
Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
392k GitHub starsUsed in 1 repo~462 tokens
Knowledge ManagementAuto-check passed
Obsidian Vault Maintainer
openclaw/openclaw
Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.
392k GitHub starsUsed in 2 repos~262 tokens
Knowledge ManagementAuto-check passed
Openclaw PR Maintainer
openclaw/openclaw
Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.
392k GitHub stars~2.2k tokensUpdated today
DevelopmentAuto-check passed
Open Source Maintainer Assistant
slopus/happy
Helps maintain the slopus/happy open source project by triaging issues, drafting closing comments, finding duplicates and checking fixes, with approval before anything is posted.
24k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Maintainer Review
openai/openai-agents-python
Official
Assess a GitHub issue or PR for demonstrated need, supported alternatives, correctness, and maintainer action.
30k GitHub stars~8.9k tokensUpdated today
DevelopmentAuto-check passed
Deerflow Maintainer Orchestrator
bytedance/deer-flow
A skill your agent uses when a DeerFlow maintainer needs comment-only GitHub issue or PR handling: resolve issue/PR scopes with gh, analyze issues, post or draft issue comments, perform PR review…
83k GitHub stars~5.4k tokensUpdated today
DevelopmentAuto-check passed

More from bitovi/ai-enablement-prompts

All 40 skills in this repo

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
Cross Package Types
bitovi/ai-enablement-prompts
Type flow patterns for tRPC + Prisma monorepos. An agent skill from bitovi/ai-enablement-prompts.
121 GitHub stars~1.1k tokensUpdated 27 days ago
Auto-check passed

Questions about Component Registry

What does Component Registry do?

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

When should I use Component Registry?

Component Registry fits situations like: auditing components; planning extractions; checking what components exist.

How do I install Component Registry in Claude Code?

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

How do I install Component Registry in Codex?

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

Can I use Component Registry 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-registry -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-registry, .gemini/skills/component-registry, .github/skills/component-registry and .opencode/skills/component-registry in your project.

What does Component Registry need to run?

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

Does Component Registry 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 Registry 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 Registry use?

Component Registry 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 Registry use?

About 597 tokens (SKILL.md is roughly 2.4k 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 Registry?

Skills that share tags, products or a category with Component Registry: Wiki Maintainer (openclaw/openclaw, 392k stars), Obsidian Vault Maintainer (openclaw/openclaw, 392k stars), Openclaw PR Maintainer (openclaw/openclaw, 392k stars) and Open Source Maintainer Assistant (slopus/happy, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Component Registry?

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.

Install Component Registry

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill: Component Registry

Purpose

Registry Location

Registry Format

Maintenance Workflow

Scanning for Patterns

Updating the Registry

Integration with Other Skills

Files

Compare with similar skills

Similar skills

More from bitovi/ai-enablement-prompts

Questions about Component Registry