On May 28, 2026, Figma gave Figma Make a capability most people assumed was years away: connect it to a production or sandbox repository through the Figma desktop app, and Make becomes, in the company’s own framing, “a visual surface for building and editing real software.” Alongside the repo connection, Figma shipped a new editing panel for “precise design adjustments like layouts, colors, font sizes, and effects.” The significance is blunt: Figma is no longer just a design tool. It is now a code editor pointed at your live codebase, and the last stretch of boundary between design and production code is being dismantled.
How the New Workflow Works
Per The Verge, the connection is made through the Figma desktop app, and teams choose whether to link a production repository or a sandbox one — the latter is an obvious on-ramp for teams that want to experiment before touching anything real. Once linked, Make acts as a visual editing layer over that codebase: coarse changes happen through prompts, fine-grained tweaks land in the new panel, and both live in the same surface. CMSWire’s read on the announcement was equally direct: the new capabilities push designers “deeper into engineering territory,” letting them edit production code without leaving the canvas. The Verge frames this as the follow-up to Make’s earlier general availability — a fast cadence from text-to-app demo to a tool that expects to live inside your engineering workflow, not beside it.
From Prototype Generator to Production Tool
The step also marks an identity change. Figma Make started life as a prompt-driven prototype generator; it now claims to be an editing surface for real software. A same-day Figma article, “4 new ways to go from idea to product with AI tools,” offers useful reference points. Marketing agency Merkle used Figma’s AI agent to generate roughly 50 layout variations for a telecom client, compressing “the production work that would have taken days… into hours.” Affirm went “from idea to working prototype in two days instead of the usual six weeks” for checkout payment-plan badges, with MCP passing components, tokens, and layout structure straight into the coding environment. Hotel group Accor built a prototype of a webpage that reorganizes itself based on what the user types — searching “golf” reshapes the page — while the Figma MCP server “kept everything connected to the brand’s design system.”
The same article introduced Make kits — in Figma’s words, they “do for Figma Make what MCP does for AI-generated code” — so prototypes use your actual components and styles from the first prompt, while Make attachments carry project context like data and brand guidelines. These mechanisms are what make production editing survivable: visual edits only stay sane if they manipulate a real design system rather than a plausible-looking approximation generated from nothing.
Redrawing the Design-Engineering Boundary
Pointing a visual editor at a live repo changes responsibilities, not just tooling. Designers get to touch something that actually runs sooner — FloQast’s case in the same Figma piece is instructive: a prototype with a simulated backend, tested against realistic data from a real customer, exposed “flows that looked right on the surface but fell apart in practice.” That is the argument for connecting design to code early. But every visual edit on a production repository is, ultimately, a commit. As editing entry points multiply, code review and CI become the gatekeepers, and the engineering review process turns into the next bottleneck. Figma’s own description of the design-to-code loop — prototype in an AI coding tool, pull it onto the canvas for refinement, return to code via MCP “with the design context intact” — makes clear the passage now runs in both directions.
Three Practical Cautions Before Adopting
First, connect the sandbox repository first, and graduate to production only once the team has real review discipline. Second, treat every Make edit as a pull request: through the diff, through CI. However precise the new editing panel is, what lands is still a commit. Third, wire up Make kits or an MCP design-system integration on day one, so visual edits manipulate real components and tokens — otherwise design debt simply moves from the mockup into the repository. The tool opened the door; the governance is still yours to bring.
Sources
- Figma Make can edit your production codebase now — The Verge
- Figma Make Brings Visual Editing to Live Codebases — CMSWire
- 4 new ways to go from idea to product with AI tools — Figma
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.