Claude Design through the eyes of a UX designer.

UX Design
MH
Marieke Hepkema
UX designer
1 June 2026 · 8 min read
Claude Design through the eyes of a UX designer

Claude Design has caused quite a stir recently. What can you do with the tool, and what value does it add to a UX designer's workflow?

Claude Design

Claude Design from Anthropic Labs has caused quite a stir recently. It is an AI-powered design tool that lets you generate prototypes, slide decks and one-pagers for websites with just a few simple prompts, without any design experience. The platform is part of a trend of agentic design products, such as Google Stitch and Lovable. Anthropic says the platform has been released as a research preview, but the tool already offers plenty of possibilities and is widely used and discussed. Even so, you can expect the tool to be developed further as time goes on. In this blog post, I take a look at the world of Claude Design and other agentic design tools from a UX designer's perspective.

Beautiful designs, based on your design system

With Claude Design, you can quickly generate designs that look good, whether or not you have design experience. When generating designs, you can add your own design system so that Claude takes it into account (and the output becomes less generic). You can do this via GitHub, your codebase, a Figma file, and/or by uploading fonts, logos and assets. Importing design system elements is sometimes slightly cleaner via GitHub than via a .fig file, but it's nice that the option is offered. For the smoothest handover to Claude Design, you need to document your design system well, which of course takes some extra time and effort. The handover of the design system doesn't always go well either: sometimes basic components such as button colours and focus states aren't implemented correctly. Once the design system has been created, you can approve or adjust the elements individually, but every adjustment can use up valuable credits.

Part of a screenshot of the Claude Design interface, with the header 'set up your design system' at the top. It shows the different kinds of input you can give Claude to generate a design system, such as code on GitHub, a Figma file, or logos, fonts and assets.

At first glance, the design system it builds is more extensive than the fairly simple 'design system' Google Stitch (beta) provides when you start a project (although Stitch generates more rules than are immediately visible on the style sheet). It is a shame, though, that you can't zoom in on the typography output, which means you can't quite inspect the design system properly. That does little justice to the precision with which a design system is built.

The design systems generated by Claude Design and Google Stitch. Claude Design produces a relatively extensive list of components, whereas Google Stitch mainly shows a visual foundation with colours, fonts and buttons, and a limited variety of components.

Claude Design on the left, Google Stitch on the right

A good addition is that Claude asks you a number of questions at the start of a project to understand it properly. These cover tone of voice, colour scheme and scope (should the product have a paywall?). Questions like these come up in every development project, and they are a smart addition to the workflow in Claude Design. And every prompt counts, because Claude's credits can get expensive.

Opus 4.7: a powerful model with expensive brain cells

Claude is known for its strong AI models, and Claude Design uses them too. The Claude Opus 4.7 model is powerful, but it has a downside: with Opus 4.7 you burn through your weekly credits very quickly. After importing an extensive design system, for example, you may already have used up a considerable part of your weekly allowance. And a design is rarely perfect first time, often requiring several rounds of iteration. This credit problem can be partly solved by using Opus 4.7 only for the first designs, and then iterating with a less 'expensive' model such as Sonnet 4.6. It was also recommended earlier to send the generated prototype to Claude Code as soon as possible to save credits, but now that Claude Design has recently started sharing credits with Claude Code and Claude AI, this workaround seems less viable, although Claude Code is somewhat more economical to use. The handoff to Claude Code is very well set up, though: components, design tokens, copy and interaction notes are all passed along, and all in all this workflow considerably speeds up the handoff from design to development.

Claude Design from a UX designer's perspective

Claude Design is an impressive tool that could streamline certain tasks. You never have to stare at a blank screen waiting for inspiration again; a prompt is enough to generate ideas. Anthropic itself says the product also works well for generating variations to build on. I'm still somewhat cynical about this, because it can indeed do that, but it also uses up a lot of credits, so the question remains how often you would find it worthwhile to tackle this with Claude Design.

The designs that come out of Claude are often impressive and easily include animations. In my view, this tool is good for developers without design expertise and other people who want to generate websites but have little design experience. Or for when you want to generate a slide deck or a video with motion graphics without spending too much time or money on it. For now, designing a complex app with several rounds of iteration still seems better done by at least sketching and mapping it out in Figma first (where AI can help if needed), not least because you burn through your Claude credits so quickly. It's important to remember that UX design is much more than designing beautiful interfaces: a 'pretty' design with cool animations can fail just as badly on usability.

Ultimately, designers want to stay in control of the design. Everything must be achievable pixel perfect, and as a designer you don't want to be busy with just prompting and approving. Figma seems to have understood this.

The Figma logo on a dark background

Figma: the tool made for designers

Figma has recently announced a few very promising updates. With the Figma design agent you can use AI directly in your design canvas - no more importing and exporting, but new tools in a design application where you have far more control over the overall design. You can generate variations and have colleagues' comments applied automatically - following a design system of your choice, of course. You can also have the design agent write your design system documentation, which can save a lot of work too. In addition, Figma Design edit functionality is being added to Figma Make - which further blurs the line between design and development in this tool as well. My suspicion is that most designers will want to use this product much more, because switching between quickly generating screens and editing pixel by pixel offers more freedom in practice and better matches how many digital products are designed. It is also nicest to build designs in a central place where your whole team can work on them at the same time. It remains to be seen, though, how the credit allowance for the design agent will work out, and how quickly you burn through it. It does make me hopeful that Figma is thinking realistically about how AI can add the most value to designers' workflow.

Conclusion

Agentic design tools like Claude Design are promising and help streamline certain tasks and speed up the design-to-development handoff, but they also have shortcomings. Sometimes you burn through your credits within an hour and have to wait before you can carry on - which, ironically, feels like a slowdown. There are various use cases where agentic design tools come in handy, for example generating lots of variations in the early phase of a project. With Claude you can map out several design directions in no time, to build on further. 

For designers, Claude Design is good for:

  • Quickly making prototypes, exploratory designs and early validation

  • Generating visuals when you have designer's block

  • Generating slide decks

  • Adding animations quickly

But:

  • AI credits are expensive and may become even more so

  • For complex apps, Claude Design may not be sufficient as a starting point, especially if no designer is involved. For more standard websites, it is a handy tool.

For now, Claude Design is mainly good for generating websites (with cool animations to match) and for workflows where a few first sketches with a number of variations need to be produced quickly. The tool is also handy for developers and people without design expertise, or for people who don't mind how closely the output matches an initial design (or in situations where there is simply enough budget to keep buying credits). The direction of travel is clear, in any case: development and design are growing ever closer together. Claude seems to be taking a step towards design from development, and Figma a step towards development from design. I'm very curious what future versions of the already impressive Claude Design will look like, but personally I'm mostly looking forward to the new functionality Figma has announced (and I suspect many designers share that sentiment). Exciting stuff! :)

Tips for Claude Design

  • When generating beautiful designs, don't lose sight of accessibility and responsiveness: make sure colour contrasts are WCAG-compliant, add alt text to images and check how the design looks at other screen sizes.

  • For your Claude workflow, take a look at Claude skills, for example these Claude Skills for accessibility

  • Don't lose sight of the product's usability either; beautiful doesn't always mean good - the user experience must stay front and centre.

  • Validation remains important: be critical and check the generated designs.

  • Use edit mode for small tweaks, so you don't have to spend a prompt (and the credit that comes with it) every time. Another option is to carry on working in Claude Code after the initial draft.

Edit content