component-catalog
Skill7 starsChanged 4 months agoMITView on GitHub
Decide which interface components to reuse, extend, or add from observed product patterns and the existing codebase. Use for component-library coverage or design-to-code planning.
In this repository95 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditSkill
- agent-memory-profilesSkill
- agent-messaging-gatewaySkill
- agent-session-checkpointsSkill
- agent-skill-migrationSkill
- ai-interaction-designSkill
- animation-craftSkill
- animation-vocabularySkill
- apple-designSkill
- apple-desktop-automationSkill
- approval-sandbox-policiesSkill
- atomic-designSkill
- better-colorsSkill
- better-typographySkill
- better-uiSkill
- browser-research-agentSkill
- codex-opsSkill
- competitive-intelSkill
- content-designSkill
- creative-rendering-auditSkill
- cron-agent-workflowsSkill
- dashboard-from-researchSkill
- data-synthesisSkill
- design-extractSkill
- design-measurement-and-experimentationSkill
- design-sandbox-proofSkill
- design-system-referenceSkill
- design-systemsSkill
- design-to-code-handoffSkill
- dialkitSkill
- docker-environmentsSkill
- emil-design-engSkill
- figma-auditSkill
- figma-code-connectSkill
- figma-create-fileSkill
- figma-design-systemsSkill
- figma-ds-rulesSkill
- figma-generate-designSkill
- figma-generate-librarySkill
- figma-implement-designSkill
- figma-library-builderSkill
- figma-plugin-apiSkill
- figma-prototypeSkill
- figma-syncSkill
- figma-useSkill
- figma-web-captureSkill
- find-animation-opportunitiesSkill
- flutter-genSkill
- gateway-ops-observabilitySkill
- hermes-agent-bridgeSkill
- hyperframes-videoSkill
- improve-animationsSkill
- information-architectureSkill
- interaction-designSkill
- interface-craft-gateSkill
- interview-researchSkill
- ios-app-intentsSkill
- ios-performance-debuggingSkill
- linear-syncSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use for a bounded product surface with repeated patterns, or when a supplied design does not clearly map to existing components.
- Distinctive: line 15
Use the component catalog as a vocabulary check.
- Distinctive: line 18
Verify the decision with representative callers and a Storybook story or existing component preview.
≈ “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 catalog
When to use
Use for a bounded product surface with repeated patterns, or when a supplied design does not clearly map to existing components. For implementation of one Figma or Paper selection, use design-to-code-handoff first. Do not use a universal inventory as a build list.
Workflow
- Inventory actual routes, workflows, states, and repeated patterns. Read local instructions, component APIs, tokens, existing stories or component previews, and consumers. Record where each candidate appears.
- Use the component catalog as a vocabulary check. Identify the smallest semantic component that covers observed behavior. Do not assume Atomic Design or shadcn/ui is installed; use either only when the repository follows it.
- For each candidate choose reuse, extend, or new. Reuse when semantics, interaction, accessibility, and states fit. Extend when the API can support a missing state without breaking current callers. Add only when the needed behavior has a distinct contract. Record the alternative considered and why it fails.
- Specify the public API, supported variants, states, composition, keyboard behavior, focus management, responsive behavior, and token dependencies. Keep visual variants separate from semantic behavior.
- Verify the decision with representative callers and a Storybook story or existing component preview. Test keyboard and touch interaction for controls. Check that the proposed API covers observed states without one-off overrides.
Output
| Pattern and evidence | Existing component | Decision and reason | Required states and contract | Verification | Unresolved |
Name missing source evidence or unavailable previews. A component count is not evidence of coverage; report the observed workflows and states that are covered instead.
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.