The “Figma is dead” takes started the moment Claude Design shipped - a few shorts weeks ago. They’re wrong. But something is dying, and it’s worth calling it out.
This is the generated companion piece to the latest episode of Acquired Taste, where Jeremy and David spent an hour working through Claude Design, Figma, and how the design workflow is actually shifting in practice.
Claude Design Isn’t a Blank Canvas Tool
Most prototyping tools, whether it’s Lovable, v0, or Replit, drop you into an empty screen and wait. Claude Design starts differently.
You describe what you’re building, and the first thing it does is have you sketch directly on the canvas: crude line drawings, rough enough that the file format it saves is literally .napkin. Then it converts that sketch into wireframes, asking you questions at each step as it narrows in on what you actually need. That process is closer to how design actually works than almost any other tool on the market. Stop, ask questions, think before you execute.
The other thing Claude Design does well is something designers may not love to admit: a lot of good design is math. Grid systems, type scales, margin and padding rules, border radii, alignment logic. These things have to be sequential and consistent, and getting them right manually is tedious even for experienced designers. Claude Design just handles it. Tell it you want an eight-pixel grid and it applies it. Adjust spacing at a system level without touching individual components. The boring half of the craft, the part that was always math pretending to be craft, evaporates.
Building on an Existing Codebase Changes Everything
Claude Design’s real advantage over the vibe-coding tools isn’t what it does from scratch. It’s what it does with something that already exists.
Connect it to a GitHub repository and it can mock up changes to an actual product using that product’s actual component styles. Not something that looks roughly like it. The product. For teams working on an existing application where the work is iterating on what’s already there, not blue-sky concepting, there’s no real comparison.
The handoff is clean too. Claude Design outputs HTML, not a Figma file with layers of abstraction between the design and the actual code. It generates a URL or a zip of files that goes straight to a coding agent. In Jeremy’s testing so far, the implementation accuracy has been 100% when handed to Claude Code. The Figma handoff, even with MCP, doesn’t get there.
The Three Aesthetics Problem
The honest downside, at least right now: when you ask Claude Design for multiple options, you almost always get similar visual concepts and fonts: a polished version of whatever you already have, a dark, terminal-style look, an editorial version with elaborate typography and neutral tones, etc.
All three are clean. All three are better than default Tailwind or a bare ShadCN install. But Claude Design isn’t going to surprise you. It regresses to the mean every time, and it hasn’t shown much ability to push users outside those three defaults.
For an internal dashboard or enterprise workflow tool, that’s probably fine. It just needs to work and look consistent. But for consumer-facing products where visual expression matters, you’ll hit that ceiling. The tool is a month old. That’ll likely get fixed. Worth naming anyway.
Figma Is a Whiteboard Now
Figma hasn’t been replaced. Its role has changed.
For complex work, especially dense information-heavy layouts, there’s still value in slowing down and manually laying things out. The act of doing it forces understanding. You start to see how the data relates to itself, which relationships matter, what deserves hierarchy. Asking an AI for ten layout variations and picking the one you like isn’t the same thing.
And when a coding agent can’t execute something specific after multiple attempts, the fastest fix is to draw it precisely in Figma and point to it. “This. Exactly this.” It works every time.
Figma has gone from being the tool to being a scalpel within a larger suite. For pixel-perfect control on consumer products, for high-fidelity creative work, for the multiplayer collaboration that defined a generation of design culture, it’s still the right instrument. It’s just not the center of gravity anymore.
The Handoff Flipped
For most of design history, the flow ran in one direction. Designers produced Figma files and handed them over. Engineers came to the design. The file was the proof of work.
That’s reversing. Design is now reaching into engineering, not the other way around. And the handoff isn’t going to a front-end engineer anymore. It’s going to an agent.
That changes what a good handoff looks like. Handing an agent the full design context in one shot is expensive in tokens and messy in practice. The same discipline that was supposed to define agile, breaking work into the smallest shippable unit, turns out to matter just as much when the recipient is an agent. The temptation is to hand over everything at once because it’s an AI and it can handle it. In practice, smaller and more focused gets better results.
The enterprise implications of this are real. When agents read tickets and write code, the coordination layer between design and engineering looks different. The roles built around managing that handoff, design ops, front-end translation, the person who owned the design system documentation, are all in motion.
The Floor Is Higher
The more durable change isn’t which tool wins. It’s that the quality floor for software UI just went up.
Naked Tailwind installs, bare bootstrap templates, and default component libraries with no visual design decisions made. Those were fine for utility apps where nobody expected anything better. That baseline doesn’t hold anymore. Anyone can now produce something that looks clean and functions correctly, using Claude Design or any of these tools. The race to acceptable is over.
What that means is that the competitive edge moves up the stack. The designers who figure out how to define systems in natural language, who know how to prompt their way past the three default aesthetics, who can translate taste into a design system that AI actually generates from, those designers will have a real advantage. Not because the craft is going away. Because the craft is moving upstream, and the work that was always most important, understanding the problem, defining the system, making decisions about what matters, finally has room.
Two Kinds of Designers
AI is forcing a split that’s been latent in the profession for years.
There are designers who have always wanted to understand the business case, who are curious about what’s being built and why, who see their job as working on the problem, not just executing the screens. And there are designers who put on headphones and make things look good in Figma.
The second type is in trouble, at least in product design. The ticket-taking, screen-keeping version of the job is getting automated at the execution layer. That’s not a loss for the profession. It’s a correction.
The designers who will do well in this world are the same ones who always would have done well if the tools had let them. The ones who want to get closer to the code, closer to the problem, closer to the shipped thing. Tools are becoming interfaces for agent coordination. The static design file is dying. Design thinking, the actual kind, is becoming a more strategic asset, not a less important one.
About Us
Design Language is a newsletter for all product builders (PMs, Engineers, Founders, etc) who want to improve their design literacy, hone their sense of taste, and improve their craft when building products.
Jeremy Belcher is a 15 year product and design veteran. He has designed UX/UI for products used by tens of millions for brands like Google, Salesforce, Saturday Night Live, DirecTV, BMW, Emirates, Visa and in the past several years has focused on new enterprise workflow products. He runs the product studio Robot Heart, which designs, builds, and validates 0 → 1 B2B workflow tools for teams and founders.
David Issa is a digital strategy and product design leader with over 15 years of experience guiding companies through transformation. He has helped scale products and teams across healthcare, fintech, and enterprise software, translating complex systems into human-centered experiences. David runs a strategic design practice focused on aligning purpose, architecture, and execution—bridging design, AI, and organizational strategy to help teams build with clarity and intent.
