TL;DR: Claude (by Anthropic) is one of the most useful AI assistants in a real product design workflow. It excels at the language-heavy parts of design: synthesizing research, writing and refining UX copy, critiquing flows, and documenting design systems. Use Claude's most capable models (the Opus family, currently Claude Opus 4.8) for deep reasoning and critique, and a faster model like Claude Sonnet for quick everyday tasks. Below is the exact workflow I use as a designer who also writes code.

What is Claude, and why use it for design?

Claude is an AI assistant made by Anthropic. For designers, its strength is judgment with language and structure — not generating pretty pixels, but helping you think, write, and decide. That makes it a force multiplier for the upstream parts of design where the real leverage is.

1. Synthesize user research

Paste raw interview notes, survey responses, or support tickets and ask Claude to cluster them into themes, surface pain points, and flag contradictions. This compresses days of synthesis into minutes. Prompt it like: “Group these 20 interview notes into themes, rank by frequency, and quote the strongest example for each.”

2. Write and refine UX copy

Claude is excellent at microcopy — button labels, empty states, error messages, onboarding. Give it the context and the user's emotional state and ask for three options at different tones. Then refine: “Make the error message reassuring, not blaming, and under 12 words.”

3. Get a design critique

Describe a flow or paste the steps and ask Claude to poke holes in it: where will users get confused, what's the riskiest assumption, what edge cases are missing. Use a capable model here — Claude Opus 4.8 reasons carefully and will push back rather than just agree.

4. Document your design system

Claude turns scattered decisions into clean documentation: component usage guidelines, do's and don'ts, accessibility notes. Paste your components and ask for consistent, structured docs your whole team can follow.

5. Bridge design and engineering

Because I also write code, I use Claude to reason about feasibility — what a design will cost to build, where the edge cases are, how to explain a design decision to engineers. This is where design, engineering, and business judgment meet.

Tips for better results

• Give Claude context and intent, not just the task — tell it who the user is and what the business needs.
• Ask for options and tradeoffs, not a single answer.
• Use a capable Opus-family model for critique and reasoning; a faster model for quick drafts.
• Treat output as a strong first draft, then apply your own taste.

FAQ

Can Claude design a UI? It's best for the thinking, writing, and critique around design rather than producing final visuals. Pair it with your design tools.

Which Claude model should designers use? An Opus-family model (currently Claude Opus 4.8) for deep critique and reasoning; a faster Sonnet model for quick everyday tasks.

Is Claude better than other AI tools for design? It's particularly strong at language, judgment, and structured thinking — the upstream parts of design where decisions are made.

Carlos Lastres is an Apple Design Award–winning product designer and software engineer in Tokyo who works hands-on with AI tools, including Claude, to design and ship revenue-generating products.