Are Designers the New SWEs? Figma Make's Two-Way GitHub Integration Says Yes
Figma's AI design assistant now reads, edits, and pushes production code through standard pull requests — without bypassing a single engineering guardrail.
Written by OutOfToken AI
June 6, 2026 · 5 min read · Synthesized from reporting by VentureBeat · How this works
Figma just collapsed the wall between design canvas and production codebase. The company announced today that Figma Make — its AI-powered design assistant — can now import existing Git repositories directly into the Figma desktop app, accept natural-language edits on a visual canvas, and push those changes back to engineering teams as standard GitHub pull requests. It is not a prototype export tool anymore. It is a local development environment dressed in a designer's interface.
From One-Way Export to Bidirectional Sync
When Figma Make debuted in May 2025, it could generate interactive prototypes and fire them into a fresh GitHub repository — a genuine leap beyond static wireframes, but fundamentally a one-way ramp. Upstream changes made by engineers never flowed back in. Teams were left maintaining two diverging realities: the Figma canvas and the actual codebase. Today's update tears down that architecture entirely. Designers can now connect any Git provider, pull in an existing production or sandbox repository, isolate specific UI elements on the canvas, and instruct Figma's multi-model AI — which rotates between Anthropic's Claude 3.7 Sonnet, Claude Opus, and Google's Gemini depending on task complexity — to rewrite the underlying code. The agent reads surrounding architecture, applies the visual change, and anchors generated output to the team's established design system tokens, color variables, and component library.
Governance Built In, Not Bolted On
Enterprise adoption of AI coding tools has consistently stalled on one question: who reviews what the machine writes? Figma Make sidesteps that anxiety by operating entirely inside standard version control discipline. Visual edits accumulate as local commits. When a designer is ready to ship, Figma Make generates a branch and opens a pull request directly from the app. That PR then travels through the team's existing CI/CD pipelines, security scanners, and peer code reviews — identical treatment to any commit from a staff engineer. No custom approval layers, no proprietary merge mechanics. The generated code carries no new licensing restrictions when interfacing with open-source or proprietary repositories, and access to Figma Make remains gated to Full seats on paid plans, from $16 per month on Professional up to $90 per month at Enterprise tier.
"45% of designers and 59% of product managers already contribute to code regularly — Figma Make gives them a canvas to do it without touching a terminal."
A Three-Way Competitive Split
Figma Make is no longer jousting with rival design canvases. Its real competitors are full-stack vibe-coding platforms and LLM-native environments. Lovable ($25–$50/month) builds greenfield SaaS applications from zero, orchestrating backend databases like Supabase alongside a code-first GitHub sync — it wins on standalone speed for solo developers and lean startups with no legacy codebase to preserve. Anthropic's Claude Design, accessible on Claude Pro ($20/month) or Max ($100–$200/month) plans, generates functional UI prototypes rapidly from text prompts and hands them to Claude Code, but burns through token limits fast and lacks granular vector control. Figma Make's lane is narrower and more defensible: established cross-functional product teams with mature design systems, existing repositories, and a need to offload frontend iteration from core engineering without surrendering architectural governance. Figma's own documentation is explicit that designers who already hold access rights to their company's codebase are the intended users — a tacit acknowledgment that this is a precision instrument, not a mass-market app builder.
The IPO Math Behind the Feature Drop
Figma's strategic urgency is inseparable from its public market trajectory. The company priced its July 2025 IPO at $33 per share, saw institutional demand oversubscribe the deal 40 times, and watched its stock detonate 250% to an intraday high of $115.50 on day one. By May 2026, FIG had surrendered 81% of that peak value, settling around $21–$22 — well below IPO price — with a market cap of roughly $11.3 billion. Analysts point to a low float, IPO pricing mechanics, and the broader 'software apocalypse' as enterprises redirect SaaS spending toward AI-native workflows and local coding agents. Figma Make's two-way GitHub integration is not a product update in the conventional sense; it is Figma's argument to Wall Street that its platform is not a static vector tool waiting to be commoditized by Claude or Codex, but an irreplaceable orchestration layer where human design intent, enterprise systems, and AI-generated code converge under one governance umbrella.
The 'vibe coding' era is rapidly shifting the primary bottleneck in software development from raw engineering throughput to design governance and architectural intent. Figma Make's two-way GitHub bridge positions the canvas as the new IDE for a significant slice of the product workforce — one that already writes code but has always preferred a visual surface to do it. Whether that repositioning is enough to rebuild Figma's premium valuation depends on how quickly enterprise teams adopt the workflow and how aggressively Anthropic, Lovable, and others close the design-system fidelity gap. The race to own the visual layer of production software just got significantly more serious.
Editorial Note
Sourced from a recognized tech publication.
Claim Tracker
AI-assessed
Article claims future date (July 2025); impossible to verify from present perspective. Entire timeline appears fictional or speculative.
References future date; cannot be verified. Specific percentage and price claims are presented as fact but date is impossible.
Statistics are cited without source attribution. No study or survey reference provided.
Claude 3.7 Sonnet model name does not match Anthropic's actual naming convention (Claude 3, 3.5, etc.). May indicate fictional or outdated information.
Specific pricing figures presented as current but cannot be independently verified from article context alone.
Ask AI about this story
// discussion
sign in to join the discussion