I've been a designer for years, and I'll be honest — I was skeptical of AI in my workflow. Then I spent a weekend actually testing prompts instead of dismissing them, and a few of them stopped me cold. Not because they replaced design thinking, but because they accelerated the parts of the job I found most frustrating: extracting clarity from vague clients, writing copy that doesn't embarrass the design, and defending decisions in presentations.
Here are the 8 prompts I kept. All battle-tested.
1. Turn Vague Client Requests Into Clear Design Briefs
Clients say things like "make it pop" or "we want something professional but also fun." This prompt converts that soup into an actionable brief.
You are an experienced creative director. I'm going to share what my client told me about their project. Your job is to translate their words into a clear design brief with: project goals, target audience, tone/voice, visual direction (3 adjectives), things to avoid, and 3 questions I should ask to fill gaps.
Client said: [paste their words here]
Why it works: Forces structure where there isn't any. The "3 questions" output alone saves at least one round of revision by surfacing gaps before you start.
2. Get Specific UX Copy Feedback (Not Vague Reactions)
Generic feedback like "this sounds cold" is useless. This prompt gets you actionable critique.
You are a senior UX writer reviewing interface copy. For each piece of copy I share, tell me: (1) what emotional response it creates in the user, (2) specifically what's wrong with it if anything, and (3) a rewritten version with an explanation of what you changed and why.
Copy to review: [paste your copy]
Why it works: Breaking the critique into three parts forces specificity. You stop getting "I don't like this" and start getting "the passive voice here creates distance."
3. Generate User Personas That Go Beyond Demographics
"35-year-old marketing manager in Chicago" isn't a persona — it's a spreadsheet row. This prompt builds someone real.
Create a detailed user persona for a [product type] targeting [demographic]. Go beyond demographics. Include: daily frustrations, what they Google when stressed, the last app they paid for and why, what they're trying to prove to themselves or others, their relationship with technology, and a direct quote they might say when they first encounter our product.
Why it works: The "what they Google when stressed" and "what they're trying to prove" fields force psychological depth. You'll find yourself designing for the person, not the age bracket.
4. Write Micro-Copy for Edge Cases
Error messages, empty states, loading text, CTAs — these are where UX quietly wins or loses. Most designers leave them as placeholders until it's too late.
Write micro-copy for the following UI states for a [describe your product]. For each, give me 3 options: one functional, one warm/human, one that adds a touch of personality. States: empty state (no results), error state (server error), loading state, success confirmation, and a CTA for [primary action].
Why it works: The three-option format prevents you from shipping the first idea. The "personality" option often reveals something about your product's voice you hadn't defined yet.
5. Get a Senior Designer's Critique of Your Work
This is the most uncomfortable prompt to use, and the most valuable.
You are a senior UX designer with 15 years of experience, known for honest, direct feedback. I'm going to describe a design decision I made. Tell me: what are the risks I haven't considered, what would make a skeptical stakeholder push back on this, what's the strongest argument against my approach, and what would you change if this were your project.
My design decision: [describe it]
Why it works: Most feedback loops are too polite. This prompt is engineered to surface the objections before your stakeholders do.
6. Run an Accessibility Audit on Your Design Decisions
Before handing off to a dev, run your decisions through this.
I'm going to describe design choices for a [type of interface]. For each choice, flag any accessibility concerns based on WCAG 2.1 AA guidelines, explain the user impact (who is affected and how), and suggest an accessible alternative.
Design choices: [list your choices — colors, font sizes, interaction patterns, etc.]
Why it works: Accessibility checks usually happen too late, after the design is built. This integrates the check into the design phase where it's still cheap to change.
7. Competitive UI Analysis Prompt
Stop spending an hour manually cataloging what competitors are doing.
I'm designing [feature/screen] for [product type]. Describe how 5 leading products in this space typically handle this feature — include common UI patterns, what works well, common failure modes, and one unconventional approach worth considering. Then identify a gap that none of them fill well.
Why it works: The "gap that none of them fill" output is where differentiation comes from. Even when the analysis is imperfect, it accelerates a conversation that usually takes a full competitive review.
8. Build a Presentation Narrative for Stakeholders
Design reviews fail when you lead with how something looks instead of why you made it.
I'm presenting a design to stakeholders who care about [business metrics]. Help me build a narrative that: opens with the user problem (not the solution), explains the design decisions in terms of user behavior and business impact, anticipates 3 objections they're likely to raise and prepares my response, and closes with a clear ask.
Context: [describe your design and the business goals it serves]
Why it works: Reframes the presentation from "look what I made" to "here's the problem, here's evidence this solves it." Stakeholders stop reviewing aesthetics and start engaging with decisions.
These prompts aren't magic — they're structured thinking tools. The difference between a prompt that helps and one that gives you generic slop is specificity: force the role, force the format, force the output shape.
I have 500+ more organized by use case — design, writing, marketing, code, ops. $27, instant download: https://toshleonard.gumroad.com/l/rzenot
Top comments (0)