40 AI Prompts for Designers: UI/UX, Branding, and Creative Briefs (2026)

You are a senior UX researcher planning a research study.

Create a user research plan for [PRODUCT/FEATURE — e.g., a new onboarding flow for a project management tool].

Research objectives:
- [OBJECTIVE 1 — e.g., understand why 60% of users drop off during onboarding]
- [OBJECTIVE 2 — e.g., identify which features users expect to configure first]

Provide:
- Research questions (5-7, prioritized)
- Methodology recommendation (usability testing, interviews, surveys, diary studies — with rationale)
- Participant criteria and recruitment plan (sample size, demographics, screener questions)
- Session structure and timing
- Discussion guide or task scenarios
- Analysis framework
- Timeline and resource requirements
- Deliverables and how findings will be shared

Target: [NUMBER] participants over [TIMEFRAME]. Budget: [AMOUNT or "limited"].

Create a detailed user persona for [PRODUCT/SERVICE] based on these research insights:

Demographics: [AGE RANGE, ROLE, INDUSTRY, COMPANY SIZE]
Key behaviors: [HOW THEY CURRENTLY SOLVE THE PROBLEM]
Pain points: [FRUSTRATIONS WITH CURRENT SOLUTIONS]
Goals: [WHAT SUCCESS LOOKS LIKE FOR THEM]

Include:
- Name, photo description, and demographic details
- Job title and responsibilities
- Technology proficiency and tools used daily
- Goals (functional and emotional)
- Frustrations (specific, not generic)
- A day-in-the-life scenario
- Key quotes (things this persona would actually say)
- How they discover and evaluate new tools
- Decision-making factors (price sensitivity, features, ease of use, social proof)

Make the persona specific enough to make real design decisions against. Avoid generic traits that apply to everyone.

Create a detailed user journey map for [PERSONA] achieving [GOAL — e.g., a marketing manager setting up their first email campaign in our tool].

Journey phases:
1. Awareness / Discovery
2. Evaluation / Sign-up
3. Onboarding / First use
4. Core task completion
5. Return / Habit formation

