Claude Design (and other stuff "UX Roundup for April 27")

Claude Design ≠ Smart Figma

Claude Design is Anthropic’s new AI-native design environment to generate and iteratively refine UI designs, slide decks, and interactive prototypes by conversing with Claude rather than drawing everything manually. It runs on Anthropic’s latest vision model (Claude Opus 4.7).

Claude Design is a browser-based canvas paired with a chat pane where you describe what you want (e.g., “mobile onboarding flow for a budgeting app for retirees”) and get a structured layout, styling, and content automatically. You then refine that output using natural language, inline comments, or direct edits on the canvas, with Claude updating the full design systemically.

Early feedback emphasizes the benefits of the designs aligning with your established design system, and it’s strongly recommended to upload your complete design system to Claude Design before using it to produce any designs. Claude Design can crawl your codebase and design files to automatically infer a design system if you don’t have an explicit design system already defined.

Ryan Mather, who is a designer at Anthropic, posted his initial advice for using Claude Design. Three points that stood out to me:

• Do spend time upfront to set up your design system in Claude Design and upload the core screens from your existing design.
• Iterate with your engineers live: you can now get live protypes in real time, making for deeper discussions about proposed new features.
• Don’t use chat, but point to the places in the design you want to change. This is much easier than a verbal description of changes.

The overarching insight from Mather is that Claude Design is a different beast than traditional design tools that are based on laying out individual UI screens one at a time. The new tool redefines the job of designing.

The primary artifact shifts from the screen to the system. Traditional canvas tools treat the screen as the unit of work. You open a frame, you drag components onto it, you finish a screen, you start another. Claude Design inverts this: the design system is the primary artifact, and individual screens are ephemeral outputs of that system applied to a brief. This is why Mather’s advice about uploading your design system first isn’t housekeeping; it is the work. If your design system is thin or inconsistent, your outputs will be thin and inconsistent, no matter how cleverly you prompt. If your system is rich and opinionated, Claude has more constraints to push against, and the generated designs feel like they actually belong to your product rather than to the model’s statistical average of “good SaaS UI.”

The cost curve of exploration inverts. In Figma, producing three credible variants of an onboarding flow takes hours, so designers tend to commit to a direction early and refine it. In Claude Design, generating five directions costs about as much as describing them, so the bottleneck shifts from production to evaluation. This sounds like pure upside, but many designers report feeling overwhelmed at first: they haven’t needed to develop a vocabulary for rapidly discriminating between options, because they’ve never had this many options. Taste becomes a throughput constraint rather than an output quality.

Fidelity stops being a ladder. The traditional progression from sketch, wireframe, mockup, prototype, to released product exists because each rung costs more than the one below it, so you do cheap work first to de-risk expensive work later. Claude Design collapses this ladder by making high-fidelity interactive prototypes nearly free. This is liberating, but it’s also the biggest trap in the tool. You skip the “low-fi thinking” stage where you’re forced to wrestle with information architecture and flow before getting seduced by visual polish. The discipline of deliberately working at low fidelity, even when you don’t have to, is an emerging best practice.

Why pointing beats describing. Mather’s advice to point at the canvas rather than chat deserves unpacking. Natural language is excellent at conveying intent (“make this feel more trustworthy,” “reduce the density”) but terrible at conveying location (“the third card in the second row, but only the variant that shows when the user is logged out”). Pointing resolves the referential ambiguity that chat handles poorly. The cleanest workflow treats the canvas as the “where” and the chat as the “what to change.” Mixing them (e.g., typing “make the blue button on the second screen slightly smaller”) is where Claude Design sessions tend to go off the rails.

The critique loop changes shape. In Figma, feedback flows from reviewer to designer, and the designer adds value by interpreting vague feedback into concrete changes. In Claude Design, reviewers can talk to the system directly. This weakens the designer’s role as a feedback-translator and strengthens his or her role as constraint-setter: the person who defined the design system, wrote the brief, and chose the initial direction. Designers who have built their careers on being “the one who can turn ‘make it pop’ into actual pixels” will find that leverage shifting.

Engineers become collaborators, not stakeholders. Mather’s point about iterating with engineers live is another 180° flip in the UX workflow. In traditional workflows, engineers arrive after designs are “done” and push back on feasibility, creating expensive rework. When engineers can propose changes directly in the design environment to test “what if this list virtualized differently” or “what happens to the layout at this breakpoint,” they’re co-designing rather than gatekeeping. The design/engineering boundary gets productively fuzzier.

The failure modes are different, and worth learning to spot. Figma designs fail by being inconsistent, off-brand, or physically impossible to implement. Claude Design outputs fail differently: they tend to be internally consistent but generic, exhibiting a kind of aesthetic mode collapse toward the average of well-designed products. They can be confidently wrong about things that don’t translate to natural language, such as microinteractions, timing, spatial rhythm, the specific way a particular element should feel under the finger. (Though all of these will obviously get better in the next release.) And they can feel over-optimized, as though every decision has been justified, which paradoxically makes them feel soulless. Learning to recognize and correct for these failure modes is the new craft.

The competency stack shifts. Traditional design workflows reward visual craft as a production skill. Claude Design rewards it as a judgment skill: you still need to know what “good” looks like, but you’re using that knowledge to evaluate output rather than to produce it. Alongside this, three competencies become disproportionately valuable: clear articulation of intent and constraints, strong design system literacy (knowing what’s worth codifying and what should stay flexible), and curatorial stamina (the ability to evaluate a lot of options without defaulting to the first acceptable one). None of this makes designers obsolete. It makes the median designer’s job look more like what senior designers and design directors already do: setting direction, defining standards, and exercising judgment over output they didn’t personally produce.

All of these shifts mean that Claude Design moves designers up the abstraction ladder. You’re no longer the person placing rectangles; you’re the person defining what rectangles should exist and why. That’s a bigger change than any feature list conveys, and it’s why teams who treat Claude Design as “Figma, but I type instead of drag” tend to underwhelm themselves with it.

For the sake of variation, I replaced my usual Silicon Valley product team with one based in Tokyo to bring you this comic strip about the new design process:

(Nano Banana 2)

Even though I refer to Claude Design in the above analysis of how systems-capable AI design tool change the design process, I expect that the implications of the forthcoming competing tools from the likes of Google and OpenAI will be much the same. AI is super-competitive, and better tools will likely emerge soon.