Why Reddit built its own AI prototyping tool | Blair Metcalf
- ID
- 39532
- Status
- summarized
- Published
- 26 Oct 2026, 8:04 PM
- Fetched
- 26 Oct 2026, 9:36 PM
- Provider
- Lenny's Newsletter
- Category
- product-startup
- Original URL
- https://www.lennysnewsletter.com/p/why-reddit-built-its-own-ai-prototyping
- Source URL
- https://www.lennysnewsletter.com/feed
Summary
- Score
- 7.5
- Created
- 26 Oct 2026, 9:37 PM
- Tags
- Audience
- developersvibe_codersai_agent_usersstartup_founders
What happened
Blair Metcalf, principal UX engineer at Reddit, describes Reddit Proto, an in-house vibe-coding harness built on a custom Figma MCP plus Cursor that takes a designer from blank slate to a shareable, production-shaped prototype without touching Git. Proto reportedly hit 100% adoption across Reddit's UX and product org with 700+ live prototypes, using a design-system MCP as a 'Rosetta stone' that maps Reddit's product language to real production code, an annotation-to-targeted-Cursor-edit loop, real Reddit data instead of mock data, and a 'feature capsule' artifact for engineering handoff.
Why it matters
The reusable pattern here isn't the tool, it's the design-system MCP: mapping your own component vocabulary to production code so generated output matches your codebase instead of generic React. If you're standing up internal AI prototyping, the decisions to copy are annotation-driven targeted edits (rather than whole-file regeneration), real data over mock data for leadership review, and a defined handoff artifact (the 'feature capsule') so prototypes don't dead-end at demo stage.
Discussion angle
What would go in your team's 'Rosetta stone' MCP — and what's the smallest version worth building (one design system, one repo, one deploy target) versus just letting designers prompt Cursor raw?