Back to episodes
Claude Code vs Figma Make
This episode is in Finnish. The video below is the original recording; this page provides an English summary for easier reading.
Summary
Why Claude Code has edged out Figma Make in daily design work: Mikki and Tuomas compare speed, interactions, workflows, and where Figma still wins.
About The Good Side in this episode
Mikki and Tuomas share how Claude Code changed design practice: less mechanical Figma drawing, more concept thinking, more interaction design, and more systematic documentation than before.
Key discussion points
- With Claude Code, designers spend less time on mechanical Figma drawing and more on actual thinking
- Visual work like design tokens and color palettes still happens in Figma because it is faster there
- Interaction design has grown because building interactions no longer requires hand-assembly in Figma
- Claude Code acts as project memory: task lists, meeting notes, and open questions before client calls
- Meeting transcripts are refined with Claude Code before storage; raw dumps are not saved as-is
- Usability and accessibility agents are next: Nielsen heuristics can be fed straight to an agent
Questions & answers
- Will Claude Code replace Figma entirely?
- Not yet. Figma is still faster for visual design, tokens, and color evaluation. Claude Code takes interaction design and functional builds; Figma keeps quick visual iteration.
- What does Claude Code change in a designer’s day?
- Less mechanical execution. While Claude Code runs, you test what is already built and capture new ideas. Thinking and testing take more time; drawing takes less.
- Can agents automate usability testing?
- In principle, yes. You can give an agent Nielsen heuristics or similar guidelines to review a PR before release. First experiments need setup time, but the concept works.
Topics: Claude Code, Figma Make, design workflow, interaction design, design agents, usability agent, The Good Side, Behind the Pixels, design tokens, AI-assisted design, UX design tools