100 AI Prompts for UI/UX Designers — Complete Guide

Write 6 usability test task scenarios for [product/feature]. Each task should: be scenario-based (not tell users where to click), have a clear success state, test a specific user goal, be realistic for [target user persona], and avoid using the exact UI labels as cues. Include a warm-up task and order them from easiest to hardest.

Create a UX research plan for [project/feature]. Include: research questions, recommended methods with rationale (given [timeline] and [budget]), participant recruitment criteria and screener questions, session structure with time allocation, data collection approach, analysis method, and how findings will be shared with the team.

Synthesize the following usability test observations into actionable findings: [paste observation notes from sessions with participants P1-P5]. Group issues by severity (Critical/Major/Minor using Jakob Nielsen's scale), describe each issue with: what happened, how many participants experienced it, the likely cause, and a recommended design fix.

Perform a heuristic evaluation of the following screen/flow: [describe the UI or paste a description]. Evaluate against all 10 Nielsen Norman heuristics. For each violation found, rate severity (0-4), describe the specific problem, the affected heuristic, and a concrete design recommendation to fix it.

Design a card sorting study to improve the information architecture of [product/website]. Define: open vs closed sort rationale, the list of [N] cards to sort (suggest cards for [content domain]), instruction script for participants, how to analyze results (dendrograms, similarity matrix), and how many participants are needed for statistical reliability.

Create a detailed empathy map for [user persona] interacting with [product/situation]. For each quadrant — Says, Thinks, Does, Feels — provide 4-5 specific, concrete observations. Also include Pains and Gains sections. Base the map on [describe the research data or context available].

Evaluate the following UI design description for accessibility issues: [describe the interface]. Check against WCAG 2.1 AA criteria for: color contrast, text alternatives for images, keyboard navigation order, focus indicator visibility, form label associations, error identification, and touch target sizes. Provide specific fixes for each issue found.

Write participant instructions for a 7-day diary study to understand how [user type] [performs activity]. Include: what to capture and when (triggers), the daily prompt questions (max 5 questions per entry), how to submit entries (channel), a reminder message template for Day 3 and Day 6, and tips for good diary entries with examples.

Analyze the following click-tracking/heatmap data description for [page/screen]: [describe click patterns, rage clicks, dead clicks, scroll depth]. Identify the top 3 UX issues revealed by the data, explain what each pattern suggests about user expectations, and recommend A/B test hypotheses to address each issue.

Define UX success metrics for [feature/redesign]. Include: behavioral metrics (task completion rate, time on task, error rate), attitudinal metrics (SUS score, CSAT, CES), business metrics that UX improvements affect, baseline measurement plan, target values with rationale, and how to report UX metrics to leadership alongside product metrics.

Write all the microcopy for a [form type: e.g., 'account creation'] form with these fields: [list fields]. For each field provide: label text, placeholder text (if useful), helper text, and error messages for common validation failures. Follow plain language principles, use second person, and ensure error messages tell users exactly how to fix the problem.

Write empty state copy for [product feature] for three scenarios: first-time user who has not created anything yet, user who has deleted all items, and search that returns no results. For each: write the headline, body text, and CTA button label. Make the copy helpful and encouraging, not apologetic.

Write user-friendly error messages for the following error scenarios in [product]: [list 8-10 error types: e.g., network timeout, invalid input, permission denied, server error]. For each error, write: a clear headline (what happened), an explanation in plain language (why it happened), and a recovery action (what to do next). Avoid technical jargon.

Write a sequence of 5 onboarding tooltips for [feature] targeting new users. Each tooltip should: explain the benefit (not the feature), be under 20 words for the body text, have a CTA button that moves the user forward, and follow a logical progression from context → action → outcome. Include the tooltip title and body for each step.

Improve the following UX copy from [product]. Current copy: [paste existing copy]. Issues to address: [describe problems: too technical, too long, negative framing, unclear CTA, etc.]. Provide 3 alternative versions with different tones (e.g., friendly, direct, professional), and explain the specific improvements made in each version.

Create a voice and tone guide for [product/brand]. Define: 3-4 voice attributes (what the brand sounds like), the difference between voice (constant) and tone (contextual), tone guidelines for 4 emotional contexts (celebratory, instructional, warning, error), words to use and avoid, and 5 before/after copy examples demonstrating the transformation.

Write push notification and email subject line copy for the following [N] notification types for [product]: [list notification types]. For each, provide: push notification title (max 50 chars) and body (max 100 chars), email subject line (max 60 chars), and preview text (max 90 chars). Optimize for open rate and clarity, avoid clickbait.

Write copy for a modal dialog that asks users to [describe the action requested: e.g., 'confirm deleting their account']. Include: a clear headline that states what is happening, body text that explains consequences without catastrophizing, a primary CTA button (the destructive or confirming action), a secondary CTA (cancel), and optionally a checkbox for 'Do not show again'. Follow the 'no tricks' pattern.

Review the following UX copy for localization readiness: [paste copy]. Identify: strings that will expand significantly in German/French/Spanish (flag anything over 30 chars), idioms that do not translate, cultural references to avoid, date/number/currency format placeholders, and UI strings that need different grammatical gender handling. Suggest localization-friendly rewrites.

Write a section of a content style guide for [company/product] covering: [topic: e.g., 'numbers and dates', 'button labels', 'capitalisation rules']. Provide clear rules with rationale, examples of correct and incorrect usage, edge cases, and exceptions. The audience is product designers and writers joining the team.

Design a user flow for [user task: e.g., 'upgrading a subscription plan'] in [product]. Define each step the user takes from entry point to completion. Include: decision points with branching paths, system feedback at each step, error recovery paths, and how the flow differs for [persona A] vs [persona B]. Present as a numbered step list with branches.

Define all the states needed for the [component type: e.g., 'data table row', 'form field', 'card'] component. For each state (default, hover, focused, active, disabled, loading, error, success, selected, empty), describe: visual change, user trigger, accessibility behavior, and any animation/transition needed. Identify any states that are missing from the current design.

Design a motion and animation system for [product]. Define: easing curves for different interaction types (enter, exit, transition), duration guidelines by element size and importance, spring physics values for interactive components, reduced-motion alternatives for all animations, and when NOT to animate. Provide CSS custom property definitions.

Critique the following wireframe/design description for [screen name]: [describe the layout and components]. Evaluate: information hierarchy (is the most important element most prominent?), cognitive load, consistency with [describe existing patterns], task flow logic, accessibility concerns, and missing states. Provide specific, actionable improvement suggestions.

Design a responsive layout strategy for [page/component] that adapts across mobile (320-767px), tablet (768-1023px), and desktop (1024px+). For each breakpoint, define: layout grid, component stacking/reordering rules, typography scale changes, navigation pattern adaptation, and which features to show/hide. Note any interaction pattern changes between breakpoints.

Analyze the following layout description for [screen]: [describe layout]. Identify opportunities to better apply Gestalt principles: proximity (grouping related elements), similarity (consistent visual treatment), continuity (guiding eye movement), closure (completing implied shapes), and figure-ground (foreground/background clarity). Suggest specific design changes for each principle.

Recommend the best data visualization approach for displaying [describe the data: type, relationships, comparisons]. Compare 3 chart type options, evaluate each for: data type fit, user comprehension, space efficiency, and animation potential. Provide a recommended implementation with: axis labels, color encoding, interactive states, and mobile adaptation.

Design a design token structure for a design system covering [product type]. Define the 3-tier token architecture: global tokens (raw values), semantic tokens (contextual meaning), and component tokens (specific usage). Create token naming conventions, cover: color, typography, spacing, elevation, border-radius, and motion. Provide Figma variable names and CSS custom property format.

Redesign the following complex feature using progressive disclosure: [describe the current design with all its complexity]. Identify the primary use case that 80% of users need, what to show by default, what to reveal on demand (secondary options), and what to put in advanced settings. Explain the disclosure trigger (expand link, settings icon, etc.) and the information hierarchy.

Design the keyboard navigation model for [component: e.g., 'date picker', 'data grid', 'modal dialog']. Define: Tab and Shift+Tab behavior, arrow key interactions within the component, Enter/Space actions, Escape behavior, focus trap scope (for modals), and how to communicate the component's keyboard controls to users. Reference WAI-ARIA authoring practices.

Write documentation for the [component name] design system component. Include: component purpose, when to use vs when not to use, all variants and their use cases, props/properties table (name, type, default, description), accessibility notes, related components, and 3 usage examples showing the component in context. Audience: designers and developers.

Define a governance model for a design system used by [N] product teams. Cover: contribution process (how teams propose new components), review criteria (when a pattern becomes a system component), ownership model (who maintains what), versioning and deprecation policy, communication channels for updates, and how to handle design system debt.

Create a pattern library entry for [UX pattern: e.g., 'inline validation', 'bulk actions', 'onboarding checklist']. Include: pattern description, problem it solves, when to use it, when NOT to use it, anatomy (key elements), behavior specification, accessibility requirements, and 2-3 real-world examples from products that do it well.

Write a design handoff specification for [feature/screen] to be passed to the engineering team. Include: component inventory with states, spacing specifications (use 8px grid values), color tokens to use (not hex values), typography styles (use style names), interaction descriptions for each interactive element, animation specs, and open questions for engineering.

Audit the following design system component set for inconsistencies: [describe components and variations]. Check for: naming inconsistencies (similar patterns named differently), visual inconsistencies (same purpose, different appearance), missing states (components that lack certain states other components have), and accessibility gaps. Prioritize issues by impact.

Document the rationale for the following color system for [product]: [describe the colors and their usage]. Explain: the primary/secondary/accent color selection reasoning, semantic color assignments (success, warning, error, info), contrast ratio compliance for each text/background combination, dark mode adaptation strategy, and usage guidelines for each color role.

Define a typographic scale for a [product type] using [type family]. Create a scale of 6-8 type sizes using a modular scale ratio of [1.25/1.333/1.414]. For each level, define: size, line-height, letter-spacing, weight, usage context, and responsive adjustments for mobile. Include the named styles (e.g., Heading 1, Body, Caption) and corresponding CSS custom properties.

Write usage guidelines for an icon library of [N] icons for [product]. Define: when to use icons alone vs with labels (and the accessibility requirement for each), grid and sizing standards (16/20/24/32px), stroke weight rules, color usage, semantic icon naming conventions, and how to request new icons to be added to the library.

Create a design QA checklist for reviewing implemented screens against design specifications. Organize into categories: layout and spacing (8px grid adherence, alignment), typography (size, weight, line-height), color (exact token usage, contrast), interaction (hover states, animations, loading states), accessibility (focus indicators, screen reader labels), and responsive behavior.

Plan a migration from [old design system/legacy styles] to [new design system] for a product with [N] screens. Define: migration strategy (big bang vs incremental), component mapping table (old → new equivalents), breaking changes and how to handle them, team communication plan, quality control process, and how to track migration completion.

Structure a design critique session for a [duration] meeting reviewing [feature/screen] with attendees: [list roles]. Define: the critique agenda, how to frame feedback (I like / I wish / What if), how to prevent solution-jumping, a decision log format for recording agreed changes, and how to close the session with clear next steps.

Help me justify the following design decision to a skeptical stakeholder who prefers [their preferred approach]: [describe the design decision you made and why]. Structure the argument: user research evidence supporting the decision, business impact rationale, trade-offs acknowledged, and how to frame a test to resolve the disagreement if needed.

Write a UX impact report for [quarter/period] showing the business value of design work. Include: usability improvements with before/after metrics, design debt reduced, design system adoption metrics, user research insights that influenced product decisions, NPS/CSAT changes attributable to UX work, and the estimated revenue or retention impact.

Write a design brief for [project]. Include: project background and business context, target users with key characteristics, problem to solve (not solution to build), constraints (technical, timeline, brand), success criteria (how we know the design worked), key stakeholders and their interests, and what is explicitly out of scope.

Create a UX strategy presentation outline for [product area] for a [duration] executive presentation. Structure it as: current user experience pain (with data), competitive benchmark, our design principles, 3 strategic UX bets for [timeframe], required investments (team, tools, research), expected outcomes, and what success looks like at the end of [period].

Write a UX case study for [project name] for a portfolio or team presentation. Include: project context and constraints, my role and contributions, the research approach and key insights, design iterations with rationale for changes, the final solution with key design decisions explained, measurable outcomes, and what I would do differently.

Plan a 5-day design sprint to tackle [challenge]. For each day, provide: the day's goal, specific activities with time allocations, facilitation instructions, materials needed, and expected outputs. The team is [N people, list roles]. Define how to select the sprint target on Day 1 and how to structure the user test on Day 5.

Create a design team charter for a [N-person] UX team at [company type]. Define: team mission, the principles that guide how we work, our responsibilities within the product development process, how we collaborate with product and engineering, our meeting cadences, how we give and receive feedback, and how we measure team health.

Write a business case for redesigning [feature/product area]. Include: current state pain with quantified impact (user frustration data, support ticket volume, metric underperformance), proposed redesign scope, expected business outcomes (retention, conversion, support cost reduction), resource requirements (design and engineering time), risk assessment, and recommendation to proceed.

Write 5 design principles for [product/team]. Each principle should: be specific enough to guide a real design decision (not generic like 'be simple'), be written as an imperative sentence, include a 'not [anti-pattern]' counterpoint, have a real product example demonstrating the principle, and feel authentically yours. Avoid the word 'user'.