Vibe design has killed design too

For two years we’ve lived inside a permanent wake. Every few weeks someone published the definitive obituary for our craft: programming was dead, they said, replaced by a new and vaguely embarrassing thing called vibe coding. You no longer needed to understand the code, just vibe with it. Copy, paste, run, repeat until it compiled. Andrej Karpathy put a name on the practice in February 2025, and the rest of the industry, with its usual enthusiasm for burying entire professions in a single tweet, turned it into a verdict. We took the joke with whatever dignity we had left.

Well. It turns out the obituary had a second page, and this time the byline isn’t ours.

While developers argued over whether we still had a craft or just nostalgia, a quiet army of tools has been chewing on exactly the same problem, one desk over. v0, Figma Make, Google Stitch, Lovable. The same move that left us with no excuse for taking three days on a CRUD now leaves a designer with no excuse for taking three days on an onboarding flow. The logic is identical. Only the victim changed.

We’re not going to pretend to feel much sympathy. But there’s no need to overdo it either: this isn’t payback, it’s just a machine that devours tasks without pausing to check the professional credentials of whoever used to do them.

The first knife was sharpened by one of our own

Worth remembering who started it. v0 was born at Vercel, a developer infrastructure company, in October 2023. A hundred thousand people joined the waitlist in three weeks, nearly all of them engineers. The pitch was: write a prompt, get back a production-ready React component. Nobody sold it as a design tool back then. It was sold as productivity for programmers.

The catch, if you can call it that, is that a UI component isn’t just code. It’s also composition, visual hierarchy, spacing, typography, brand feel. Design, in other words, even when it comes out of a terminal and gets requested by someone who has never opened Figma. Somewhere in 2024, without anyone signing a press release about it, the line between “generating an interface” and “designing an interface” dissolved inside the same prompt. We developers spent months insisting that vibe coding didn’t understand what it was producing. We might have been right, but while we argued about that, it was already producing design.

The company that sold you the canvas now sells you the output

The truly uncomfortable part came later, and it came from inside the house. At Config 2025, its own annual conference, Figma unveiled Figma Make: describe an app, attach an image, or paste a design file, and the system hands back a working prototype, logic included, without anyone touching a frame. It left beta and went available to everyone a couple of months later, that same summer.

Dylan Field, its CEO, got on stage to reassure a room full of designers: in an AI world, he said, design would matter more than ever. He walked off stage and his own company shipped a tool that turns a sentence into a finished product without going through anyone with “designer” on their business card. We’ve lived this ourselves: no “design will be the differentiator” speech survives very long against the demo of the product that makes design unnecessary.

This one sounds familiar. It’s the exact same rhetorical pirouette they pulled on programming: “AI doesn’t replace engineers, it frees them up for higher-level work,” they said, while the supply of available higher-level work turned out to be suspiciously thin.

Design had its own invisible labor too

For years, developers struggled to explain that programming wasn’t just typing. Now it’s designers’ turn to explain that designing wasn’t just moving rectangles around a canvas. Google bought Galileo AI in May 2025 and turned it into Stitch, wired into Gemini: describe a screen, get full variants back, typographic hierarchy and component alignment already resolved in seconds. Lovable positions itself squarely for people who can’t code but want a visual result; it even ships a chatbot with a designer’s personality, simulating, inside the chat window itself, the conversation you used to have with an actual person sitting next to you.

The industry’s response mirrors, beat for beat, the one we gave a year earlier. First denial: this is just for quick prototypes, nobody would ship this to production. Then the graceful resignation: well, at least it frees us from repetitive tasks so we can focus on strategy. We said exactly the same thing about CRUDs and migrations. We’re still writing migrations.

The first job to disappear is always the same one

The labor market hasn’t taken long to confirm the parallel either. Junior designer openings now draw somewhere between five hundred and eight hundred applications, a number that until recently we only saw in junior programming hiring. More than half of design hiring managers say demand for senior profiles has gone up; barely one in four is actively hiring juniors. Basic production work, the kind that used to be how you cut your teeth, now gets solved with a prompt and a quick review.

