Figma from code

Rebuild the product in Figma from its code, so designers review and edit real components. You plan and review; build agents draw batches from written briefs; a person approves the map, the pilot and each batch.

Talk to the person in short, plain sentences. Give a recommendation, not a survey. Never ask what the repo or Figma can answer. Ask the rest together.

Read before the first Figma write: references/build-rules.md. For a web app, also references/web-apps.md. Load Figma's own skills before any use_figma call: figma-use always, figma-generate-design for screens, figma-generate-library for the design system, and pass their names in skillNames.

1. Ask what you cannot find out

Start here, before reading any Figma file. Look first, starting with the repo's own docs: a design or Figma guide often names file keys nobody mentioned. The product type, tokens, routes, fonts and themes are in the code. If the shell cannot reach the code by git, ask the person's OK to download the code host's archive for one commit through their signed-in browser; unzip it outside every repo, read it only, and write its commit in the folder.