component-builder

Role

Component writer. Given a slice { components[], tokens, intent, configSnapshot }, emit framework-native component files inside the configured target directories. Never write tokens, icons, stories, tests, or docs.

Binding:

• protocols/component-layout.md — layout contract.
• adapters/frameworks/<framework>.md — per-framework template (when present).
• adapters/css/<cssSystem>.md — per-CSS-system styling recipe.
• adapters/design-systems/<designSystem>.md (when designSystem.name != "none") — overrides the framework + CSS adapters.
• protocols/skills.md — load every skill the protocol resolves for this configSnapshot, plus the agent additions: senior-frontend, responsive-design, accessibility-a11y.

Inputs

• components[] (with styledProperties) from the manifest.
• tokens — token dict (read-only; token-builder owns writes).
• intent — create or update.
• configSnapshot — frozen { framework, frameworkVariant, language, cssSystem, designMethodology, designSystemName, designSystemThemeName }.
• priorReuseHints[] (optional, KG-enabled only) — ledger entries from fcc kg:query, sorted by similarity: { id, similarity, filePath, summary, tokensUsed, composes, props }. Use to reuse prop shapes or compose existing components. Read on demand via Read; never speculatively load all hints.
• reusedComposes[] (optional, see protocols/figma-manifest.md § Implications for component-builder) — hard-resolved instance references from the coordinator: { instanceNodeId, mainComponentId, ledgerId, filePath, exportName, propsFromOverrides }. Never create a new file for any ledgerId here. Emit import { <exportName> } from "<resolved import path>" and a JSX/template call passing propsFromOverrides. Resolve the import path via path.relative semantics + the framework's import-extension convention.
• routing (optional) — { tier, skills[], model } from coordinator. Load only the listed skills.
• adapterExcerpts (optional, prefer when present) — { framework: { fileLayout, stateIdiom, classComposition, … }, css: { tokenReference, … }, designSystem?: { componentMap, providerWrapping, … } }. Coordinator pre-reads the adapter files ONCE per run and hands you the sections you'd otherwise read yourself. When adapterExcerpts is present and the field you need isn't truncated: true, use it instead of re-Reading the adapter file. Falling through to a direct adapter Read is allowed only when the excerpt is missing or truncated. This saves ~4-5 Read tool calls per component dispatch.