Using Claude as a Design Collaborator: A Practical Prompt Workflow
"Using AI for design" is one of those phrases that gets thrown around in a way that makes it sound either magical or completely useless. It's neither. Claude doesn't replace anything a designer already does well, but it's oddly good at the parts of design work that are slow and frustrating: articulating tradeoffs, stress-testing copy logic, generating structured critique when you're too close to a layout to see what's wrong.
This post is a practical walkthrough of how to use Claude as a design collaborator, with example prompts and the limits to watch for. If you want a broader framework for deciding when to trust AI output at all, there's one in 10 Patterns for Evaluating AI Outputs — this post stays focused on the design-specific workflow.
01The Problem With Most "AI for Design" Advice
Most articles on this topic tell you to ask Claude to "generate UI copy" or "suggest color palettes." That's fine, but it treats Claude like a vending machine — input a category, receive an output, move on. Claude works much better as a thinking partner than a generator. The difference is subtle but important.
A generator produces answers. A thinking partner helps you ask better questions, poke holes in your assumptions, and surface the thing you weren't quite able to articulate. Framing the collaboration that way changes the quality of what you get back.
02Step 1: Describe Your Interface in Structured Terms
Claude can't see your Figma file. Even where Claude's vision capability is available, describing the interface in words is useful in itself, because it forces you to think clearly about what you're actually building.
Here's a template for starting a design review session:
Screen: [name of the screen] User goal: [what the user is trying to accomplish] Current structure: [list the main elements in order — headline, subheadline, form fields, CTAs, etc.] Current copy: [paste the actual copy, not a description of it] My specific question: [one clear question — not "what do you think?"]
Say you're working on a subscription upgrade prompt that appears mid-session in a project management tool. A filled-in version might look like this:
Screen: Upgrade prompt modal (appears when free user tries to export a report) User goal: Export their report. They didn't come here to upgrade — they were interrupted. Current structure: Modal title, 2-sentence value prop, feature list (3 bullets), two buttons (Upgrade Now / Maybe Later) Current copy: Title: "Unlock Full Export" Body: "Upgrade to Pro to export reports in PDF and Excel. Get access to advanced filters, custom branding, and priority support." Bullets: PDF + Excel export / Custom branding / Priority support Primary CTA: "Upgrade Now" Secondary CTA: "Maybe Later" My question: Does this copy address the right thing at the right moment, or is it trying to sell too much to someone who just wanted to export a file?
A prompt like this gives Claude enough to reason with. The useful observations here are that the body copy is doing two different jobs — justifying the export feature specifically, and then pivoting to list unrelated upsells like "priority support." For a user who was interrupted mid-task, that pivot creates friction. And "Maybe Later" is a passive dismissal that doesn't acknowledge the user's actual intent (they still want to export — they just might not want to upgrade right now).
Those are often observations you're already circling around but haven't quite landed on. Having them stated plainly helps you move faster.
03Step 2: Use Claude to Stress-Test Your Hierarchy Logic
A useful approach is having Claude argue against a layout decision. Not "improve this layout" — that's too open. Ask it to find the weakest part of the information hierarchy and explain why.
Picture a dashboard landing page. You give Claude the screen description and ask: "If a first-time user landed here with zero context, what's the first thing they'd get confused by, and what in the current hierarchy is causing that?"
The answer may not be the one you expect. You might assume the empty state is the problem (it often is — see empty state design). But Claude might point somewhere else, such as the navigation: a "Reports" tab visible before the user has created any data signals a level of completeness the product hasn't earned yet. That's the kind of insight worth acting on.
04Step 3: Generate Variations, Then Judge Them Yourself
Claude is good at generating multiple versions of things — headlines, CTA labels, error messages, onboarding step copy — but don't ask for "the best" version. That framing just gets you one answer that Claude has pre-decided is best, which removes your judgment from the loop.
Instead, ask for variations with intentional differences in tone or emphasis:
Give me 5 versions of this CTA label. Each version should prioritise a different thing: 1. Speed / getting results quickly 2. Safety / low-risk commitment 3. Social proof / others are doing this 4. Curiosity / what will they discover 5. Direct / no framing at all, just the action Context: This button appears on a free trial signup page for a B2B invoicing tool. Users are small business owners, slightly skeptical of SaaS tools, probably burned before.
This gives you five coherent options you can actually evaluate, rather than one "optimised" label that might not fit the brand voice or the user's actual headspace. The judgment stays yours. Claude just saves you the time of staring at a blank doc.
05Step 4: Run a Structured Accessibility Logic Check
Don't use Claude to replace an actual WCAG audit — that requires tooling and real browser testing. But it's useful for catching logical gaps in your accessibility reasoning before you get to that stage.
Describe a component — say, a custom dropdown with keyboard navigation — and ask Claude to list every accessibility consideration you should be accounting for: ARIA roles, keyboard interaction patterns, focus management, screen reader announcement order. Not to implement them, but to give you a checklist you can audit against.
Say you've built a multi-select filter component where the selected state is communicated purely through background colour change. No aria-selected, no visible text change, no icon. A checklist like this should include "ensure selected state is communicated through means other than colour alone" — which is WCAG 1.4.1 — and the fix is quick once you know where to look.
06Step 5: Use It for Design Rationale Documentation
This is probably the least glamorous use case, but it saves real time on client projects. After making a design decision, describe what you chose and why, and ask Claude to help write it up as a clear design rationale — the kind that goes in a handoff doc or a client presentation slide.
Example input:
I moved the primary action button from the top-right of the card to the bottom of the card, below all the content. Reason: user testing showed people were clicking it before reading the card content, then being surprised by what happened next. Help me write this as a one-paragraph design rationale for a client handoff doc. Audience: non-technical stakeholders.
Treat the output as a first draft: edit the tone, add specifics, and move on.
07Where Claude Earns Its Place — and Where It Doesn't
It's worth being honest about the limits.
Claude does not know your users. It knows a reasonable approximation of "general users" based on its training data, which skews toward Western, English-speaking, tech-comfortable demographics. If you're designing for, say, someone running a warung who needs to invoice on a mobile browser on a slow connection, apply heavy skepticism to Claude's assumptions about user behaviour. It can suggest patterns that make sense in a Silicon Valley SaaS context and fall completely flat for that user.
Claude also doesn't know your technical constraints. It'll suggest things that are elegant in theory and impossible on, for example, shared hosting with no WebSocket support. That's fine — you just filter for it. But you have to know to filter, which means you have to bring your own context to the conversation, not expect Claude to infer it.
And occasionally Claude is just wrong. It'll state an accessibility rule with confidence that's slightly off, or recommend a copy pattern that clashes with the brand. This is why the output always goes through your judgment before it goes anywhere near a client. The evaluation layer is non-negotiable.
08A Quick Reference: Prompt Patterns That Work
- Hierarchy critique: "If a first-time user landed here with zero context, what would confuse them first?"
- Copy variation: "Give me 5 versions of this label, each prioritising a different goal: [list goals]."
- Accessibility checklist: "List every accessibility consideration I should account for in this component: [describe component]."
- Rationale writing: "I made this design decision for this reason — write it as a one-paragraph rationale for non-technical stakeholders."
- Stress test: "Argue against this design decision. What's the strongest case for doing it differently?"
- Copy audit: "Is this copy doing one job or two? If two, which job should it prioritise at this moment in the user journey?"
09The Mindset Shift That Makes It Work
The biggest change isn't in how you prompt Claude — it's in what you expect from the collaboration. Stop expecting it to give you answers and start expecting it to help you think faster. That's a different relationship with the tool, and a more honest one.
Claude is sharp at pattern recognition, articulation, and structured critique. It's weak at contextual judgment, cultural nuance, and knowing what you haven't told it. Once you accept that split, you stop being frustrated when it misses something obvious (to you) and start using it for the specific tasks where it consistently adds value.
For UI/UX work, that turns out to be a lot of tasks. Not all of them — but enough to make it worth learning.
10Frequently asked questions
Can Claude actually help with UI/UX design decisions, or is it only useful for writing and code?
Claude is genuinely useful for design reasoning tasks — critique, user story framing, copy hierarchy, and accessibility logic — even though it can't see your screens without a vision-capable model. The key is learning to describe your interface in structured, specific terms so Claude has enough context to reason about it properly.
What kinds of design prompts give the best results from Claude?
Prompts that include the user type, the goal of the screen, the current copy or structure, and a specific question you want answered. Vague prompts like "make this better" return vague answers. Specific prompts like "this modal has three actions — which one should be the primary CTA and why?" get you real reasoning.
Is Claude reliable enough to use in a client-facing design workflow?
As a thinking partner and first-pass critic, yes. As a final decision-maker, no. Claude's suggestions still need to be filtered through your knowledge of the actual users, technical constraints, and brand context — things it simply doesn't have access to unless you supply them.
Denny Pratama
Product designer in Indonesia. Since 2018 I’ve designed SaaS products, dashboards and marketing sites, and now I build my own designs too.