This skill is a router that determines the entry point for component work. It does not read all reference documents in order. It selects only the skills and references needed for the current task.
What to check first
- From the repository root to the modification path, the applicable
AGENTS.mdread. seed-component-mapto find the current implementation, public exports, Recipe, Registry, documentation, and examples. If it is a new component,not-foundleave the result as evidence that there is no current implementation.- Directly read the actual files that appear in the results. Do not infer the API or responsibilities from map results alone.
- Classify the request as one of: modifying an existing component, a new component, or documentation/Storybook only.
Used together with seed-* skill
| Judgment needed | Skill to use |
|---|---|
| Find the current layer and public path | seed-component-map |
| Compare API, state, and accessibility differences between React and Lynx | seed-api-parity |
| Write Lynx documentation and runnable examples | seed-write-lynx-component-docs |
| Write versions and changesets for public package changes | seed-changeset |
| Determine the impact of the current change, verification order, and PR base | seed-change-plan |
| Prepare rebase, commit, push, and PR with the confirmed base | seed-submit-change |
seed-api-parityDifferences are not immediately considered omissions. First classify whether they are intentionally different items due to runtime, accessibility, or input method differences between the browser and Lynx.
seed-submit-changeis used only when the user requests submission work. seed-change-plandetermined by origin/dev, origin/minor, origin/major Use one of them as-is for the rebase and PR base.
Modify existing component
seed-component-mapFrom the results, read the files directly related to this request.- If you need to change React and Lynx together or determine whether a difference on one side is a problem,
seed-api-parityuse. - Write the user outcome you want to change in one sentence and confirm the target platform and distribution method.
- Only when changing the structure, Architecture decision과 API designread. Do not apply the full design process to work that only changes styles or documentation.
- Modify only the necessary source files based on the closest file in the existing implementation. Do not directly modify generated files.
- Verification checklistRun the items related to the actual changes in .
- If the public package changes,
seed-changesetuse. When preparing a commit or PR, regardless of the type of change,seed-change-plandetermine the base with . If you are asked to rebase, commit, push, or submit a PR, at the endseed-submit-changeuse.
New component
seed-component-map의not-foundCheck the paths of the existing component closest to it as well.- The target platform is
react,lynx,cross-platformdetermined as one of Platform selectionlies in. - API designthe delivery method is determined as one of
package-only,snippet-only,package+snippet,docs-only. - Only when there is a blank in the requirements that would change the implementation, Requirements explorationis used. Do not re-interview for an already specific request.
- Architecture decision, Headless responsibilities, Recipe types, accessibility, and reference components per layer are determined.
- Convert the decisions finalized with the following command into a file plan.
bun skills/seed-create-component/scripts/scaffold-plan.ts <component> \
--platform <react|lynx|cross-platform> \
--surface <package-only|snippet-only|package+snippet|docs-only>
The script does not decide architecture or Registry necessity on its own. source, reference, generated, conflictsReview and leave only the source files needed for this task in the plan.
- Implementation orderimplement only the necessary layers among Headless, Rootage, Recipe, Styled UI, Registry, documentation, and examples.
- Verification checklistis run. If a public package changes,
seed-changesetis used. When preparing a commit or PR,seed-change-plandetermine the base with, and only when asked to submit,seed-submit-changecontinue with.
If a new package, external dependency, or CI configuration is needed, get user confirmation before implementation.
Short path
Change only Lynx documentation and examples
If component and runtime behavior are not changed, seed-component-mapcheck the deployment method with, then seed-write-lynx-component-docsis used. If a problem that also reproduces in an actual host app is found, do not create a documentation workaround and return to the component change flow.
Change only Storybook
docs/stories/*.stories.tsx나 docs/.storybook/*If only is changed and the public API and behavior are maintained, Storybook rules과 Visual verificationuse only. If a component API or Recipe change becomes necessary during the work, switch to the existing component change flow.
When only generated artifacts are out of sync
First find the source files and generation command. Do not directly edit generated files. If the source is correct, run the generation command from the repository guidelines and check that only the expected generated artifacts changed.
Implementation reference routing
| Situation | Document to read |
|---|---|
| Platform is ambiguous or cross-platform | platform-gate.md |
| Deciding public API or Registry status | api-design.md |
| There is an important blank in the requirements | brainstorming.md |
| New component or layer structure change | architecture-decisions.md, pattern-catalog.md |
| React Styled UI implementation | react-patterns.md |
| Lynx implementation | lynx-patterns.md |
| Recipe implementation | recipe-patterns.md |
| Check only per-layer paths and generation relationships | guide.md |
| Implementation order including Registry, documentation, and examples | implementation-steps.md |
| Research external interfaces and accessibility patterns | external-references.md |
| Verification and visual confirmation | verification-checklist.md, visual-testing.md |
| A blocker occurs | sticking-policy.md |
| Review after modifying this skill's routing | review-prompts.md |
Completion conditions
- The requested user results and target platform match in the implementation, types, and documentation.
- The distribution method chosen between package and Registry is also applied as-is to the documentation and examples.
- The source files were modified and the generated files were not edited directly.
- Existing tests related to the change and the repository's required verification passed.
- Public package changes have a finalized changeset.
- If preparing a commit/PR, there is a change plan that uses the finalized base regardless of whether a changeset exists.