Questions developers ask.
What does F2F do?
It turns a Figma design into exact, structured context for an AI coding agent, maps that design to the components and tokens already in your repository, and then measures the built screen against the design so the agent can fix what does not match.
Does it generate the code itself?
No. Your AI coding agent writes the code. F2F gives it exact facts and a repo-aware brief before, and a measured report after. That separation is what lets it work with any agent and any stack.
Which frontend stacks are supported?
React, Next, Vue, Svelte and plain HTML on the web; Flutter on web, Android, iOS or as a host test; React Native and Jetpack Compose on Android; React Native and SwiftUI on iOS. Repo inspection currently understands Flutter and React/Next/Vue/Svelte projects best.
Which AI agents does it work with?
Any agent that can read files in your repository and run a terminal command. The brief and reports are plain Markdown and JSON.
What does it cost?
Nothing. It is open source under the MIT license. It needs no paid Figma plan, no paid API and no server. The Figma free plan works.
Does my design or code leave my machine?
No. The Figma plugin has no network access. The CLI runs locally, reads your repository read-only and never opens env or key files. There is no telemetry.
How accurate is it?
Exported values matched Figma's own JSON export with zero mismatches on a real file. Verification checks every tagged layer to ±1 px. In a measured run, one fix round driven by the report took a screen from 31 to 44 of 47 matching layers; the rest were font-rendering warnings.
Does it check colours and fonts?
Yes, on web, as numbers: font family, weight, italic, size, text colour, background and corner radius of every tagged layer are compared with the Figma values, and fonts the browser fakes because their file is not loaded are reported. On Android and iOS this is not measured yet, so check colours and fonts by eye.
What do I need installed?
Node 22 or newer and the Figma desktop app. For web checks, Chrome or Edge. For Android, adb. For iOS, idb. Nothing is downloaded for you.
Does it handle responsive layouts?
Partly. Each screen is measured at its design width, and on web verify also loads the page at 375 px and fails if it scrolls sideways or cuts off content. The brief tells the agent to build fluid layouts that stack and wrap. Breakpoints are not invented: linking several Figma widths of the same screen is on the roadmap.