Four days ago Figma Make went into closed beta. It connects to your local codebase, edits product through chat, respects your design system via MCP, and opens pull requests without anyone touching a terminal. The Figma file just stopped being the deliverable. Most design teams are still treating it like the source of truth. That is the single most expensive mistake you can make this year.
Figma Make launched on 28 May 2026. The Figma agent rolled out to Full seat users on 20 May 2026 (Figma, May 2026 release notes). Both shipped quietly into closed beta. Both will be on every Pro plan by Q4. The pattern is now obvious. Anthropic launched Claude Design in April 2026 and Figma's stock dropped 7% on the news (DesignRush, April 2026). Google shipped Stitch in March. v0 has been a working IDE since February 2026. Lovable's August 2025 Design View was the early signal. The shift is six tools deep before it even hit mainstream pricing.
The Figma file is now the starting prompt. The codebase is the artefact. If your team's process still treats the Figma file as the spec engineering ships from, you have built your design system into the wrong layer.
I have seen this play out twice in the last three months at the agency. One client was rebuilding a regulated UAE lottery product. Their design system lived in Figma. Their developers shipped from screenshots and Jira tickets. We moved tokens out of Figma into a code-resident library and reconnected the Figma file to that library as a mirror. The first agent-driven build cut handoff time on a new flow by 60% and removed five rounds of QA correction on spacing and typography alone. The Figma file did not stop existing. It stopped being the source of truth.
The second client was a MENA fintech. They had no design system in Figma at all. They had a working component library in their React codebase, undocumented, but stable. We pointed Claude at the codebase through the MCP server, not at Figma. We shipped four new screens in ten days that engineering signed off without a single design review meeting. The Figma file was a sketch. The system was the truth. That is the right shape.
Argument 1. The Source of Truth Moved
If your tokens, components, and spacing live in Figma and your engineers translate them by hand, you are paying tax twice.
Figma Make connects to your local codebase directly. Direct editing of the product, not the file (Figma release notes, May 2026). Claude Design and Stitch both treat code as the canonical output. The Figma file is a prompt, not the deliverable. v0's February 2026 update built a full in-browser IDE with Git integration. It does not need Figma at all to ship production-quality shadcn/ui components.
This is not a tooling preference. This is a contract change. The handoff layer just collapsed.
Argument 2. Your Design System Has to Live Where the Agents Read It
If it lives in Figma alone, agents have to translate. Translation is where drift happens.
A code-resident design system with MCP exposure is now the only credible setup. Tokens in code. Variants in code. Documentation in code. Figma mirrors the system, not the other way around. Vercel's design engineering function has shipped this way for two years. Linear has the cleanest version. They are the model, not the outlier. Vercel design engineers sit on a base band of $155k to $240k for a reason (Vercel Careers, 2026). They are the people writing the contract.
Argument 3. The Job at the Top of the Design Team Changed in May
The head of design's primary deliverable is no longer a deck or a roadmap. It is a runnable system with an exposed contract. If your senior designers cannot define that contract, they are about to become very expensive translators.
Figma's State of the Designer 2026 report has the receipt. 73% of hiring managers want AI tooling proficiency. 79% want experience designing AI products (Figma, State of the Designer 2026). The senior bias is real and stacking. The mid-career designer who can run a Figma file but cannot read a component spec is the one priced out of the market.
Argument 4. Most Teams Are Not Ready and the Lag Is Structural
Most product design orgs run their token system in Figma. Most engineering orgs treat the Figma export as the spec. There is no contract between the two layers. Agents make this gap fatal because they will write code against whichever source they can read first.
A reasonable benchmark: if your design system audit finds more than 30% of components have no code equivalent, agents will hallucinate around them. I have seen this exact failure in three audits in the last quarter. Two of those three were for products with stronger Figma libraries than codebases. The agent reads the code first, ignores the Figma library, and ships something off-brand. The designers spend a sprint fixing it. That is the bill you pay when the contract is broken.
Argument 5. There Is a New Category of Design Leader Emerging This Year
Not the design VP who runs critique. Not the head of design system who curates a Figma library. The systems architect who owns the contract between Figma, the codebase, the AI agents, and the engineering pipeline. That role does not have a clean title yet at most companies. It will by Q4. The senior IC who can build that contract gets paid like a principal engineer. The senior IC who cannot gets reclassified down a band.
Pushback
The obvious counter: agents are not good enough yet to be trusted with production code, so the file remains the source of truth. Half right.
The current generation of agents do drift, do hallucinate, do break tokens, do invent spacing. They are not yet writing production code without supervision. Fine. The argument is not that agents replace the file in the next six months. The argument is that your design system has to be readable by an agent today, because the agents are the new collaborators on the team and the budget conversation around design headcount will assume agent productivity within a year.
A second counter: small teams cannot afford to maintain a code-resident system. Also half right. Small teams cannot afford to maintain Figma and code separately either. The fix is to pick one canonical source. Pick code. Mirror it in Figma. Agents work with both.
A third counter, the one I get from heads of design every other week: this only matters for product orgs with mature engineering. Wrong. This matters more for early-stage and mid-market orgs. Those are exactly the orgs where one designer plus an agent is replacing a three-designer pod, and where the founder is asking why the design retainer costs the same as a junior engineer.
What I Would Do
If I were running design at a 25-person product team right now, I would put a designer with code muscle on the system contract this month. I would move tokens out of Figma into a JSON or CSS variable set in the codebase. I would expose components to an MCP server within six weeks. I would let agents touch low-stakes surfaces in production by Q3.
I would not let any designer ship a new component without it landing in code. I would not let any engineer ship a UI change without it landing in the design library. I would stop running design reviews on Figma files and start running them on shipped product.
The agency clients I am working with this year are getting more out of a senior designer with code fluency and an agent than they got out of a five-person design pod two years ago. That is not a story about AI replacing designers. That is a story about the deliverable changing. The teams that adjust first will eat the teams that don't.
The Figma file is not dead. It just stopped being the artefact. If your team is still treating it like the source of truth, you are running a 2023 process in a 2026 hiring market. Fix it before your CFO does.
Fact Check
Every factual claim in this article, with its source.
Claim: Figma Make entered closed beta on 28 May 2026 and the Figma agent rolled out to Full seat users on 20 May 2026, both connecting directly to production codebases.
Source: Figma, May 2026 release notes. figma.com
Claim: Figma's stock dropped roughly 7% the day Anthropic launched Claude Design on 17 April 2026.
Source: DesignRush, April 2026. designrush.com
Claim: Vercel's design engineer role carries a base salary band of $155,000 to $240,000.
Source: Vercel Careers, 2026. vercel.com
Claim: 73% of hiring managers want AI tooling proficiency and 79% want experience designing AI products.
Source: Figma, State of the Designer 2026. figma.com
Unsourced statements (Jay's opinion or lived experience): Jay's two agency case studies (the UAE lottery client design-system migration and the MENA fintech MCP-driven build); his claims about a 60% handoff-time cut and shipping four screens in ten days; his forecast about a new "systems architect" design leader role. These are Jay's points of view, not third-party data.