LukeW: the design system gets your feature 90 percent done, your team finishes the last 10

Designers are arguing about whether Figma is dead and whether they all have to learn Claude Code tomorrow. That is the loud version of a real shift happening underneath. Design work is sliding closer to code, and the design system you built is no longer the thing that holds the product together. Let me catch you up.

The deep cut

• Code moves design work, not away from it. Joyce Global's team became design engineers and still starts every project on the canvas.
• The system gets you 90, you finish the last 10. LukeW's agents nail the first pass, then a designer marks up every broken variant.
• A sandbox you own beats a tool you rent. Patrick Morgan built Design Studio so his designs move between Claude, Cursor, and Codex.

Figma is not dying, the handoff is

The Reddit question "will Figma die and will designers vibecode" keeps circling UX Design forums. The honest answer from teams actually doing this: no, and the canvas still matters. Figma itself is pushing deeper into generation with Figma Weave, a node-based workflow for building and reusing imagery and video.

The studio that went furthest still keeps Figma in the loop. Joyce Global rebuilt its team as design engineers, people who design and build in one pass. Even there, CEO Simon Dziukiewicz says "creative ownership starts on the canvas." What is dying is the clean handoff where a designer ships a mockup and a developer guesses the rest.

The 90 percent problem

Agents can apply your design system to production code. They cannot finish the job. Luke Wroblewski says the first pass of a feature, driven by the design system plus agent instructions, gets 90 percent of the way there. Older models managed 50 to 60. The last 10 percent is every variant and edge case the system never accounted for.

His team closes that gap with a fast visual feedback loop: mark up what is broken, make the agent fix each one, repeat. The tempting next step, letting the AI feed all that back into the design system, does not work yet. Give today's models free rein and they over-document instead of simplifying. A designer's judgment about what to keep still carries the system.

The repository nobody rebuilds twice

The sharper move is owning your setup instead of starting from scratch in each tool. Patrick Morgan built Design Studio at Sublime Security because one-off prototypes in Claude and v0 were disconnected and locked him to one provider. "I want my design work to come with me," he said. Canvases are Excalidraw, docs are Markdown, views are React, so the work stays portable.

The same instinct shows up at Figma, where PM Ezra Mechaber turned his personal setup into PM OS, a shared repo of 31 skills now used by 60 to 70 product managers. Both treat AI work as something you build, version, and share, not a chat you throw away.

The dip is where your team quits

Here is the part that bites teams: this takes real work, and the early results are bad. One practitioner describes spending half a day and still not getting what they wanted, feeling like they are wasting tokens and time. That is the moment "AI sucks" sounds most reasonable, and most people step off.

The fix is a mindset, not a prompt. Treat the agent like a new hire who is talented but does not know your standards. You train it with examples of good work, your brief, your principles. Cursor's Lauren Tan calls it a trust ladder: the more you trust the tools you sharpened, the more you can hand over. The enterprise worry on Reddit, 20 teams, no unified system, years of legacy UI, is real. Without a source of truth, vibe-coding across repos makes more inconsistency, not less.

Three questions for your team

• If a PM vibe-codes a solution and hands it straight to devs, who owns design review before it ships?
• Do our design principles and components live somewhere an agent can read them, or only in a Figma file people open by hand?
• When a designer hits the half-day dip on an AI workflow, do we fund the climb or quietly let them drop back to the old process?