For each phase, map:
- User actions (what they do)
- Touchpoints (where they interact with us)
- Thoughts (what they're thinking)
- Emotions (😊 → 😐 → 😤 scale with specific triggers)
- Pain points (specific friction, not generic)
- Opportunities (design interventions we could make)

Highlight the "moment of truth" — the single interaction that determines whether they become a retained user or churn.

Format as a structured table, not a visual diagram.

Write a moderated usability test script for testing [FEATURE/FLOW — e.g., the checkout process for a meal delivery app].

Duration: [MINUTES] per session
Participants: [PERSONA DESCRIPTION]
Platform: [WEB/MOBILE/DESKTOP]

Script structure:
1. Introduction and consent (2 min)
   - Explain think-aloud protocol
   - Reassure: we're testing the design, not them

2. Background questions (3 min)
   - Current behavior and experience with similar products

3. Task scenarios (15-20 min)
   - Task 1: [REALISTIC SCENARIO, not "click the button in the top right"]
   - Task 2: [SCENARIO]
   - Task 3: [SCENARIO]
   For each: scenario context, success criteria, follow-up probes

4. Post-task questions (5 min)
   - System Usability Scale (SUS) or custom rating
   - "What was the most confusing part?"
   - "What would you change?"

5. Wrap-up (2 min)

Include moderator notes for common situations: participant gets stuck, participant asks for help, participant goes off-script.

Create a competitive UX audit framework for [PRODUCT CATEGORY — e.g., email marketing platforms].

Competitors to analyze:
1. [COMPETITOR 1]
2. [COMPETITOR 2]
3. [COMPETITOR 3]

Evaluate each on:
- First-time user experience (signup to first value)
- Information architecture and navigation patterns
- Core task efficiency ([KEY TASK — e.g., creating and sending a campaign])
- Visual design and brand consistency
- Mobile responsiveness
- Error handling and help systems
- Accessibility (WCAG compliance)
- Onboarding approach (guided tour, tooltips, video, docs)

For each competitor:
- 3 things they do better than us
- 3 things they do worse
- 1 unique approach worth considering

Conclude with a gap analysis and top 5 opportunities for our product.

Write a design system specification for a [COMPONENT — e.g., Modal/Dialog] component.

Design system: [SYSTEM NAME]
Framework: [REACT/VUE/ANGULAR/FIGMA]

Include:
- Component description and use cases
- Anatomy (labeled parts: header, body, footer, overlay, close button)
- Variants (size: small/medium/large, type: informational/confirmation/destructive)
- Props/API:
  - title (string, required)
  - size (enum, default: medium)
  - onClose (function, required)
  - [OTHER RELEVANT PROPS]
- States (default, focused, loading, error)
- Behavior:
  - Focus trap when open
  - ESC key dismisses
  - Click outside behavior (configurable)
  - Scroll behavior (body scroll lock)
- Accessibility requirements (ARIA roles, keyboard navigation, screen reader)
- Content guidelines (title max length, body text guidelines, button labels)
- Do's and Don'ts with examples

Format for Storybook documentation or internal design system docs.

Document the design token structure for [BRAND/PRODUCT].

Organize tokens by:
1. Color
   - Primitives (raw color values with names)
   - Semantic tokens (text-primary, bg-surface, border-default, etc.)
   - Component-specific tokens
   - Dark mode mappings

2. Typography
   - Font families and fallbacks
   - Size scale (with px, rem, and use case)
   - Weight scale
   - Line height scale
   - Letter spacing

3. Spacing
   - Base unit and scale (4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px)
   - Named tokens (space-xs through space-3xl)

4. Elevation
   - Shadow levels with CSS values
   - Use cases for each level

5. Motion
   - Duration tokens (fast, normal, slow)
   - Easing curves with CSS values
   - Animation principles

For each token, include: name, value, usage description, and visual example description.

Write brand guidelines for [BRAND NAME], a [INDUSTRY/PRODUCT TYPE] company.

Brand attributes: [3-5 ATTRIBUTES — e.g., innovative, trustworthy, approachable]
Target audience: [PRIMARY AUDIENCE]
Competitive positioning: [HOW WE'RE DIFFERENT]

Cover:
1. Brand overview
   - Mission and vision
   - Brand personality and voice
   - Core values

2. Visual identity
   - Logo usage rules (spacing, minimum size, incorrect uses)
   - Color palette (primary, secondary, accent, neutral — with hex, RGB, CMYK)
   - Typography (headings, body, accent — with hierarchy)
   - Photography/illustration style guidelines
   - Iconography style

3. Voice and tone
   - Writing style (formal/casual, technical/accessible)
   - Tone variations by context (marketing, support, error messages, social)
   - Word list (words we use, words we avoid)
   - Example copy for common use cases

4. Application examples
   - Social media post formatting
   - Email template guidelines
   - Presentation slide guidelines

Keep it practical — a new designer or marketer should be able to produce on-brand work after reading this.

Write a creative brief for [PROJECT — e.g., redesigning the landing page for a B2B analytics product].

Client/stakeholder: [NAME]
Budget: [AMOUNT or range]
Timeline: [DEADLINE]

Include:
- Project overview (what and why)
- Business objective (measurable goal)
- Target audience (who, what they care about, current perception)
- Key message (the one thing the audience should take away)
- Supporting messages (secondary points, max 3)
- Competitive context (what competitors are doing visually)
- Mandatory elements (logo, legal copy, specific imagery)
- Tone and feel (with visual reference descriptions — "think Stripe's clarity meets Linear's polish")
- Deliverables list with sizes/specs
- Approval process and stakeholders
- Success metrics (how we'll know this worked)

The brief should be specific enough to align the team but open enough to allow creative solutions.

Audit the UX microcopy for [FEATURE/FLOW — e.g., the sign-up and onboarding flow].

Current copy:
[PASTE CURRENT MICROCOPY — buttons, labels, help text, errors, empty states, tooltips]

For each piece of copy, provide:
- Current text
- Issue (if any): clarity, tone, length, jargon, passive voice, accessibility
- Recommended revision
- Rationale for the change

Also identify:
- Missing microcopy (where users likely need guidance but don't have it)
- Inconsistencies (different terms for the same thing)
- Opportunities for personality (where bland copy could build brand)

Follow [VOICE/TONE GUIDELINES or "friendly, clear, and confident"] voice.

Design a comprehensive error message system for [PRODUCT TYPE — e.g., a SaaS project management tool].

Create error messages for:
1. Form validation errors (empty field, invalid email, password requirements, etc.)
2. Authentication errors (wrong password, account locked, expired session)
3. Permission errors (unauthorized, feature gated, team limit reached)
4. System errors (500, timeout, maintenance, offline)
5. Payment errors (card declined, expired, insufficient funds)
6. File errors (too large, wrong format, upload failed)

For each error:
- Error message (user-facing, plain language)
- Supplementary text (what to do about it)
- Tone (empathetic for user errors, transparent for system errors)
- Action button label

Rules:
- Never blame the user
- Never use technical jargon (no "Error 403" or "invalid token")
- Always provide a clear next step
- Keep messages under 2 sentences