figma-from-code-discovery-components

name	figma-from-code-discovery-components
description	Subagent for figma-from-code Phase 0a. Discovers the complete component architecture of a web application via browser crawling and static code scanning. Produces a topologically-sorted build order and inspects the target Figma file for existing pages and components.
model	claude-sonnet-4-5

Skill: Component Discovery

Discovers the complete component architecture of a web application by combining two methods: (1) browser crawling to find runtime components with routes and selectors, and (2) static code scanning to find all components including those not rendered during the crawl (modals, inline-edit variants, conditional renders, etc.). Produces a merged, topologically-sorted build order (leaves first, layouts last). Also inspects the target Figma file to report existing pages, variable collections, and components.

When to Use

• Before running figma-from-code on a fresh Figma file
• When the component hierarchy may have changed and you need an updated build order
• Standalone audit of what components a site uses and how they nest
• When resuming a build and component-map.json is missing

Prerequisites

• Dev server running at {devServerUrl} (or custom URL)
• Playwright installed (node_modules/playwright-core)

Placeholders like {devServerUrl} resolve from state.json → config.

Required Inputs

• fileKey: The Figma file key (for the Figma inspection step)
• devServerUrl (optional, default http://localhost:5173): The running dev server URL

Output Files

Written to .temp/figma-from-code/:

File	Contents
component-map.json	Authoritative tiered build order (machine-readable), incl. capture data
component-map.md	Human-readable report with Mermaid diagram
interactions.json	Interaction scenarios that reveal gated components (authored in step 3c)

Workflow

1. Ensure output directory exists

mkdir -p .temp/figma-from-code/

2. Verify dev server is running

curl -s --max-time 3 {devServerUrl} > /dev/null || echo "Dev server not running"

If not running, halt and tell the user to start the dev server.

3a. Enumerate routes statically

The link-following crawler only finds routes reachable via <a href>. Routes reached programmatically (e.g. navigate('/cases/new')) are invisible to it, so enumerate routes from the source code first:

1. Read the app's router configuration (e.g. <Route path=...> in React Router, file-based route folders) and list every declared path.
2. Grep the source for programmatic navigation literals: navigate(, router.push(, history.push(, and to=/href= string literals.
3. Watch for conditional renders behind a parameter value: a route like /cases/:id where the page renders a different component when id === 'new' means /cases/new is a distinct concrete route — include it explicitly.

Produce a comma-separated route list of concrete, parameterless paths (e.g. /,/cases/,/cases/new,/tasks/new). Leave :id-style dynamic routes to the crawler — it instantiates them from real links.

3b. Run the passive component discovery script

node {skillRoot}/scripts/map-components.js \
  "{devServerUrl}" --routes {enumerated_routes} --crawl --max-crawl 30 \
  --markdown .temp/figma-from-code/component-map.md \
  --output .temp/figma-from-code/component-map.json

This produces the authoritative build order — a topologically-sorted list of tiers where leaves come first and layouts come last. All subsequent phases of figma-from-code use this output. Each component found at runtime gets a capture object recording the exact URL and CSS selector (plus ordered fallbackSelectors) where it was observed.

3c. Author interaction scenarios for gated components

After the passive pass, read component-map.json and list components with capture: null / instances: 0. Many of these only mount after a user interaction (dialogs, dropdown menus, tooltips, click-to-edit inputs). For each, read its source file and call sites to find the trigger element, then write a scenario to .temp/figma-from-code/interactions.json:

{
  "scenarios": [
    {
      "id": "case-more-options",
      "route": "/cases/:id",
      "steps": [{ "click": "button[aria-label=\"More options\"]" }],
      "expect": ["MoreOptionsMenu"]
    },
    {
      "id": "editable-title-edit",
      "route": "/cases/:id",
      "steps": [{ "click": "main h1" }],
      "expect": ["EditableTitle", "EditControls"]
    }
  

• route may be a visited concrete route or a :param pattern — patterns resolve against a concretely visited URL.
• steps run in order; verbs are click, hover, press (e.g. "Escape"), and fill ({"fill": {"selector": "...", "value": "..."}}). Each step accepts an optional settle (ms, default 400).
• expect lists component names the scenario should reveal — used to report scenarios that need refinement.
• Prefer click/hover steps: only those are replayed at screenshot time (Phase 2.5). press/fill steps run during discovery but are not part of the capture replay.

Safety rules (mandatory — copy into every scenario review):

• Never click elements whose text or handler indicates destruction or persistence: Delete/Remove/Confirm inside an already-open confirmation dialog, Save, Submit, or any type="submit" button. Opening a confirmation dialog is allowed; confirming it is not.
• Prefer aria-label or role+text based step selectors; never positional (nth-of-type) ones.
• Each scenario must be independently replayable from a fresh page load — never depend on state left by a previous scenario.

3d. Run the interaction pass

node {skillRoot}/scripts/map-components.js \
  "{devServerUrl}" \
  --augment .temp/figma-from-code/component-map.json \
  --interactions .temp/figma-from-code/interactions.json \
  --markdown .temp/figma-from-code/component-map.md \
  --output .temp/figma-from-code/component-map.json

--augment seeds from the existing map and skips the passive crawl, so this pass only runs the scenarios. Read interactionResults from the output:

• status: "ok" — scenario ran; found lists revealed components (now carrying capture with the replay recipe).
• status: "missing_expected" — scenario ran but some expected components were not revealed; missing lists them.
• status: "failed" / "no_matching_route" — step selector or route problem; error has details.

For scenarios that did not reveal their expected components, refine the step selectors and re-run 3d (max 2 refinement iterations). Debug a single scenario interactively with:

node {skillRoot}/scripts/discover-components.js "{devServerUrl}{route}" --click "{trigger}" --list

Components still without capture after refinement are genuinely non-renderable from the live app (loading/error states, hover-only primitives) — record each with its reason for the final report.

4. Normalize component names

The DOM scanner extracts React component names from the fiber tree, which may differ from the Figma naming convention for icons and assets:

• Lucide icons: scanner reads the internal displayName (e.g. EllipsisVertical) rather than the import alias used in code (e.g. MoreVertical)
• SVG asset wrappers: scanner sees the wrapper component name (e.g. CartonLogo) rather than the Figma asset name (e.g. Asset/CartonLogoSvg)

Run the normalization script to align names with Figma conventions. This requires icons.json from Phase 0b.

node {skillRoot}/scripts/normalize-component-map.js \
  .temp/figma-from-code/component-map.json \
  .temp/figma-from-code/icons.json \
  --write

If icons.json does not yet exist (Phase 0b hasn't run), skip this step — the orchestrator will re-run normalization after Phase 0b completes.

The script resolves names via three strategies:

1. Direct icon match: component name is a known icon import name → prefix with Icon/
2. Lucide alias resolution: component name is a Lucide canonical name that differs from the import alias → resolve via lucide-react exports → prefix with Icon/
3. Asset prefix match: component name is a prefix of a known asset name → prefix with Asset/

5. Discover frontend source directories

Run the code scanner in discovery mode to locate component directories:

node {skillRoot}/scripts/discover-code-components.js \
  --discover --root .

Read the JSON output and automatically apply the following default exclusions (do not wait for user input — this is a subagent):

• Any directory named ui/ that is a direct child of a components/ folder (shadcn primitives, not application components)
• Any directory path containing __tests__, __stories__, .storybook, or node_modules
• Any directory path containing /dist/ or /build/

For each excluded directory, record the directory path and the exclusion reason. Include the final componentDirectories list and the list of any excluded directories with their reasons in the discovery summary returned to the orchestrator. The orchestrator will surface these to the user at the next user-facing checkpoint so they can request adjustments if needed.

After running --discover and applying exclusions, write both componentDirectories and excludedDirectories into component-map.json as top-level fields so they are preserved through the --scan merge in Step 6 and available to the summary script in Step 10:

// Merge into component-map.json after --scan completes
const map = JSON.parse(fs.readFileSync('.temp/figma-from-code/component-map.json', 'utf-8'));
map.componentDirectories = componentDirectories; // [{ path, componentCount, subdirs }]
map.excludedDirectories = excludedDirectories;   // [{ path, reason }]
fs.writeFileSync('.temp/figma-from-code/component-map.json', JSON.stringify(map, null, 2));

6. Scan code for all components

Run the code scanner in scan mode with the confirmed directories:

node {skillRoot}/scripts/discover-code-components.js \
  --scan {confirmed_dir_1} {confirmed_dir_2} \
  --browser-map .temp/figma-from-code/component-map.json \
  --output .temp/figma-from-code/component-map.json \
  [--exclude {excluded_dirs}]

This merges code-discovered components into the browser-discovered map. Each component gains a source field ("browser", "code", or "both") and a codeDependencies array. Tiers are recomputed from static import analysis to include all components. Browser data (routes, selector, instances) is preserved for components found by both methods.

7. Read and summarize the output

Read .temp/figma-from-code/component-map.json and extract:

• tiers[] — the tiered build order (number of tiers varies per project)
• tree — the merged component hierarchy
• componentCount — total components to build
• Source breakdown:
  • {bothCount} found in browser + code
  • {codeOnlyCount} found in code only
  • {browserOnlyCount} found in browser only (no source file matched)

8. Inspect the Figma file and match components

Use get_metadata (fileKey) to retrieve all components and component sets from the Figma file. This returns every component with its name and nodeId.

Build a lookup map from the Figma metadata: { componentName → nodeId }.

After normalization (step 4), component names in component-map.json use Figma conventions (Icon/Bot, Asset/CartonLogoSvg, Button). Match each component by exact name against the Figma lookup map.

For each component in every tier of component-map.json, add a figmaNodeId field:

• If a matching Figma component exists: set figmaNodeId to the node ID string (e.g. "918:50")
• If no match: set figmaNodeId to null

Also use use_figma to do a read-only inspection for file-level state:

• List all pages (names + IDs)
• Check if variable collections already exist (Palette, Semantic, Spacing)
• If a page named Screens already exists, list its top-level children. Each direct child frame is a pre-existing screen. Build preExistingScreens as { frameName: nodeId } (e.g. { "CasesPage": "123:456" }). If no Screens page exists, set preExistingScreens to {}.

8b. Ensure .figma/figma.json exists for every matched component

For each Figma component returned by get_metadata (regardless of whether it appears in the runtime component-map.json), ensure a tracking record exists next to its source file. The tracking file path is resolved as follows:

1. Component has a sourcePath in component-map.json: write to path.dirname(sourcePath)/.figma/figma.json
2. Component has no sourcePath (browser-only or synthetic): search each directory in config.componentsRoot (an array) for a matching component folder. Use namespace-aware path rules — Icon/Bot → {componentsRoot[i]}/Icon/Bot/.figma/figma.json. Try each componentsRoot entry in order; use the first match. If no match is found, use the first componentsRoot entry as the default.

Same schema as Step 6 of plugins/figma-from-code/skills/figma-from-code/7-build-component/SKILL.md:

{
  "fileKey": "{figmaFileKey}",
  "nodeId": "{nodeId}",
  "url": "https://figma.com/design/{fileKey}?node-id={nodeIdWithDashes}",
  "componentName": "Button",
  "createdAt": "2026-05-15T14:32:00Z",
  "updatedAt": "2026-05-15T14:32:00Z",
  "dependencies": []
}

Behavior:

• File missing: create it. Set createdAt and updatedAt to the current ISO 8601 UTC timestamp. Create the .figma/ folder first if it does not exist.
• File present: do not modify it. This phase only seeds tracking files for components that lack one — refreshing updatedAt is plugins/figma-from-code/skills/figma-from-code/7-build-component/SKILL.md's job.

Skip COMPONENT children of COMPONENT_SET nodes (variants) — only write tracking files for the top-level component or component set.

Failure handling: if a write fails (permission, missing parent path that can't be created), log the failure and continue with the rest. Surface the count of failures in the final report (Step 10).

9. Write updated output

Re-write .temp/figma-from-code/component-map.json with the figmaNodeId field added to every component entry across all tiers. Also add a top-level figma summary object.

Why this matters for later phases: the orchestrator uses every component with a non-null figmaNodeId as the immutable preExistingComponents snapshot in state.json. The orchestrator's "Pre-Existing Components Rule" requires explicit user authorization before modifying, replacing, or deleting any of those nodes in later phases (Phase 3 rebuilds, Phase 5 fix-loops, ad-hoc cleanup). Accuracy of figmaNodeId matters — a missed match silently degrades that protection.

{
  "figma": {
    "fileKey": "{fileKey}",
    "pages": [{ "name": "...", "id": "..." }],
    "variableCollections": ["Palette", "Semantic"] or [],
    "existingComponentCount": 12,
    "missingComponentCount": 5,
    "preExistingScreens": { "CasesPage": "123:456" }
  },
  "tiers": [
    {
      "tier": 1,
      "components" 
             ... 
             ... 
      
    
  

10. Write discovery summary for the orchestrator

Extract the data the orchestrator needs into a small summary file so it never has to read the full component-map.json (which can be 48KB+):

node -e "
  const map = JSON.parse(require('fs').readFileSync('.temp/figma-from-code/component-map.json','utf-8'));
  const tiers = map.tiers.map(t => ({ tier: t.tier, label: t.label || 'Tier ' + t.tier, components: t.components.map(c => c.name) }));
  const builtComponents = {};
  const preExistingComponents = {};
  let bothCount = 0, codeOnlyCount = 0, browserOnlyCount = 0;
  for (const t of map.tiers) {
    for (const c of t.components) {
      if (c.figmaNodeId) {
        builtComponents[c.name] = c.figmaNodeId;
        preExistingComponents[c.name] = c.figmaNodeId;
      }
      if (c.source === 'both') bothCount++;
      else if (c.source === 'code') codeOnlyCount++;
      else if (c.source === 'browser') browserOnlyCount++;
    }
  }
  const componentCount = map.tiers.reduce((sum, t) => sum + t.components.length, 0);
  // Read componentDirectories and excludedDirectories from the --discover output
  // These are written by Step 5 and preserved in component-map.json
  const componentDirectories = map.componentDirectories || [];
  const excludedDirectories = map.excludedDirectories || [];
  const summary = {
    buildOrder: { tierCount: tiers.length, tiers },
    builtComponents,
    preExistingComponents,
    preExistingScreens: (map.figma && map.figma.preExistingScreens) || {},
    componentCount,
    componentDirectories,
    excludedDirectories,
    sourceBreakdown: { both: bothCount, codeOnly: codeOnlyCount, browserOnly: browserOnlyCount },
    figma: map.figma || null
  };
  require('fs').writeFileSync('.temp/figma-from-code/discovery-summary.json', JSON.stringify(summary, null, 2));
  console.log('Discovery summary written: ' + componentCount + ' components across ' + tiers.length + ' tiers');
"

Write to .temp/figma-from-code/discovery-summary.json. The orchestrator reads only this file (~3KB) instead of the full component-map.json. The componentDirectories and excludedDirectories fields are surfaced to the user at the Wave 1 pause for confirmation (see orchestrator § "Wave 1 Pause: Component Directory Confirmation").

11. Report

Report what exists in Figma vs what needs to be created, including the discovered build order and source breakdown:

Component Discovery complete:
- {componentCount} components across {tierCount} tiers
- Source breakdown: {bothCount} browser+code, {codeOnlyCount} code-only, {browserOnlyCount} browser-only
- Interaction scenarios: {scenarioCount} run, {recoveredCount} components recovered via interactions
- Components without capture (cannot be screenshotted from the live app): {list with reason each}
- Tier 1 (leaves): {component list}
- Tier 2: {component list}
- ...
- Tier {N} (top-level): {component list}

Figma file state:
- Pages: {existing page names}
- Variable collections: {existing or "none"}
- Already built: {count} components ({list})
- Not yet built: {count} components ({list})

Scripts Reference

Script	Location	Purpose
map-components.js	{skillRoot}/scripts/map-components.js	Crawls routes, detects framework, discovers components, computes build order. --interactions runs scenarios from interactions.json; --augment seeds from a previous output and skips the passive crawl
normalize-component-map.js	{skillRoot}/scripts/normalize-component-map.js	Aligns scanner names with Figma conventions using icons.json + Lucide alias table
discover-code-components.js	{skillRoot}/scripts/discover-code-components.js	Auto-discovers frontend packages and scans source for all components. --discover mode finds directories; --scan mode parses imports, merges with browser map (preserving capture), recomputes tiers

Do NOT modify map-components.js — drive it via its flags (--routes, --interactions, --augment); app-specific knowledge belongs in interactions.json, never in the script.

Skip / Resume

If called with resume: true, check whether .temp/figma-from-code/component-map.json exists on disk. If it does, skip the discovery run and read the existing file. If it's missing, re-run.

Error Handling

Scenario	Action
Dev server not running	Halt, tell user to start the dev server
map-components.js fails	Check Playwright installation, verify URL is accessible
Figma use_figma read-only call fails	Report error but do not block — component discovery output is still valid
Empty component-map.json	Check that dev server is serving the app (not an error page)