
How Notion designers ship live prototypes in minutes | Brian Lovin (Product designer)
Brian Lovin (guest), Claire Vo (host)
In this episode of How I AI, featuring Brian Lovin and Claire Vo, How Notion designers ship live prototypes in minutes | Brian Lovin (Product designer) explores notion’s designer-led Next.js playground accelerates prototyping with Claude Code Brian Lovin (Notion AI designer) argues B2B SaaS design improves when prototypes “encounter reality” early—ideally in the browser, not only in Figma.
Notion’s designer-led Next.js playground accelerates prototyping with Claude Code
Brian Lovin (Notion AI designer) argues B2B SaaS design improves when prototypes “encounter reality” early—ideally in the browser, not only in Figma.
Notion’s internal “Prototype Playground” is a simple shared Next.js repo where each designer/PM/engineer has namespaced folders for standalone prototypes, enabling visibility and easy reuse of code patterns across the team.
Brian demonstrates an AI-assisted workflow with Claude Code: planning first, using voice-to-prompt, leveraging project-level and local Claude instruction files, and creating reusable slash commands and skills.
Advanced automation includes MCP-driven Figma-to-code generation with an iterative verification loop and a deploy command that creates branches/PRs, runs checks, and monitors CI to reduce onboarding friction for less-technical designers.
Key Takeaways
Design quality rises when prototypes hit “reality” earlier.
Lovin frames design as a gradient from napkin to production; moving toward real browser behavior sooner reveals issues like loading states, responsiveness, and interaction flaws that static mocks hide.
Get the full analysis with uListen AI
A shared prototype repo creates compounding leverage for a design org.
Keeping all prototypes in one Next. ...
Get the full analysis with uListen AI
“Nothing magical” beats “perfect tooling” for adoption.
Prototype Playground succeeds by being straightforward (Next. ...
Get the full analysis with uListen AI
Plan-first prompting produces better agentic coding outcomes.
Lovin consistently uses Claude Code’s plan mode and emphasizes reading the plan—especially valuable for catching wrong assumptions before code is written.
Get the full analysis with uListen AI
Treat every AI request as a prompt to automate the workflow.
His guiding rule: if Claude asks you to check something (browser, lint, CI), teach it to do that itself via commands, tools, or scripts—leading to longer autonomous runs and fewer human interruptions.
Get the full analysis with uListen AI
Project context should be standardized globally and personalized locally.
A committed claude. ...
Get the full analysis with uListen AI
Slash commands and skills turn tribal knowledge into reusable interfaces.
Commands like /create-prototype, /figma, and /deploy encode best practices (structure, verification, prerequisites), while skills like “Find Icon” + scripts mitigate recurring hallucinations (e. ...
Get the full analysis with uListen AI
AI product UX is hard to design in Figma alone—prototyping with real models is essential.
For AI chat experiences, golden-path Figma conversations break down when models stall, ask follow-ups, or error; code prototypes connected to real models surface the true UX needs (progress, errors, recovery).
Get the full analysis with uListen AI
Notable Quotes
“You want your designs to encounter reality as early as possible.”
— Brian Lovin
“I can prototype faster. I can prototype in production.”
— Brian Lovin
“There’s no back end for Prototype Playground. It’s just all files on disk.”
— Brian Lovin
“Any time the AI asks you to do something, you should… see if you could teach the AI to answer that question for itself.”
— Brian Lovin
“Do you know that I used to have to walk uphill both ways for my CSS?”
— Claire Vo
Questions Answered in This Episode
What specific shared components/styles made prototypes feel “Notion-y” fastest, and which were intentionally left out to avoid over-structuring?
Brian Lovin (Notion AI designer) argues B2B SaaS design improves when prototypes “encounter reality” early—ideally in the browser, not only in Figma.
Get the full analysis with uListen AI
How is the Prototype Playground homepage list generated from per-prototype metadata, and what conventions prevent collisions across users?
Notion’s internal “Prototype Playground” is a simple shared Next. ...
Get the full analysis with uListen AI
Your /figma command uses a “verification loop” with Chrome DevTools MCP—what checks does it run to decide the implementation matches the Figma frame, and what are the common failure modes?
Brian demonstrates an AI-assisted workflow with Claude Code: planning first, using voice-to-prompt, leveraging project-level and local Claude instruction files, and creating reusable slash commands and skills.
Get the full analysis with uListen AI
You said MCP is “context inefficient” and can run forever—what concrete guardrails (limits, truncation strategies, tool scoping) helped keep it reliable?
Advanced automation includes MCP-driven Figma-to-code generation with an iterative verification loop and a deploy command that creates branches/PRs, runs checks, and monitors CI to reduce onboarding friction for less-technical designers.
Get the full analysis with uListen AI
For designers without engineering backgrounds, which onboarding step is the biggest drop-off: Git/branches, running locally, or understanding Next.js/React structure?
Get the full analysis with uListen AI
Transcript Preview
The way I think about designing B2B SaaS is you want your designs to encounter reality as early as possible. I've always been into prototyping, and then all of a sudden, these AI coding tools come along, and now I can prototype faster. I can prototype in production.
So explain to us what this prototype playground is.
It's just a Next.js app. All of our prototypes are in one place. Seeing what other people are working on is really fun and interesting, and oftentimes, you spot cool ideas, and you're like: "Ooh, I want to try that." The code is all in one place. It's just in one repo, and so I can just yoink cool ideas from other people's prototypes and incorporate them into mine.
Every time somebody is, like, a little anti-AI-assisted coding, I'm like: "Do you know that I used to have to walk uphill both ways for my CSS?" It was not fun [chuckles] to do this.
I mean, even just sitting here watching this, I still just find this magical.
[upbeat music] Welcome back to How I AI. I'm Claire Vo, product leader and AI obsessive, here on a mission to help you build better with these new tools. Today, we have a designer-centric episode with Brian Lovin, designer at Notion AI, who's gonna show us how he set up a prototype playground for the entire Notion design team to vibe code using Claude Code any prototype they need. This is a great one for someone looking to either shift their design organization into a code-first prototyping mode or learn some advanced techniques with Claude Code. Let's get to it. This episode is brought to you by WorkOS. AI has already changed how we work. Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically. But there's a catch: these tools only work well when they have deep access to company systems. Your copilot needs to see your entire code base. Your chatbot needs to search across internal docs, and for enterprise buyers, that raises serious security concerns. That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features. Building all that from scratch, it's a massive lift. That's where WorkOS comes in. WorkOS gives you drop-in APIs for enterprise features so your app can become enterprise-ready and scale upmarket faster. Think of it like Stripe for enterprise features. OpenAI, Perplexity, and Cursor are already using WorkOS to move faster and meet enterprise demands. Join them and hundreds of other industry leaders at workos.com. Start building today. Brian, welcome to How I AI. What I am so excited about in terms of our conversation today is you're gonna show us about how one of the best-designed products out there, Notion, is being designed by people like you using these new AI tools like Claude Code. So why did you make this shift to how you were doing design, what it meant to prototype, design, and build things, especially for a product and in a company who values design so highly?
Install uListen to search the full transcript and get AI-powered insights
Get Full TranscriptGet more from every podcast
AI summaries, searchable transcripts, and fact-checking. Free forever.
Add to Chrome