Choose one branch according to the result the request wants, and read only that branch's reference. The lookup, comparison, and token branches are read-only. Return the result and stop; do not move to another branch unless the user requests implementation.
| Request result | Reference to read | Execution |
|---|---|---|
| Only the implementation, export, Registry, documentation, and test paths of one component | component-map.md | bun skills/seed-component/scripts/component-map.ts <Component> |
| Only the differences in React and Lynx public APIs and user-facing results | api-parity.md | bun skills/seed-component/scripts/api-parity.ts <Component> |
| Only the definition, alias, usage sites, generation surface, or contrast of color tokens (even without a component) | color-token-analysis.md | bun skills/seed-component/scripts/token-map.ts '<token>', token-contrast.ts |
| A new component or a port for a platform that does not have one | implementation-workflow.md new and porting | bun skills/seed-component/scripts/scaffold-plan.ts |
| Changing the implementation, behavior, or structure of an existing component | implementation-workflow.md changing an existing implementation | Compare APIs if needed after path lookup |
| Only Lynx documentation and runnable examples (keeping component behavior unchanged) | lynx-docs.md | Path lookup only when the path is unclear |
| Only React documentation and examples, Storybook, and generated output | implementation-workflow.md short path | Path lookup only when the path is unclear |
Boundaries
- The documentation and Storybook-only branches do not require component implementation. If an API or behavior problem that also reproduces in a real host app is found, switch to changing the existing implementation instead of using a documentation workaround.
- If a new package, external dependency, or CI configuration is needed, get user confirmation before implementation.
- Independently judging Lynx native results without modifying the source is handled by
seed-verify-lynx-component. - If ownership across multiple layers, parallel work, or coordination between agents is requested or needed, use
seed-orchestrate-componenttogether. - Changesets, change plans, and submissions are handled by
seed-change.