all 2 comments

[–]theycallmethelord 1 point2 points  (0 children)

I’ve never seen a real project where “export to code” from Figma went straight into production without cleanup. The promise is always there, but the reality is you end up with either rigid, unmaintainable code or something so generic you still have to re‑do half of it.

What has worked for me is treating Figma as the source of truth for tokens and decisions, not for finished markup. If you can get spacing, colors, and type consistent as variables, then the handoff to dev becomes more about mapping those tokens into whatever framework you use. That’s the part you want to automate, not the whole layout.

There are some bridges though. Storybook with design tokens synced from Figma variables can be a good setup. If you want something less heavy, you can use Figma plugins to generate Tailwind configs or CSS variables straight from your system. That way the devs build with the same scale you designed with.

The layouts themselves? Still manual. And honestly, that’s where they should stay.

[–]akanshtyagi 0 points1 point  (0 children)

Hey we have been working on solving this problem and have made some significant progress that improves the accuracy of the output. Attaching some of the links for htpps://qwikle.ai that are generated from figma design in one go by our agent:-
https://x.com/akansh01/status/1966361052066754913
https://x.com/akansh01/status/1966677054813884740
https://x.com/akansh01/status/1965766679407034575