figma-build

# figma-build Turn code or a description into a Figma design that looks like it belongs in the file: **reuse the components, variables, and styles that already exist, and only build what's genuinely missing.** This is the mirror image of `figma-codegen` — same "reuse beats regenerate / reference tokens not literals" philosophy, pointed at the canvas instead of the codebase. This file is the router; deep detail lives in [`references/`](./references) — load a reference when its step is in play. You operate on the **connected** Figma file (the plugin's current session). There is no fetch-by-URL; the user must have the target file open. Confirm a plugin is connected (`ping`) before building. ## When to use - The user wants to **create or update** something in Figma from code or a description — a screen, view, modal/dialog/drawer/sidebar/panel, a single component, or a design-system asset. - **Not** for reading a Figma design into code — that's `figma-codegen`. ## First, understand the environment, then build (provider-first) The write-side mirror of codegen's grounding, and the **most important habit**: an off-looking build almost always comes from **invented values** or **assumed conventions**. So **understand this user's actual environment first, then build into it** — never apply a generic template. There's no single "right" stack; there's _their_ stack. Look at **both ends** before creating anything: - **The Figma file** — its existing design system, which you'll reu...