The 30 Best AI Prompts for Designers (UX, UI, and Brand)

If you're a designer using AI tools in your workflow, you've probably run into the same wall I kept hitting: great prompts get lost. You write something that actually works — a critique prompt that finally gives you useful feedback instead of generic praise, or a user research synthesis prompt that saves you two hours — and then you can never find it again.

This post is a collection of 30 prompts that work. I've written them for designers who work across UX research, UI design, brand and visual identity, and client communication. These aren't filler prompts you'll use once. They're prompts worth saving, iterating on, and building into your actual workflow.

---

UX Research & Discovery

1. Synthesize user interview notes into themes

Here are my raw notes from [X] user interviews about [product/feature].
Identify the top 5 recurring themes, quote specific users where relevant,
and flag any outlier responses that don't fit the main patterns.
Format as: Theme → Evidence → Implication.

Notes: {{clipboard}}

You'll get structured themes instead of a pile of observations. The "outlier" flag is particularly useful — AI tends to smooth over edge cases, and this prompt forces it to surface them.

2. Write a research discussion guide

I'm running usability tests on [feature/product].
The research goal is to understand [specific question].
Write a 45-minute discussion guide with:
- 5-minute intro + permission to record
- 3-4 warm-up questions
- Core tasks for the participant to attempt
- Follow-up probing questions for each task
- 5-minute debrief

Participant profile: [role, experience level, context]

Faster than building a guide from scratch, and the structure usually holds up in practice.

3. Turn survey data into an executive summary

Here are the results from a [N]-participant survey about [topic].
Write a 300-word executive summary for a non-technical audience.
Lead with the single most important finding.
Use plain language. Include 2-3 direct quotes.

Data: {{clipboard}}

Works well for stakeholder presentations where the full data deck would be ignored.

4. Generate screener questions for recruiting

I need to recruit participants for usability testing of [product type].
Target profile: [description].
Write 8 screener questions that will identify:
- Relevant experience level
- Usage of comparable tools
- Time availability
- Any disqualifying factors
Include answer options and the criteria for passing each question.

5. Identify gaps in a user journey map

Here is a user journey map for [user goal] across [product/service].
Analyze it and identify:
- Steps where the user has no feedback about what's happening
- Moments where motivation is likely to drop
- Places where the user's mental model probably conflicts with the system's model
- Any steps that could be eliminated

Journey map: {{clipboard}}

This is more useful than asking for "pain points" — it forces the AI to look at specific categories of friction.

---

UI Design & Interface Copy

6. Write microcopy for an error state

I need error message copy for this scenario: [describe what went wrong].
The user's context: [what they were trying to do].
The product's voice: [e.g., "professional but approachable", "technical audience"].

Write 3 versions:
1. Minimal (under 10 words)
2. Helpful (tells user what to do next)
3. Friendly (warmer tone, still clear)

For each version, also write the button label(s).

Error messages are the most under-designed part of most products. This prompt forces you to consider all three formats.

7. Generate empty state copy

Write empty state copy for [specific screen/feature] in [product].
The user arrives here when [situation — first time, no results, cleared data, etc.].
Product voice: [description].

Include:
- Headline (under 8 words)
- Supporting text (1-2 sentences max)
- CTA button label

Write 4 variants — test them against each other.

8. Write onboarding tooltip copy

I'm designing onboarding tooltips for [feature name].
Users see these during their first session after [specific trigger].
Product voice: [description].

Write tooltip copy for these 5 steps: [list steps]
Each tooltip should:
- Be under 20 words
- Focus on what the user gains, not what the feature does
- Include an action if applicable

9. Audit a navigation structure for clarity

Here's the navigation structure for [product].
Review it for:
- Label ambiguity (items that could mean multiple things)
- Missing parent categories
- Items that are likely to be searched for but are hard to find
- Any redundancies

Current nav: {{clipboard}}

10. Write placeholder text that actually helps

Write placeholder text for these form fields in [product type]:
[list of field names]

Requirements:
- Each placeholder should show an example value, not a label
- Keep it realistic (use plausible fake data, not "John Doe")
- Match the register of [product voice]

---

