SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsseed-component-map

seed-component-map

Coding & development

View repository

Updated 10-15 20:30

About this skill

SEED Component Map

Use the SEED repository itself as the single source of truth to build a connection map for one component. Do not use a static catalog or external server. The script only reads the current checkout and returns the same JSON for the same file state.

Execution

Specify one component inside the repository.

bun skills/seed-component-map/scripts/component-map.ts ProgressCircle

kebab-case can also be used.

bun skills/seed-component-map/scripts/component-map.ts action-button

Query only one component at a time. If multiple components are needed, run it for each one.

Reading the results

The result JSON contains the following items.

  • component: The normalized name of the input and the search status
  • platforms: The react, lynx platform where the actual surface was found
  • rootage: The Rootage source that is edited directly
  • recipeSources: React and Lynx Recipe sources
  • generatedOutputs: Rootage, CSS, and variable generated artifacts. Do not edit directly.
  • headless: Platform-specific Headless sources
  • implementations: React and Lynx Styled UI implementations
  • packageExports: Public exports leading from the component barrel to the package root
  • registry: Registry implementation and registration files
  • docs: Common, React, and Lynx documentation
  • examples: Documentation examples and the vendored surface of the repository example app
  • tests: Unit tests and Storybook stories
  • ambiguities: Candidates to query again when the exact name was not found

component.stateis one of the following three.

  • matched: Found the exact component surface
  • ambiguous: There is no exact surface, but there are candidates with overlapping names
  • not-found: Found neither an exact surface nor candidates

Work procedure

  1. Before making changes, query the target component map once.
  2. Read the paths of the needed arrays directly to check the actual responsibilities and public API.
  3. generatedOutputsis excluded from the edit targets, and find the corresponding Rootage or Recipe source.
  4. ambiguous면 ambiguities[].candidateRun it again with the exact name of
  5. If implementation or changes are needed, follow the gates and verification procedure of ../seed-create-component/SKILL.md.

Do not infer behavior from the map results alone. This skill only locates paths and does not replace code changes, generation, or verification.

Search scope

The script searches only the following surfaces.

  • packages/rootage, packages/qvism-preset, packages/lynx-qvism-preset
  • packages/css, packages/lynx-css
  • packages/react-headless, packages/lynx-react-headless
  • packages/react, packages/lynx-react
  • packages/stackflow's public components and primitives
  • docs/content, docs/registry, docs/stories, docs/examples
  • examples

It does not follow symlinks or build and cache directories. If a new supported surface appears, do not add a static result file; instead update the search scope of scripts/component-map.ts.