AI Prompts for UX Designers

Create a detailed user persona for a [product/service] user. Include: name, age, occupation, and demographic snapshot, goals (3 primary goals related to the product), frustrations and pain points (4-5 specific pain points), technology comfort level and device usage, a day-in-the-life scenario showing when and how they interact with our product, behavioral patterns (how they make decisions, what influences them), a key quote that captures their attitude, and 3 scenarios where they would use our product. Base the persona on [research data/user type description].

Design a 45-minute moderated usability test script for testing [feature/product/prototype]. Include: introduction script with consent and recording disclosure (3 min), warm-up questions about participant background (5 min), 5 task scenarios with specific success criteria and time limits, post-task questionnaires (SUS or SEQ) after each task, probing questions for when participants struggle, a post-test interview guide (5 min), and a debrief script. For each task, include: the scenario context, the specific instruction (without revealing the path), what to observe, and follow-up questions.

Write UI microcopy for these [product] interface elements: [list specific elements — error messages, empty states, loading states, tooltips, confirmation dialogs, onboarding steps, etc.]. For each element, provide: the primary copy, a secondary/supporting copy option, the tone (helpful/playful/serious/encouraging), character count, and rationale for the language choice. Follow these UX writing principles: clarity over cleverness, use active voice, front-load important information, and be specific about what the user should do next. Match a [brand voice description] tone.

Help me prepare a structured design critique for [feature/screen/flow]. The design goals are: [list goals]. Organize the critique around these lenses: 1) Does it meet the user's primary goal efficiently? 2) Is the information hierarchy clear and scannable? 3) Are interactive elements discoverable and consistent? 4) How does it handle edge cases and error states? 5) Is it accessible (WCAG AA)? For each lens, provide: 3 specific questions to ask, what to look for in the design, common pitfalls in this type of interface, and a rating framework (works well / needs refinement / needs rethinking).

Design an information architecture for a [product/website type] with these content types: [list content types and features]. Create: a site map with primary, secondary, and tertiary navigation levels, card sorting suggestions for organizing content into categories, navigation labeling recommendations with alternatives tested against clarity, user flow diagrams for the 3 most critical tasks, and search and filter taxonomy recommendations. Consider [user research findings] when organizing. Prioritize by user frequency and importance.

Create a comprehensive accessibility audit checklist for [product/feature] targeting WCAG 2.1 AA compliance. Organize by category: perceivable (color contrast, alt text, captions), operable (keyboard navigation, focus management, timing), understandable (error handling, labels, predictability), and robust (semantic HTML, ARIA, cross-browser). For each item, include: the specific WCAG criterion, what to check, how to test it (tools and manual methods), common failures in [product type] interfaces, and the fix approach. Prioritize items by impact on users with disabilities.

Write a design system specification for a [component name] component. Include: component description and use cases, visual variants (sizes, states, themes), props/API with descriptions and default values, interaction states (default, hover, focus, active, disabled, loading, error), responsive behavior across breakpoints, accessibility requirements (ARIA roles, keyboard behavior, screen reader announcements), content guidelines (character limits, truncation rules), do's and don'ts with examples, and related components. Format as a documentation page.

Create a user journey map for [persona name] completing [goal] with [product/service]. Map these phases: awareness, consideration, onboarding/first use, regular use, and advocacy. For each phase, document: user actions (what they do), touchpoints (where they interact), thoughts (what they are thinking), emotions (frustrated/neutral/delighted with reasoning), pain points and opportunities, and metrics to track. Highlight the moments of truth — the 3-4 critical interactions that determine whether the user succeeds or churns. Include recommendations for improving each pain point.