What problem does it solve?
In the SEED Design monorepo, a single component is spread across Rootage token definitions, style recipes, headless logic, React and Lynx implementations, package exports, registry entries, docs, examples, and tests. Finding every connected file before making a change is slow and error-prone. This Skill scans the current checkout and returns a deterministic JSON map of every surface tied to one component.
Core Features & Use Cases
- Component connection map: Given a component name (PascalCase or kebab-case), it locates Rootage sources, recipe sources, generated outputs, headless code, React/Lynx implementations, package export chains, registry entries, docs, examples, and tests.
- Match state handling: Returns
matched, ambiguous, or not-found, and for ambiguous names lists exact candidate components to re-query instead of guessing.
- Source vs. generated separation: Clearly distinguishes files you edit directly (Rootage, recipes) from generated outputs you must not modify.
- Use Case: Before changing ProgressCircle, run the script to see its React and Lynx implementations, public export chain, and Storybook stories so you can assess impact and platform parity.
Quick Start
Ask the AI to run the component map for a component, for example: "Map the ProgressCircle component in the SEED Design repo so I can see all its sources and public surfaces."