figma-catalog-importlisted

# Figma catalog import Take a published **design-artifact catalog** — the `design-artifacts/<system>` bundle that [`compose-design-catalog`](../compose-design-catalog/SKILL.md) produces (`catalog.json` + DTCG tokens + `images/` + `wireframes/`) — and import it into **Figma** as authoritative, code-derived renders. This is the **import hop** — the **Figma destination adapter**. It consumes either arranger's output: a whole-system bundle from **compose-design-catalog** (a `design-artifacts/<system>` branch or a `compose-preview serve` host) *or* a curated render set from **compose-preview-design-board**. Both arrangers delegate the Figma side here rather than duplicating it, because Figma is the one *heavy* destination (a plugin, in-place reconcile, a `design-map.json` correspondence); Claude Design is a light HTML/PNG drop-in that stays in those skills. ## Code is the source of truth The catalog is rendered from real component code, so it is correct by construction — padding, type, colour, corner radius, touch targets are what the components actually resolve, not what a spec claims. **Figma is a *view* of the code, never the authority.** Published Figma kits are seed/reference only. This stance is what makes the import safe to re-run: the render always wins, so a re-import is a refresh, not a negotiation. ## Decide the case FIRST — before writing anything to Figma Two axes decide everything. **State the case out loud before you touch the file.** Getting this wrong can cl