Figma Make Now Edits Your Real Codebase

What is the new Figma Make feature?

On May 28, 2026, Figma launched a closed beta that lets Figma Make connect to your real codebase, edit live elements, and open a pull request. Before this, Make generated standalone prototypes. Now it can touch the actual repository behind a product. It is Figma pushing further into the design-to-code territory that slows most B2B SaaS launches.

How does it connect to my code?

You link a Git repository to Figma Make. GitHub is natively supported, and other Git providers connect over SSH. Once linked, Make can read the codebase, understand the existing components, and propose edits in context. This is different from copy-pasting generated code, because Make works against your real file structure rather than a blank sandbox.

Can it really open pull requests?

Yes. Figma's release note says you can commit changes and open a pull request without touching a terminal. Make stages the edit, writes a commit, and pushes a branch for review. For a designer who knows what they want but not the command line, this removes a real barrier. The PR still goes through normal human review.

What is the Figma MCP integration?

Figma exposes a Model Context Protocol server so AI coding agents can read design context directly. Combined with the new Make codebase feature, an agent can pull a component's exact spec from Figma and apply it in code. For teams already using Claude or Cursor, this tightens the loop between the design file and the shipped UI.

Do I need a terminal?

No, and that is the point. The whole workflow, from editing an element to opening a pull request, runs inside Figma. A designer can propose a real code change without learning Git commands. That said, an engineer still reviews and merges the PR, so the safety net of human code review stays firmly in place.

What are Make skills?

Make skills are reusable instructions that teach Make how your team builds. Think of them as saved patterns for your design system, naming conventions, and component structure. Once defined, skills make Make's output match your house style instead of generic code. For a studio, this is how you keep AI-assisted edits consistent across many projects.

When is Config 2026?

Figma Config 2026 runs June 23 to 25 at Moscone Center South in San Francisco. Config is where Figma typically announces its biggest features, and over 10,000 designers, developers, and product leaders attend, a figure with medium confidence. Expect the Make codebase beta to graduate or expand around the conference, so watch the announcements.

How does this change design handoff?

It compresses it. The classic handoff, where a designer ships a file and an engineer rebuilds it in code, loses detail at every step. When Make can apply design changes directly to the codebase, the gap narrows. For B2B SaaS teams, that means faster iteration and fewer pixel-mismatch arguments between design and engineering.

Should my team adopt it now?

Pilot it, do not bet the roadmap on it yet. It is a closed beta, so access is limited and behavior will change. Try it on a low-stakes internal project first. If your team already lives in Figma and ships to GitHub, the upside is real. Keep your existing handoff process running in parallel until the beta stabilizes.

Will this replace front-end developers?

No, it shifts what they do. Make handles routine edits and first-pass implementation, which frees engineers for architecture, performance, and the hard problems AI still fumbles. The Wix layoffs this week show AI compressing routine work across the industry. The durable front-end role is judgment and systems thinking, not hand-coding every button.

Scoping your next build around this shift? Pair this with the Figma design agent beta breakdown, the Figma Buzz and Grid GA notes, and the bento grids design piece. Let's chat.