If you're shipping static sites, or building on a standard design system, the Figma MCP server is probably doing great work for you, and you can skip this one. This is for the people who have hit the friction: anyone trying to make the design-to-code pipeline more modular, maintainable, robust, and tool-agnostic, and get better code out the other end.
I started writing this as a takedown.
The plan was simple: Figma-to-code is overhyped, the demos are slick, and on most teams the reality is a mess. I was going to show you how bad it gets: the hard-coded colours, the components the model invents, the output that looks right until you actually read it.
Then I came across monday.com's design-to-code pipeline1, and I was genuinely impressed.
What monday showed me is that it can be done well, even if a developer is still cleaning up the code behind the demo.
