From Figma to Claude Code and back | Gui Seiz & Alex Kern (Figma)
Episode
40 min
Read time
2 min
Topics
Design & UX, Artificial Intelligence, Software Development
AI-Generated Summary
Key Takeaways
- ✓Figma MCP as sync bridge: Use the Figma MCP server connected to Claude Code or Codex to programmatically pull live app states directly into Figma frames. This eliminates the chronic divergence between production code and design files, letting designers manipulate real UI states with direct drag-and-drop precision rather than describing changes in words.
- ✓Code-to-Figma state extraction: When a codebase contains UI states that have no corresponding design file representation, engineers can prompt Claude Code to identify and export all variants simultaneously. For example, sending five sign-up flow states into a single Figma document, laid out side by side, gives design collaborators an accurate working canvas without any manual screenshotting or recreation.
- ✓Custom slash-skills to automate engineering toil: Alex Kern writes personal Claude Code skills, including a slash-ship command that runs preflight checks, executes Bazel builds, pushes to Git, monitors BuildKite CI, auto-fixes minor lint issues across up to five retry attempts with a one-hour timeout, and alerts on credential exposure — all without the engineer watching the terminal.
- ✓Convert internal Wiki SOPs into team-wide skills: Every engineering onboarding document, pre-PR checklist, or best-practice guide buried in Confluence or GitHub can be converted into a Claude Code skill and committed to the shared repository. This transforms institutional knowledge from passive documentation into automated, consistently enforced workflow steps accessible to the entire team by default.
- ✓Parallel Claude Code instances for throughput: Running two to five simultaneous Claude Code sessions on separate workstreams — one reconciling design-to-code changes, others writing specs, answering codebase questions, or handling exploratory tasks — multiplies effective engineering output without context-switching. This approach treats the AI as concurrent workers rather than a single sequential assistant.
What It Covers
Figma engineers Gui Seiz and Alex Kern demonstrate bidirectional workflows between Figma and Claude Code using the Figma MCP server, showing how design and code can stay synchronized without manual handoffs, enabling designers and engineers to collaborate on live states rather than static artifacts.
Key Questions Answered
- •Figma MCP as sync bridge: Use the Figma MCP server connected to Claude Code or Codex to programmatically pull live app states directly into Figma frames. This eliminates the chronic divergence between production code and design files, letting designers manipulate real UI states with direct drag-and-drop precision rather than describing changes in words.
- •Code-to-Figma state extraction: When a codebase contains UI states that have no corresponding design file representation, engineers can prompt Claude Code to identify and export all variants simultaneously. For example, sending five sign-up flow states into a single Figma document, laid out side by side, gives design collaborators an accurate working canvas without any manual screenshotting or recreation.
- •Custom slash-skills to automate engineering toil: Alex Kern writes personal Claude Code skills, including a slash-ship command that runs preflight checks, executes Bazel builds, pushes to Git, monitors BuildKite CI, auto-fixes minor lint issues across up to five retry attempts with a one-hour timeout, and alerts on credential exposure — all without the engineer watching the terminal.
- •Convert internal Wiki SOPs into team-wide skills: Every engineering onboarding document, pre-PR checklist, or best-practice guide buried in Confluence or GitHub can be converted into a Claude Code skill and committed to the shared repository. This transforms institutional knowledge from passive documentation into automated, consistently enforced workflow steps accessible to the entire team by default.
- •Parallel Claude Code instances for throughput: Running two to five simultaneous Claude Code sessions on separate workstreams — one reconciling design-to-code changes, others writing specs, answering codebase questions, or handling exploratory tasks — multiplies effective engineering output without context-switching. This approach treats the AI as concurrent workers rather than a single sequential assistant.
Notable Moment
Alex Kern revealed he uses Claude Code to excavate the origin story of an internal Figma service whose creator had long since left the company. By querying commit history through Claude, he recovered naming history and context that had been entirely lost — treating the codebase as institutional memory.
Episode Transcript
The energy that we've rediscovered around those spikes where we're all just prototyping and throwing it all into the same place, momentum begets momentum. And so having the team together riffing and yes anding and trying the stuff out is really great. This feels like pair programming for designers and engineers, and you can work very quickly back and forth using the MCP as a connector here. Oftentimes, the code base gets way ahead of where the actual design file is, and there's states or workflows that just don't exist at all within the design file. So what I can do is say, send all five states. Sign up flow to click on. Now the agent's going to do is read my code base, understand what I'm referring to when I say those five states. And for each one of those, it's going to individually import that one by one into Figma such that the Figma document will then have all of those states laid out all side by side so that my design partner can work against against it. It's definitely changed our workflows in a way that it's kinda really blown up what a workflow even is. I spend quite a lot of my time just sitting here inside of my terminal now. I often have two, three, up to five maybe cloud code instances running all at the same time, working on different aspects of the work that I'm tracking. Welcome back to How I AI. I'm Claire Vaux, product leader and AI obsessive, here on a mission to help you build better with these new tools. Today, we have Alex, an engineer, and Guy, a designer from Figma, and they're gonna show us the new world and the new workflows of design, code, and back to design. I'm really excited about this one because it's gonna show you how more forward looking teams are thinking about the interplay between design and engineering teams, how designs don't have to be static artifacts either in Figma or in code, and we're gonna get some tips and tricks on how you can use skills in your repo to take away toil, both for engineers and for designers. Let's get to it. This episode is brought to you by Optimizely. Most marketing teams aren't short on ideas, but what they are short on is time. And that's exactly what Optimizely Opal gives you back. With AI agents that handle real marketing workflows, you know, like creating content and checking compliance, generating experiment variations, personalizing user experiences, analyzing pages for GEO, even tasks like approvals and reporting. It's your AI agent orchestration platform for marketing and digital teams, plugging seamlessly into the tools you already use, handling the boring busywork, and keeping everything on brand. That leaves marketers with more time to do your actual job. See what Opal can automate for your team by signing up for a free enterprise agentic AI workshop with Optimizely. Find out more at optimizely.com/howiai. …
Get the full transcript (7,603 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 37-minute episode.
Get How I AI summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from How I AI
Build your own company brain: the enterprise AI playbook from Stripe’s engineering team | Sharadh Krishnamurthy
Sep 7 · 50 min
Marketing Against the Grain
Stop Prompting: Build an AI "Design App" Instead (Demo)
Feb 3
More from How I AI
GPT-6 Astra is a banger - here’s everything I’ve built
Sep 3 · 32 min
The Startup Ideas Podcast
Clawdbot Clearly Explained (and how to use it)
Jan 27
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
“a slash-ship command that runs preflight checks, executes Bazel builds, pushes to Git, monitors BuildKite CI”
“Alex Kern writes personal Claude Code skills, including a slash-ship command that runs preflight checks, executes Bazel builds, pushes to Git”
by Figma
“Figma engineers Gui Seiz and Alex Kern demonstrate bidirectional workflows between Figma and Claude Code using the Figma MCP server, showing how design and code can stay synchronized without manual handoffs.”
“a slash-ship command that runs preflight checks, executes Bazel builds, pushes to Git, monitors BuildKite CI”
by Anthropic
“bidirectional workflows between Figma and Claude Code using the Figma MCP server, showing how design and code can stay synchronized”
by Figma
“Use the Figma MCP server connected to Claude Code or Codex to programmatically pull live app states directly into Figma frames.”
by Figma
“Figma engineers Gui Seiz and Alex Kern demonstrate bidirectional workflows between Figma and Claude Code using the Figma MCP server”
by Atlassian
“Every engineering onboarding document, pre-PR checklist, or best-practice guide buried in Confluence or GitHub can be converted into a Claude Code skill”
company
“SPONSORS: Optimizely”
More from How I AI
We summarize every new episode. Want them in your inbox?
Build your own company brain: the enterprise AI playbook from Stripe’s engineering team | Sharadh Krishnamurthy
GPT-6 Astra is a banger - here’s everything I’ve built
Grok Bot vs. OpenClaw: How I replaced my entire agent stack
How I turned Claude into a self-improving PM assistant | Daniel Blum (PM, Melio)
I spent $20,000 on Devin in a month. Here’s what I learned | Ryan Carson (solo founder)
Similar Episodes
Related episodes from other podcasts
Marketing Against the Grain
Feb 3
Stop Prompting: Build an AI "Design App" Instead (Demo)
The Startup Ideas Podcast
Jan 27
Clawdbot Clearly Explained (and how to use it)
Eye on AI
Sep 8
86% of What Coding Agents Do Is Just Reading — Not Solving | Alexander Whedon of Subquadratic
The AI Breakdown
Sep 6
How to Build an AI-Native Company Today
a16z Podcast
Apr 20
Rethinking Git for the Age of Coding Agents with GitHub Cofounder Scott Chacon
Explore Related Topics
This podcast is featured in Best AI Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into How I AI.
Every Monday, we deliver AI summaries of the latest episodes from How I AI and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime