After 29 years as a designer, I tested Claude Design. The category just shifted, and most designers haven't noticed yet.
I have been a designer for 29 years. I have shipped work for Adobe, IBM, Danone, and a long list of companies in between. I have lived through Fireworks, Freehand, Sketch, Figma, and every wave of tool consolidation in between.
Today, sitting in front of Claude Design for the first time, I caught myself saying something I have never said about a design tool before.
"This is a better way of working."
Not "this is interesting." Not "this might replace X." A better way of working. Full stop.
The tool I was testing is Claude Design, announced this morning by Anthropic Labs. Powered by Opus 4.7. Research preview. claude.ai/design.
But the tool is not what this article is about. The tool is a proof point. What matters is the category it just defined.
I am calling it vibe design.
What vibe design actually is
The phrase vibe coding, coined by Andrej Karpathy, describes a mode of software development where a human expresses intent in natural language and an AI produces, revises, and ships the code. You stop typing the implementation. You start steering it.
Vibe design is the same shift, one layer up.
It is design produced by expressing intent in natural language, refined through live parameters and direct conversation, and handed off to code without ever producing a static design file. No .fig. No artboards. No developer translating pixels back into semantic markup. The design is never a deliverable on its own. It is always one step in the conversation between intent and shipped product.
Three properties define it:
Natural language as the primary input. You describe what you want, the tool produces a starting version, you refine through conversation.
Live parameters as the primary refinement surface. Instead of nudging pixels, you adjust sliders, toggle variants, and let the tool regenerate. Typography, spacing, color, layout, shape. All live. All reversible. All parametric.
Direct handoff to code, not to developers. The output of vibe design is not a file for a developer to rebuild. It is a structured description of intent that the code layer consumes directly. In Claude Design's case, that means a handoff bundle that Claude Code reads and builds into working software.
If you have used v0 or Lovable, you have done a version of this. But those tools collapse design and code into a single step. Vibe design separates them again, deliberately, so designers can iterate on intent before the code layer takes over.
That is the new thing. That is what Claude Design just made legible.
Why this is different from the AI design tools you've already seen
For the last two years, AI design tools have lived on a spectrum from "AI in your design tool" to "AI that writes your frontend code." I have tested most of them on my YouTube channel. Here is where each one sits.
Figma Make and Figma Agent. AI inside Figma. You still produce a .fig file. The AI accelerates the production of that file. The output is still a deliverable that a developer translates into code. Incremental, not categorical.
Google Stitch. Mobile-first, prompt-to-visual. Beautiful output, narrow scope. A speed tool, not a workflow tool.
v0 by Vercel. Prompt to React component. Collapses design and code. Great for shadcn-heavy projects, less great when you need visual iteration separate from code iteration.
Lovable. Full app generation. Excellent if you want an end-to-end app with auth and database. Less excellent if you want to iterate on pure UI intent.
Magic Path, Framer AI, Canva Magic Studio. Different flavors of the same pattern: AI accelerating existing design surfaces.
Claude Design sits somewhere none of these do. It treats design as a separate phase from code, but it refuses to produce a static file as the deliverable. The output is always live. Always parametric. Always ready to hand off as design intent to a code-generating agent.
This is what makes it feel different in practice. When I tested the calculator kit example, I was not dragging handles or nudging pixels. I was talking. I was dragging sliders. I was commenting on specific elements and asking Claude to revise. When I was happy, I clicked one button and handed the entire design off to Claude Code, which built a working prototype in an empty folder within minutes.
No Figma file was produced at any point.
And I never missed it.
The .fig file was the problem
Here is the uncomfortable thesis.
For the last decade, the .fig file has been the default unit of design work. You produce one. A developer opens it, measures it, translates it into code, and ships it. The design is finished when the file is finished. The implementation is somebody else's problem.
This worked when AI could not read intent. A Figma file was the most efficient way to encode design decisions that a human developer could reconstruct.
That constraint just dissolved.
When an AI model can consume a structured description of design intent and produce working code that matches it, the intermediate file stops being useful. Worse, it becomes a liability. It locks the design into a specific visual snapshot instead of leaving it parametric. It forces a translation step where information is lost. It creates a handoff culture where designers throw files over the wall and hope.
Vibe design kills that handoff culture.
In Claude Design, I pointed the onboarding flow at a real GitHub repository. It read my team's design system directly from the code. Every design it produced after that used the right colors, the right typography, the right components. When I handed the final design to Claude Code, Claude Code built it using those same components, because it was reading the same repo.
The .fig file would have been the wrong artifact at every step in that loop. Nobody needs it. The design intent is the asset. The rendering is disposable.
What this means for designers
Two things, and you need to hear both honestly.
The first thing. If your value as a designer is producing polished Figma files that developers rebuild in code, your value just dropped. Not tomorrow. Not in five years. Today. The AI tools are already better at producing that specific output than most mid-level designers, and they are closing the gap with senior designers fast.
The second thing, which matters more. The designers who understand what to design, why it matters, how to frame the problem, how to guide a parametric system toward a meaningful outcome — those designers just got the largest leverage increase in the history of the craft. One senior designer with Claude Design, a real design system, and Claude Code can ship more product in a week than a five-person team could six months ago.
This is the IC 2.0 thesis I have been writing and making videos about for the last year. AI collapses execution. Judgment and orchestration become the job. Vibe design is the specific form that takes inside design practice.
The designers who thrive will be the ones who treat tools like Claude Design not as threats but as amplifiers of the parts of the job that always mattered: understanding users, framing problems, holding taste, knowing when something is wrong.
The designers who struggle will be the ones who defend the file as sacred.
What this means for Figma
Honest take, because I like Figma and I have used it every working day for years.
Figma is not dying. Figma owns direct manipulation. Figma owns the collaborative file format. Figma owns the plugin ecosystem. None of that disappears in the next 12 months.
But Figma's role is shrinking.
For five years, Figma was the center of gravity in product design. Everything started there, everything ended there, and the rest of the tools orbited it. That ended today. There is now a legitimate workflow where a design is conceived in Claude Design, refined in Claude Design, handed off to Claude Code, and shipped to production without ever touching Figma.
Figma Make was Figma's attempt to catch this wave. It is a good tool, but it lives inside the Figma walled garden. It produces designs that still live as Figma files. It is a response to the last category, not the new one.
If Figma does not ship a vibe-design-native product in the next 12 months, they will be defending market share in a category that is no longer the growth category. I would not bet against them. But I would not assume the default is still the default either.
What this means for everyone else
Vibe design is not only for designers. The three groups who get the largest upside are not designers at all.
Product managers. PMs have been asking for "higher fidelity earlier" for a decade. Vibe design delivers that without requiring a designer on every feature spike. A PM can produce a wireframe, a high-fidelity mockup, or a working prototype in the same afternoon, in the company's design system, and hand it to engineering.
Founders and marketers. The gap between "idea" and "shareable visual" just collapsed. A landing page, a pitch deck, a campaign asset. All producible from intent, all exportable to Canva or PPTX or HTML, all without waiting for creative resource.
Engineers. Engineers who want to prototype a UI without pulling a designer off another project just got a tool that produces design-system-correct output in minutes and hands off directly to their existing code workflow.
Vibe design is a democratizing shift. The skill floor for producing visual work just dropped. The skill ceiling for directing visual work just got higher.
Where this goes next
Three predictions.
Direct manipulation comes back. Right now you cannot grab an element in Claude Design and drag it. Everything goes through chat or sliders. That will change within 6 months. The winning tool combines vibe design's parametric intent layer with Figma's direct control. Whoever ships that first owns the category for the next decade.
Mobile becomes table stakes. Claude Design is web-only today. Design happens on laptops anyway, but the review, commenting, and handoff flow needs mobile. Expect mobile within 12 months.
Multi-tool orchestration becomes the advanced workflow. The designers who win in 2027 will not be "Claude Design designers" or "Figma designers." They will orchestrate across Claude Design, Figma, Stitch, v0, and whatever ships next, using each for the job it is best at. Taste, judgment, and tool orchestration become the differentiator. Fluency in any single tool becomes a commodity.
How to start today
If you have a Claude Pro, Max, Team, or Enterprise subscription, Claude Design is at claude.ai/design. Research preview.
If you want to actually test vibe design rather than just read about it, here is the workflow I recommend. It is the one I used this morning.
- Point Claude Design at a real GitHub repo during onboarding. Use your own project, not a demo.
- Describe a specific page or flow you actually need to build. Not a toy example. Real work.
- Start in wireframe mode. Resist the urge to jump to high fidelity. Sit with the low-fi output and iterate.
- Use the live sliders. They look like toys. They are not. They teach you how parametric the design system can be.
- Convert to high fidelity. Notice how much it already looks like your product.
- Hand off to Claude Code. Paste the command. Watch it build.
That loop, end to end, takes about an hour the first time. Forty minutes the second time. After that, you will start redesigning how you work.
I have been a designer for 29 years. I have never been more certain that the next 10 years of design will look nothing like the last 10.
Vibe design is here.
Figma is not the center of gravity anymore.
The designers who see that early will own the decade.
If you want to see the full test end-to-end, here's the 17-minute walkthrough:
Julian Oczkowski is a designer with 29 years of experience, former contractor for Adobe, IBM, and Danone, and the creator of the AI For Work YouTube channel. He publishes weekly tests of AI tools for designers, product managers, and engineers.
YouTube: https://www.youtube.com/@aiforwork_app
LinkedIn: https://www.linkedin.com/in/julianoczkowski
GitHub: https://github.com/julianoczkowski
Top comments (0)