Context
Blair Metcalf is principal UX engineer at Reddit and the builder of Reddit Proto, an internal prototyping harness for PMs and designers. Reddit Proto wraps AI coding in Reddit's design system, internal deployment flow, and a custom mapping layer that links Figma, design tokens, components, and production code. The episode matters to PMs because it shows how to move prototyping from isolated mockups to production-like artifacts that leaders can review, engineers can hand off from, and non-engineers can create safely. It is also a concrete example of using AI by adding constraints and context, not by giving everyone raw access to a repo and hoping for the best.
The Big Idea
Reddit did not get value from AI prototyping by giving people more freedom. It got value by building a harness that keeps PMs and designers on rails, uses real Reddit data, and maps design language to production code.
That combination makes prototypes credible enough for leadership review and useful enough for engineering handoff. For PMs, the lesson is that better prototyping comes less from prompting skill alone and more from building the right system around the model.
Key Insights
Constrained harness unlocks prototyping
- Reddit built a desktop app that starts a new project without asking PMs or designers to clone repos, manage branches, or run local setup.
- The scaffold loads boilerplate, design-system components, and sample features, so the first screen is a working prototype environment rather than a blank IDE.
- Blair's goal was to let teams generate many ideas quickly, review them, then spend engineering time only on the concept that survives review.
- For PMs, the product lesson is that AI prototyping adoption often depends more on removing setup friction than on model quality.
Real data changes reviews
- Reddit product surfaces are personalized, so static Figma mocks often look irrelevant to leaders reviewing their own experience.
- Reddit Proto can render signed-in data, which lets leaders click through a prototype using content, communities, search results, and states that feel real.
- Blair said this creates instant alignment because leaders react to the product concept instead of arguing about fake content or getting distracted by gotcha details.
- Example: Blair added search typeaheads, recent searches, and community suggestions inside the prototype, pulling real data, sending it to an LLM for ranking, and testing the experience without shipping production code.
Annotations become targeted edits
- Reddit Proto lets a user click on a surface, add an annotation, and send that request to Cursor.
- The annotation carries location, component context, and an overall direction, so Cursor receives a narrow edit request instead of an open-ended prompt.
- Blair's example was simple but telling: he annotated a search box and asked for relevant typeaheads, trending, recent, and communities, and Cursor generated the change on the spot.
- For PMs, the insight is that AI coding works better when feedback is attached to a precise UI surface, not handed over as a paragraph in Slack.
Public sharing drives adoption
- Internally, prototypes are public by default, shareable by URL, and in some cases shareable externally through a QR flow with security checks.
- Reddit already had about 700 live prototypes in the system, with 100% adoption across the UX and product org and usage across more than 150 people.
- Leadership reviews happen directly in the prototype, and feedback currently comes live or through Slack, with inline commenting planned next.
- Public prototypes also create organizational visibility, which is why Reddit is building a searchable console by team, feature area, platform, and tags.
Feature capsules improve handoff
- Reddit's next step after a prototype is a feature capsule. A user selects a Figma frame, runs it through Figma MCP, and generates a package that maps the design to Reddit's production-shaped code.
- The feature capsule also produces a PRD with user goals, scope, acceptance criteria, Figma links, and workflow details.
- Blair said the PRD matters because it becomes the handoff to engineering. It gives engineers the context behind the code generation, not just the UI output.
- Production safety still matters: generated code is written to a sibling repo first, then reviewed through normal draft PR flow rather than pushed straight into production.
Great prototypers come from anywhere
- Reddit expected strong usage from designers and PMs, and Blair said the split is almost even between the two groups.
- The surprise was who excelled. A visual designer and an animator became some of the best prototypers.
- Blair's explanation was not about job title. The best users had broad context, could direct the system clearly, and were willing to try things without worrying about failure.
- For PM leaders, that suggests AI prototyping ability may correlate more with taste, context, and direction-setting than with formal coding experience.
Mental Models & Frameworks
Build rails, not freedom
- Reddit Proto is built on the idea that most PMs and designers should not start in a raw codebase.
- Good constraints include preloaded components, state toggles, persona switches, and deploy-by-default sharing.
- Use this model when the goal is idea generation and review quality, not teaching everyone software engineering basics.
Map language to code
- Blair's Rosetta stone is a visual map that connects Reddit product language, design tokens, components, surfaces, journeys, Figma, iOS, GitHub, and the prototyping repo.
- He built it as a visual verification layer. The team could see whether the harness and MCP actually contained the parts they thought they contained.
- Use this model when AI output is unreliable because design language and code language do not share a trusted source of truth.
Use feature capsules
- Step 1: select the high-fidelity Figma frame or flow that matters.
- Step 2: run that selection through Figma MCP and the design-system mappings to generate a feature capsule and PRD.
- Step 3: send the package to Cursor to write production-shaped code, then review it through the normal PR flow.
- Blair's update is important: narrower, high-fidelity selections work better than dumping in every possible surface.
Step back when AI stalls
- Blair's reset move is counterintuitive. He gets more vague, not more specific.
- He exits the crowded project context, describes the facts and intent at a higher level like a movie director, then pastes that framing back into the AI project.
- Use this when a coding model is stuck in local edits or following the wrong path. A better statement of user intent can reorient the model better than another tiny instruction.
Decision Principles
Principle: Show real context
- When: presenting a personalized product to leaders or partners.
- Why: leaders judge whether a feature feels relevant to them. Mocked content creates weak feedback, while real signed-in data makes the review concrete.
Principle: Hide tooling complexity
- When: expanding prototyping beyond engineers.
- Why: Reddit got adoption by hiding cloning, branching, local setup, and deployment behind a simple launchpad. The power stayed in Cursor and the infra, but the first-time user only saw a product-like interface.
Principle: Get broader, then specific
- When: a coding model keeps missing the point despite very detailed prompts.
- Why: Blair resets by restating the facts and intent at a director level outside the project context, then reintroducing that framing. More detail is not always more guidance.
Trade-offs & Nuance
Realism needs safety rails
- Real data and production-shaped code make prototypes more persuasive, but they also raise security and safety concerns.
- Reddit addresses this with internal deploy infrastructure, external sharing checks, and by writing generated production code to a sibling repo rather than directly into the production repo.
- A PM adopting similar tactics needs to decide where realism is worth the operational risk.
More context can backfire
- Reddit tried the kitchen sink approach, feeding many surfaces and broad context into the handoff flow.
- Blair said the team is moving back toward high-fidelity UI selections because narrower inputs produce more accurate output.
- The product lesson is that more context is not automatically better. The right context is specific, structured, and close to the surface being changed.
Openness needs private modes
- Public-by-default internal prototypes improve discovery and leadership visibility.
- Blair also acknowledged that Reddit Proto still needs a way to work under the radar for skunkworks ideas.
- The trade-off is between organizational learning and creative privacy. A mature prototype platform needs both.
Practical Application
Create a one-click launchpad
- Build a thin wrapper around your preferred coding environment that creates a new prototype from a known scaffold.
- The scaffold should pre-load design-system components, sample states, and deployment defaults so a PM or designer starts inside a working product shell.
- The goal is not elegance. The goal is to remove Git, branch, and local setup work from first-time prototype users.
Add live-data review paths
- If your product is personalized, add a safe way for prototypes to render signed-in or production-like data.
- Limit the feature to internal reviewers first, and make it obvious when a prototype is using live data versus mock data.
- This is most useful for leadership reviews, where fake content often causes irrelevant feedback or weak conviction.
Use annotation-driven edits
- Replace vague feedback threads with UI-linked annotations that capture the surface, the requested change, and the overall intent.
- Send those annotations to a coding agent as structured input, not as free text copied from chat.
- Even without a custom harness, a PM can start this workflow by screenshotting a surface, marking the exact area, and writing one precise change request per annotation.
Generate PRDs from UI
- For any prototype that survives review, generate or write a short PRD from the chosen Figma frames or prototype flows.
- Include user goal, scope, acceptance criteria, linked designs, and any states or roles the engineer must support.
- Blair's point was that AI-generated code alone is not the handoff. The PRD plus mapped UI context is the handoff.
Index prototypes like products
- Once a team has dozens of prototypes, discovery becomes its own product problem.
- Add tags for feature area, team, platform, and status so leaders and peers can find related work instead of rebuilding it.
- Reddit hit this scaling issue at around 700 prototypes, which is why the searchable console became a priority.
Questions to Consider
- Where does your team still ask leaders to react to static mockups when a production-like prototype with real user data would create better alignment?
- Which part of your prototyping workflow still requires PMs or designers to learn Git, branches, deployment, or repo structure before they can test an idea?
- What pieces of your design system are still invisible to AI coding tools, forcing the model to guess instead of using known tokens, components, and workflows?
- If your company made internal prototypes public by default, what would people discover faster, and what skunkworks or privacy controls would you need to add first?
- When an AI coding tool gets stuck on a local fix, would stepping out and restating the broader user goal and intent help more than adding another hyper-specific prompt?
Bottom Line
Reddit's lesson is that AI prototyping gets powerful when it is constrained, contextual, and connected to real product systems. A harness with real data, mapped design tokens, and structured handoff can turn PMs and designers into credible builders without asking them to become engineers.
Tools & Products
| Tool / Product | What it does | Why it was mentioned |
|---|---|---|
| Reddit Proto | Internal prototyping harness built at Reddit | The central system Blair demos. It puts PMs and designers inside a production-like scaffold and deploys shareable prototypes. |
| Cursor | AI coding IDE | Annotations from Reddit Proto are sent to Cursor, which applies targeted code edits. |
| Figma | Design and interface tool | Reddit uses Figma frames as the source for feature capsules and PRD generation. |
| Figma MCP | Model Context Protocol integration for Figma | Used to turn selected Figma frames into the input for a feature capsule and design-to-code workflow. |
| Code Connect | Figma code mapping tool | Helps map design system tokens and components between Figma and production code. |
| Kubernetes | Container orchestration platform | Powers Reddit's internal deployment layer, which Blair described as similar to an internal Vercel. |
| Vercel | Deployment platform | Mentioned as the inspiration for the internal deploy experience Reddit built for prototypes. |
People to Follow
Blair Metcalf
Blair Metcalf is principal UX engineer at Reddit and the builder of Reddit Proto. He is especially relevant for PMs and design leaders interested in AI prototyping harnesses, design-system-to-code mapping, and practical ways to let non-engineers build production-like product artifacts safely.
