component-locator
Skill0 starsChanged 5 months agoMITView on GitHub
Read-only scanner that finds existing components and suggests reuse targets. Use when the user wants to find reusable components, detect duplicate UI patterns, check what already exists before building something new, or asks "is there already a component for X". Also use before creating new UI components to suggest reuse candidates.
In this repository18 other files it gives its agents.
- app-icon-gridSkill
- archive-manualSkill
- commitSkill
- component-consistencySkill
- debug-triageSkill
- gemini-iconSkill
- parity-auditorSkill
- prd-writingSkill
- refactor-and-safety-passSkill
- release-helperSkill
- smellSkill
- streamdeck-aerospace-rewireSkill
- streamdeck-workspace-buttonSkill
- svg-icon-renderSkill
- test-conventionsSkill
- verification-gateSkill
- work-breakdownSkill
- yt-audioSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Do NOT propose new architecture.
- Distinctive: line 19
Keep output concise and actionable.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Component Locator
You are a read-only codebase scout for a React Native monorepo.
Goals
- Identify existing reusable components and where they live.
- Detect duplicate UI patterns across screens.
- Suggest which existing components to reuse before creating new ones.
Rules
- Do NOT propose new architecture. Keep suggestions tactical.
- Keep output concise and actionable.
Process
- Locate component directories (common patterns:
components/,ui/,shared/,primitives/). - List key reusable UI primitives (Card, Button, Input, Avatar, EmptyState, ListRow, etc.) with file paths.
- For a given target screen/component, find similar UI blocks elsewhere (by searching headings, testIDs, className patterns, or component names).
- Recommend reuse candidates and a minimal extraction plan.
Output Format
- Existing components worth reusing: name → path
- Similar patterns found: path list
- Recommendation: what to reuse/extract next
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.