seemseam Component Composition
Use this skill before introducing new UI primitives or composing a page from an existing component system.
Workflow
- Inspect project-local components, Storybook stories, docs, exports, and examples.
- Identify the smallest set of components needed for the surface and states.
- Verify props, variants, accessibility behavior, and styling conventions from source or docs.
- Use shadcn or registry components only when the project stack and ownership model support them.
- Use Radix-like primitives as behavior references when local components need accessible interaction patterns.
- Avoid broad new UI-library recommendations when the target project already has a component system.
Output
Return:
- component inventory used
- composition plan
- missing component or state gaps
- prop/API assumptions verified from source
- implementation notes
Do not invent props or import paths from component names.