Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-05-29 · source-backed
Figma Make shipped something I didn't expect this fast. The AI design tool now connects to Git repositories in the desktop app. Designers and PMs can visually select elements, adjust properties like layouts, colors, fonts, and sizing, and Make finds the relevant code and edits it directly. Changes are stored as local commits until you open a PR through normal GitHub workflows.
The limited beta launched May 28, Mac only. Zero credits consumed during beta.
Here's why this matters more than another "AI generates code" headline. The design-to-code handoff is one of the most expensive coordination problems in product development. A designer creates a mockup. They annotate it with redlines and specs. An engineer interprets those specs, sometimes correctly. A review cycle catches the gaps. Maybe two review cycles. Sometimes three. That loop eats days per sprint at every company I've worked at.
Figma Make collapses that loop. The designer sees the actual rendered UI, makes visual adjustments, and the tool produces the code change. Not a mockup. Not a Figma-to-React export that needs cleanup. An actual diff against your production codebase.
I'm cautiously optimistic but want to flag what could go wrong. Design tools that edit code have a long history of producing code that works but that no engineer wants to maintain. If Make generates messy CSS overrides or ignores your design system tokens, the time saved on handoff gets eaten by cleanup. The annotation feature, where designers describe interactions and animations for more complex changes, adds another input where intent can get lost in translation.
Still, the direction is right. This is vibe coding for non-engineers, and that's not dismissive. Giving designers direct agency over visual implementation without requiring them to learn React is a genuine workflow improvement. And since it's all local commits, the worst case is a bad diff that gets rejected in review.
If you have a designer on your team, get them into this beta now. It's free, it's low-risk, and you'll know within a week whether it fits your workflow. The companies that figure out how to use this well are going to move noticeably faster on UI iteration.
[Source: Figma Blog]
Each link below shares sources, entities, or timing with this story.
Figma supports MCP / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Figma supports MCP); both cover CSS, DESIGN, Figma, React; reported by the same outlet (figma.com).
Figma supports MCP / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Figma supports MCP); both cover CSS, DESIGN, Figma, React; overlapping topics (code, design, design-to-code, handoff).
Linked by a graph relationship (Figma supports MCP); both cover DESIGN, Figma, GitHub, React; overlapping topics (code, design).
Figma supports Cursor / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Figma supports Cursor); both cover Figma, GitHub; reported by the same outlet (figma.com).
Figma supports MCP / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Figma supports MCP); both cover CSS, Figma, React; overlapping topics (code, design, design-to-code).
Figma partners with Anthropic / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Figma partners with Anthropic); both cover Figma, React; overlapping topics (code, company, design, tool).
Figma supports MCP / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Figma supports MCP); both cover CSS, React; overlapping topics (code, workflow).
Figma supports Cursor / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Figma supports Cursor); both cover GitHub, React; overlapping topics (code, codebase, tool).