Brand & Visual Identity

11. Extract brand personality from a mood board description

I've been given a mood board with the following visual references: [describe images, colors, typography, examples].
Based on this, write:
- 5 brand personality adjectives
- 3 things this brand would never say or do
- A sample tagline that matches this aesthetic direction
- Suggested tone of voice in 2 sentences

Useful for the early stages of a brand project when you need to articulate direction before anything is designed.

12. Write a brand voice guide section

Write the "Tone of Voice" section of a brand guide for [company/product].
Brand context: [brief description — industry, audience, mission]
Brand personality: [3-5 adjectives]

Include:
- A description of the brand voice in 2-3 sentences
- 4-6 "we sound like / we don't sound like" examples
- One example of a real sentence written in-voice vs. out-of-voice
- How the voice shifts in different contexts (e.g., error messages vs. marketing copy)

13. Generate naming candidates for a feature

I'm naming a new feature in [product].
What it does: [functional description in 1-2 sentences].
Brand voice: [adjectives].
The name should be: [requirements — e.g., single word, verb-led, no tech jargon, international-friendly].
Existing feature names for consistency reference: [list]

Give me 15 name candidates with a one-line rationale for each.

14. Write a positioning statement

Write a brand positioning statement for [product] using this structure:
For [target audience] who [has this problem/need], [product name] is a [category] that [key benefit]. Unlike [competitor/alternative], [product] [key differentiator].

