Source: raw/How_Reddit_s_designers_build_ultra-realistic_prototypes_with_Figma_+_Cursor.md

Creator: Claire Vo (How I AI) with Blair Metcalf, principal UX engineer at Reddit · URL: https://www.youtube.com/watch?v=zF-J3rMbzZw · Duration: not recorded · Platform: YouTube (fetched 2026-11-01)

Reddit built Reddit Proto, an internal harness that lets designers and PMs vibe-code prototypes inside Reddit’s real design system, render them with their own signed-in production data, and share them as installable links. A second path turns a Figma frame into a PRD and draft production code through a custom MCP that knows how every design token maps to production. Metcalf says the main payoff is “instant alignment” with leadership. The pattern transfers to any team with a design system: constrain the AI with your components and real data instead of letting it guess.

Key Takeaways

  • Hide Git from non-engineers. A desktop launchpad app creates a project, clones the boilerplate and names it; designers then work in any IDE without thinking about repos, branches or local servers. Every shipped feature is absorbed back into the shared starting app.
  • Controls built into every prototype. Feature toggles, the option to lock navigation (“some stakeholders click too much”), device and theme switches, and persona views such as moderator, for Reddit’s complex user types.
  • Real signed-in data, not mocks. Prototypes start on mocked data but can render the viewer’s own Reddit data. Reason: leadership shown a Figma mock with fake data says “This isn’t relevant to me.” Metcalf’s search demo pulls real results, sends them to an LLM to rank, and shows type-aheads; “you don’t have to take 9 months to get that into prod, see if that works.”
  • Annotate, then send to Cursor. Click a component, write an annotation (“make relevant type-aheads, trending, recent communities”), add an overall direction, and “send to Cursor” writes a file with the code location, the annotation and the direction; telling Cursor “apply annotations” makes a targeted edit using the design system’s tokens and components.
  • Deploy and share without engineering. The launchpad deploys to internal Kubernetes infrastructure (“basically like an internal Vercel”); prototypes are shared by URL on Slack, or by QR code to a phone after a security step, where they run as PWAs.
  • Adoption numbers. About 700 prototypes sit on a shared dashboard (a searchable console with tags, teams and iOS/Android types is in progress); 100% adoption across UX and product, about 150 people, split nearly evenly between designers and PMs. A visual designer and an animator turned out to be among the best prototypers, which Metcalf attributes to being good “directors” with broad context.
  • Feature capsule: Figma frame to PRD to draft PR. Copy a Figma frame link, create from Figma via the Figma MCP, and a custom team MCP maps the frames to the design system and to production code, then writes a PRD (user goal, acceptance criteria, Figma links). Cursor builds from the PRD in a sibling repo “to keep prod clean” and opens a draft PR for normal review. They tried “kitchen sink” multi-surface inputs and went back to high-fidelity single UI frames.
  • The MCP learns from CI and reviewers. The team mapped its design system to production with Code Connect, submitted PRs, and fed failed CI checks and engineer review comments back into the MCP: “start with a map and then you try, fail, iterate.”
  • A visual “Rosetta Stone” to verify coverage. A visualization of every token, component, surface and journey in RPL (Reddit Product Language), showing each token across Figma, iOS, the GitHub codebase and the prototype repo and flagging value mismatches. It exists so the team could see the harness, and therefore the MCP, had all the parts.
  • The PRD stays the handoff. “It is the perfect handoff. It has all the context.”
  • Prompting tip when the model stalls. Metcalf steps out of the project, describes the problem broadly “like a movie director” (all the facts, then all the intents), then brings that back in: “I become a better director that is more vague, not specific.”

Try It

  1. Give your prototyping agent your design system as tools, not prose: an MCP or skill that can look up tokens, components and example usage, so it stops inventing components.
  2. Add a real-data mode to one prototype (read-only, signed-in as the viewer) and show it to a stakeholder next to the mock-data version.
  3. Pipe stakeholder comments into edits: capture component location plus comment plus overall direction in a file the coding agent reads, the same shape as Reddit’s annotations. Drawbridge is an off-the-shelf version of click-to-annotate.
  4. Write generated production code to a sibling repo and open draft PRs only, so CI and reviewers stay the gate.

Open Questions

  • The custom MCP is captioned “proto MCP ultra”; its real name and tool list were not shown, and the code itself was not shown on screen.
  • How the signed-in production-data mode is secured for prototypes shared externally is described only as “you go through some security”.