Reddit got 100% of its design team onto a tool it built, not Figma

Reddit gave 100% of its UX and product team a tool it built itself, and 700 live prototypes are running on it. Designers are canceling Figma subscriptions. Some teams now write their design system in code first and treat Figma as a copy. Something in the tooling stack is moving, and it is worth your attention before your next planning cycle. Let me catch you up.

The deep cut

• Code is the source of truth, Figma is the mirror. One design systems designer flipped the arrow so AI reads real props, not Figma's guesses.
• Build your own harness when the stack does not fit. Reddit's Blair Metcalf shipped Reddit Proto and hit 100% team adoption.
• AI generates in minutes and verifies for hours. A two-day hackathon showed review, not generation, ate the time.

The repository nobody opens

Here is the quiet pain with Figma-to-code AI. A Figma file was always an abstraction. One designer sat down and compared what a React component can express versus a Figma component and got about 17% coverage. For CSS it was around 45%. The rest, focus order, error states, what a screen reader says, lives in a developer's head.

A human developer notices what is missing and walks over to ask. An AI does not. It takes the file literally, fills the gaps with whatever it has seen most, and hands back a component that looks finished and is partly invented. None of that shows up in a screenshot, so nobody catches it in review.

So the fix is to turn the arrow around. The design system starts in code, and Figma gets generated from it. Code wins, Figma mirrors, and where they differ, Figma is wrong. That reads like a demotion for Figma. In practice the Figma file got busier, not smaller.

Reddit built its own

When your stack does not fit, you can build the tool yourself. Blair Metcalf, principal UX engineer at Reddit, built Reddit Proto, an in-house vibe-coding harness. It has reached 100% adoption across Reddit's UX and product org, with more than 700 prototypes live.

The piece that makes it work is a design system MCP that maps Reddit's product language to production code, what Metcalf calls a Rosetta stone. Prototypes run on real Reddit data, not mock data. A designer can leave an annotation that becomes a targeted code edit in Cursor. The output is close enough to engineering that it ships as a feature capsule.

The lesson for you is not "go build your own tool next week." It is that the interesting work now lives in the connection between your design system and the AI, not in any one app. Reddit invested there and got a workflow nobody wants to leave.

The bill comes at verification

The speed story has a catch worth putting in your estimates. A two-day hackathon using ChatGPT, Claude, and Copilot found that generation happened in minutes while verification ate most of the time, as Patrick Neeman's round-up recounts. Things that looked nearly done early needed heavy checking before they actually worked.

Interviews with 32 design leaders in the same round-up landed on one recurring theme: design outputs sped up, but the judgment behind them did not. If you plan a roadmap on generation speed, you will miss. Budget the review, validation, and quality time, because that is where the real effort now sits.

This is also your argument when someone asks you to halve a timeline. Faster drafts do not mean faster decisions.

Figma is not sitting still

The defections are real but uneven. One designer canceled their Figma subscription, citing low ROI, and now uses it mainly to document screens and flows. Another is relearning Axure because it builds richer interactive prototypes for usability studies than Figma does.

Figma knows the ground is shifting. At its first Config in India it added 20 new MCP partners, including Linear, Notion, and Mistral. But co-founder Dylan Field said plainly that MCP "is not a perfect protocol," that it favors frontier labs, and that exposing more data raises the risk of abuse.

Read that as a company opening up and holding back at the same time. Your AI workflow will depend on how far Figma, and the protocol it half-trusts, actually opens the door.

Three questions for your team

• Where does our design system truth actually live, in code or in Figma, and does our AI read the real props or guess at them?
• Are our project estimates built on generation speed, and if so, where in the plan is the time for verification and review?
• If we lean harder on MCP and AI tooling, which parts of our stack are we betting on, and what happens to that bet if Figma keeps its data half-closed?