Product details:
- Target audience: [description]
- Problem: [description]
- Key benefit: [what you do]
- Category: [how you want to be categorized]
- Differentiator: [why you're different]

Write 3 variations — one that emphasizes the problem, one the benefit, one the differentiator.

15. Audit a website for voice consistency

Here is copy from [website/product].
Audit it for voice consistency against this voice guide: [paste or describe guidelines].
Flag:
- Lines that feel off-brand
- Inconsistencies in register or formality between sections
- Missed opportunities to express the brand personality more strongly
Rate overall consistency 1-10 and explain the rating.

Copy to review: {{clipboard}}

---

Design Critique & Feedback

16. Give structured feedback on a design brief

Here is a design brief for [project].
Give me structured feedback covering:
1. Clarity — Is the problem clearly defined? Any ambiguity?
2. Scope — Does the scope seem appropriate for the timeline?
3. Constraints — Are design constraints specific enough to be useful?
4. Success metrics — How will success be measured?
5. Missing information — What's not here that should be?

Brief: {{clipboard}}

17. Critique a UI layout

I'll describe a UI layout and I need a critique. Don't just list positives — I want honest feedback about what could fail in use.

Screen: [describe the screen, its purpose, and its key elements]
User goal: [what the user is trying to accomplish]
Context: [desktop / mobile, first time or returning user]

Critique the layout for: visual hierarchy, cognitive load, accessibility concerns, and any interaction patterns that might confuse users.

18. Write a design rationale

I need to write a design rationale for [design decision].
Decision made: [what you designed]
Options considered: [alternatives]
The reasoning for this choice: [your actual rationale, even if rough]

Turn this into a 150-word design rationale that I can include in documentation or present to stakeholders. Use clear, confident language without over-hedging.

19. Generate questions for a design critique session

I'm running a design critique for [design/project].
Write 10 critique prompts that will generate useful feedback — not just "looks nice" responses.
The critique audience: [designers / stakeholders / mixed].
The design stage: [concept / in-progress / near-final].
Focus areas: [e.g., usability, visual hierarchy, accessibility, copy].

20. Identify edge cases in a proposed design

Here's a design for [feature/flow].
Think through every edge case that could break or degrade this design:
- What happens when the user has no data?
- What happens when there's too much data?
- What happens on a small screen?
- What happens when the user's connection is slow or fails?
- What happens if the user is on the 50th use vs. the first?
- What happens if they make a mistake and want to undo?

Design description: {{clipboard}}

---

Client Communication

21. Write a project proposal introduction

Write the introduction section of a design project proposal for [project type].
Client context: [industry, company size, what they're building].
Project scope summary: [brief description].

The intro should:
- Demonstrate that I understand their problem (not just list our services)
- Be 150-200 words
- Use a professional but direct tone
- Not start with "We are pleased to..."

22. Write a feedback request email

Write an email to [client role] requesting feedback on [deliverable].
We sent the deliverable [X] days ago.
The key decisions they need to make: [list 2-3 specific questions].
Next deadline: [date].

Requirements:
- Short (under 150 words)
- Make it easy to respond — specific questions, not "let us know your thoughts"
- Polite but not apologetic about following up

23. Respond to a difficult client comment

A client left this comment on a design deliverable: [paste comment].
The comment is [vague / off-brief / contradicts earlier feedback / stylistically personal / technically incorrect].
I want to respond professionally, address their concern, and steer the feedback toward actionable direction.

Write a response that:
- Acknowledges their input without being defensive
- Asks the clarifying question that will make this feedback usable
- Is under 100 words

24. Write a design presentation script

I'm presenting [deliverable type] to [audience] on [date].
The presentation covers: [list main sections].
Time available: [X minutes].

Write a presenter script with:
- An opening that frames the problem we were solving (not "here's what we made")
- A narrative thread that connects each section
- 1-2 suggested pauses for questions
- A closing that invites specific feedback

25. Write a project retrospective summary

Write a project retrospective summary for [project name].
Project type: [description].
Duration: [timeline].
What went well: [your notes]
What was difficult: [your notes]
What we'd do differently: [your notes]

Turn this into a 400-word retrospective that I can share with the team and client. Be honest about the challenges — this isn't a highlight reel.

---

Accessibility & Inclusive Design

26. Write an accessibility audit checklist for a specific screen

Write an accessibility audit checklist for [screen type] in a [product type].
The checklist should cover:
- Color contrast requirements
- Touch/click target size
- Keyboard navigation
- Screen reader considerations (ARIA labels, headings structure)
- Error messaging
- Animation / motion sensitivity
- Any specific considerations for [screen]

Format as a checklist I can use in Figma annotations.

27. Write alt text for UI screenshots

Write alt text for these UI screenshots that will be used in [documentation / a marketing page / an accessibility audit].
Describe each image for someone who cannot see it — focus on what information the image conveys, not just what's in it.

Images: [describe each screenshot briefly]

28. Review copy for inclusive language

Review this copy for inclusive language issues — not just obvious slurs, but also assumptions about ability, role, family structure, and technical literacy.
For each issue, explain why it's a problem and suggest a replacement.

Copy: {{clipboard}}

---

Workflow & Productivity

29. Convert rough notes into a project brief

Here are rough notes from a kick-off meeting for [project].
Turn them into a structured project brief with these sections:
- Project overview (2-3 sentences)
- Problem statement
- Goals (specific, measurable where possible)
- Non-goals (what we're explicitly not doing)
- Success metrics
- Constraints (time, technical, budget, brand)
- Open questions

Notes: {{clipboard}}

30. Write a case study for your portfolio

Help me write a case study for my design portfolio about [project name].
Project type: [description].
My role: [specific contributions].
The challenge: [problem you were solving].
Key design decisions: [2-3 decisions that defined the project].
Outcome: [results, if available].

Write a 500-word case study in first person. Focus on the decisions and reasoning, not just the deliverables. Be honest about constraints and compromises — that's what makes portfolios interesting.

---

How to Actually Use These Prompts

The problem with most prompt lists is the same one I had before building a prompt manager: you read them, think "these are useful," and then never find them again when you need them.

What's worked for me is keeping prompts in a dedicated tool — something where I can hit Cmd+Shift+P, type "critique" or "brief" or "alt text", and have the right template pasted into my AI tool in under two seconds. That speed matters. If retrieval takes 30 seconds, you'll stop using half these prompts.

The other thing worth doing: treat these as starting points. The prompts above are written to work out of the box, but they'll work better when you add your specific product context, voice guidelines, and real examples. A prompt that knows your brand's name and tone is twice as useful as a generic one.

If you're a designer who uses AI tools heavily, Promptzy stores prompts as plain Markdown files (no lock-in) and lets you fire any of them from anywhere on Mac. Free to try.