Developers got a two-year head start on this warning and didn’t pay it enough attention. The irony is that we’re now in a position to hand out the same badly-received advice we got ourselves: specialize, bring judgment, don’t get caught doing only the part the machine already knows how to do. Perfectly correct advice, and completely useless for anyone who needs this month’s paycheck, not next year’s career plan.

Same visual disaster, different name

There’s a part of this whole ordeal that has genuinely amused us developers, and we’ll admit it without shame: AI-generated design has its own version of spaghetti code, and it already has a name for the entire neighborhood, AI slop. Purple-to-blue gradient, one-pixel gray border on every card, Inter as the typeface, three feature columns, a dark mode nobody asked for. A language model isn’t trying to make something look designed; it’s reaching for the statistically most likely option, and the most likely option is always the most-seen one. The result is a website that looks suspiciously like every other website generated that same week.

Recent surveys put roughly half of consumers as able to spot AI-generated content, and a meaningful share say their trust in the brand drops once they notice it. To developers, this sounds exactly like generated code that compiles, passes the tests, and nobody still wants to maintain. It works. Nobody wants it anywhere near production in six months.

The company that rented you the brain now sells you the output too

Here’s a detail that should wipe some of the smile off our own faces, and it’s worth not hiding it from designers while we hand it to them anyway. v0, Figma Make, Stitch, Lovable: none of these tools builds its own intelligence. They all rent a model from the same two or three providers, wrap it in a pleasant interface, and charge for the wrapping. The business was never in the brain. It was in the packaging.

On April 17, 2026, Anthropic decided to stop just renting out the brain. It launched Claude Design, under its Anthropic Labs initiative: it generates designs, prototypes, presentations, and interactive content from a prompt, an image, a document, or the codebase itself. You refine it through inline comments and direct edits, it applies the brand’s design system without anyone configuring it by hand, it exports to Canva, PDF, PPTX, or HTML, and it hands the result straight to Claude Code to become a working product without ever leaving the conversation. A product manager at Datadog put it bluntly: what used to take a week of back-and-forth between design and engineering now happens in a single conversation.

Worth pausing here, because the missing piece isn’t just another tool competing for the same spot. It’s the supplier of all the other tools deciding it no longer needs to share the spot with anyone. Figma, Vercel, Lovable, and the rest have spent months building houses on land that isn’t theirs. Anthropic just announced it wants to live there too.

And if the company that makes the model — the same one that also controls the agent turning it into production code — decides to fold design, prototyping, and implementation into one closed pipeline, what’s left to sell for the middlemen who’ve spent two years thriving on renting that intelligence by the API call? The uncomfortable question isn’t whether Claude Design will replace manual design; we’d already taken that for granted before finishing the previous paragraph. The question is whether it’ll be the last tool that ever needs to exist. Not just the one that kills design by hand, but the one that kills the entire market built on temporarily renting somebody else’s intelligence.

Developers should own this without too much gloating: our own favorite tools — also rented, also dependent on the same half-dozen providers — are exactly as exposed to that same vertical integration, the day someone in San Francisco feels like it.

No need to fake too much sympathy

And here’s where the impulse deserves a pause, because it would be easy, and also cheap, to leave it at payback. What this whole episode really proves isn’t that design was expendable, any more than the previous episode proved programming was. It proves both crafts carried two distinct layers that spent years coexisting under the same job title: a production layer, mechanical and automatable, and a judgment layer, the one that decides what deserves to exist and why. AI has eaten the first layer in both cases, with the same appetite and the same indifference toward whoever was carrying the card.

It took developers a couple of years to admit that a lot of what we called “programming” was, in fact, mechanical production dressed up as a craft. Designers are now getting the same lesson in humility, with the added benefit that we’ve already watched it happen once and could have warned them with more generosity than we were shown ourselves.

AI didn’t kill design, any more than it killed programming before it. It killed the comfortable fiction that making and deciding were the same job. It still stings for developers to admit we learned that first. To designers: welcome to the club. We saved you a seat, but we’re not going to pretend it was still warm.