Plugin walkthrough
Figma to Web
A Figma screen in. A built Webflow page out.
Orientation
What it is, and how you run it.
It reads which stage the project is at, and starts there.
Once per project · /project-setup <name> · eight questions Asked together, in one message 1TargetWebflow or plain HTML 2ScopeOne page or several, and how many share a navbar and footer 3Design setAll screens ready, or arriving in waves 4FigmaThe file link, and one frame link per breakpoint 5DestinationThe Webflow site and page, or the output folder 6Class namespaceTwo to four letters 7May it write to FigmaAnnotations and pipeline lane moves need it 8Pipeline rowRow code and page title, if it sits on the board A question left blank stays a placeholder. Nothing is guessed. , then it creates the project folder What it writes into the folder CLAUDE.mdFacts, decisions, deviations and open state audit.mdFindings F1, F2, F3 on — each disposed at Stage 7 relationship-table.mdCopied from the template build-log.mdThe build narrative jobs/Empty — Stage 1 writes one folder per screen assets/Empty — Stage 0.5 exports and converts into it custom-code/Webflow target only; an output folder instead, for HTML .claude/settings.local.jsonPermissions, including the decision to let Figma be written Each is created only if it does not already exist. .
The stages
Nine stages, in order.
Where the screen moves on the pipeline board
Gatewon't continue until it passes↻repeats for every section◆waits for your answer
Stages 0, 2, 3 and 4 set up the whole project — later screens skip them and start at Stage 1.
The gate
Every section passes seven checks.
✓ All seven pass — and only then does the next section start.
Conversion time
Where the time goes.
buildingproving it matchesrework, found after it was called done
Recorded by the plugin's own timer, one page at a time, excluding the one-time project setup. Golden Bull is the only page so far with rework recorded against it. Not a measured comparison against building by hand — that test has never been run.
Honest position
What it improves, and what it can’t.
What it improves
Diffed against Figma. Lines must break on the same word.
No raster reaches the build unconverted.
One root value scales the whole page.
Custom code only where the target can't.
116 variables and 23 components before any page.
Six with variants and props registered.
What isn’t proven yet
frost-figma-to-web v0.14.0 · timings from the Frost, Mynt and Golden Bull conversions