
#161 700 Components in One Day: How Design Work Is Quietly Moving Into Code
A client of mine just rebuilt their entire Figma design system — roughly 700 components — as code components in Claude Code. It took one day. And now their designers prototype in code, while Figma has become the tool they open "when they occasionally need to design something."
In this episode, I unpack what this story reveals about where our jobs are heading. The "should designers code?" debate is over — but we didn't end it. The job market did. And the way our roles are changing isn't arriving as a memo. It's arriving as convenience.
In this episode:
- Why prototyping in the real system (instead of a Figma simulation) is a genuine qualitative leap — and why the design-to-dev handoff gap just disappeared
- The four quiet problems nobody talks about: fast isn't faithful, two sources of truth, the illusion of production-ready, and the question of where invention lives now
- Why role creep in 2026 doesn't come from your boss — it comes from your tools
- The one question that matters more than "should designers code?": are you building the mental model, or just orchestrating outputs?
- Your homework: pick one workflow change that happened "by itself" and choose it on purpose
AI for Designers: 5-week Bootcamp 💻 opening September
→ Sign up for the waiting list
👉 0€ Training: Build your first Claude Skill in 10 min 👈
→ Build your first Claude skill in 10 min
💌 Newsletter
Follow the Future of UX:
🎨 Linkedin: Future of UX Podcast
📸 Instagram: Future of UX Podcast
🍏 Apple Podcast: Future of UX
💚 Spotify: Future of UX
Find Patricia on Socials
🎥 Youtube
More episodes from "Future of UX | Your Design, Tech and User Experience Podcast | AI Design"



Don't miss an episode of “Future of UX | Your Design, Tech and User Experience Podcast | AI Design” and subscribe to it in the GetPodcast app.








