Claude Just Released a Design Tool. Put the Figma Obituaries Away.

Claude Just Released a Design Tool. Put the Figma Obituaries Away.

🎧 This post has a companion podcast episode. Hit play and read along — it's about 3 minutes. Listen out for the trigger word and type it into the agent in the bottom right corner of the screen to claim your free gift.

audio-thumbnail
Podcast: Claude Just Released a Design Tool. Put the Figma Obituaries Away.
0:00
/0

I wanted to share this with you because the internet has been on fire for the last 48 hours. Anthropic dropped a design feature inside Claude, and within a heartbeat, half of my feed was writing Figma's eulogy.

It happens every time something new comes out. A tool drops, someone calls it a "killer," and a thousand people who have never actually opened Figma a day in their life start nodding along as if the world just changed.

Here is the reality: Claude's design feature is genuinely interesting. It can generate UI mockups, layout suggestions, and visual concepts from a single prompt. That’s real. That’s useful. It is a massive leap in how we communicate intent. But it is not replacing Figma, and more importantly, that is not the conversation worth having.

Here is the actual conversation we should be having.

The "One-Shot" Trap: Why AI Design Often Feels Hollow

Most people using AI to generate designs right now are producing work that looks exactly like what it is—a one-shot output from a prompt with no real thought behind it.

You’ve seen it. It has a specific kind of "wrongness" to it. Everything is technically present—buttons, inputs, labels—but nothing feels considered. There is no hierarchy. No intention. No understanding of why an element is positioned exactly where it is.

Anyone who has spent real time in the trenches of design can spot it immediately. The work feels shallow because the process was shallow.

That isn't an AI problem. That's a knowledge problem.

When you don't understand type hierarchy, spacing, contrast, or visual weight, you can't actually direct the tool. You can't look at the output and know what's off. You can't iterate toward something better because you have no reference point for what "better" actually looks like. You are fully dependent on the first thing it gives you, and that dependency shows in every pixel of the work.

Claude's design tool doesn't change this fundamental reality. It just makes it faster to generate something that looks plausible at a glance and falls apart under any real scrutiny.

The Map vs. The Terrain: How to Actually Use Claude for Design

But here is where it gets incredibly useful if you change your perspective.

AI-generated design is a map. Figma is the terrain.

You need to walk the terrain to understand the world, but the map can show you where the mountains are. The designers who are going to win with these tools are not the ones generating the most outputs. They are the ones using the outputs to accelerate their understanding of principles they are actively building.

Every generated mockup is a free lesson in layout—if you treat it like one.

Use the output as a starting point and then go learn why it made the decisions it made. Why did it put that element there? Why is that text that size? Why does that layout breathe the way it does?

Walking the Terrain: From Prompt to Principle

The best way to use this is to take the generated design into Figma and try to rebuild it manually.

You will immediately hit moments where you don't know how to execute something, or you'll realize the AI took a shortcut that doesn't actually work in production. Those moments are the actual education. That friction is where the knowledge sticks.

Nobody trusts one-shot AI design work right now, and they shouldn't. Clients and users can feel when no thought went into something. The soul is missing, and that absence is visible even to people who couldn't articulate why it feels wrong.

The work that holds up is the work where a human understood enough to push the tool in a specific direction and then knew enough to recognize when it got there.

That takes learning the fundamentals. Claude’s design tool will not do that for you. But it will show you exactly what you don't know yet—if you pay attention to it.

That is more valuable than anything a "Figma killer" could ever offer.

If you’re looking for a way to put these systems into practice without the usual trial and error, you might find my Skool community, CMD & Conquer, helpful. We focus on the actual mechanics of creation, tracking, and nurturing, ensuring your systems are built on reality, not vibes.

Just start building.