Free UI / UX Design Prompts

Act as a senior product designer. Design a user flow for [GOAL]. User context: [PASTE]. Constraints: [PASTE]. Output: 1) the entry points, 2) the happy-path steps, 3) the 3 most likely fork points and how each is handled, 4) the exit / success state, 5) the failure recovery. End with the 1 step most likely to be the conversion killer and how I'd instrument it.

Critique this screen as a senior product designer: [DESCRIBE OR PASTE SCREENSHOT NOTES]. Audience: [PASTE]. Primary action: [PASTE]. Output: 1) the visual hierarchy verdict, 2) the 3 most likely points of confusion, 3) the cognitive load issues, 4) the accessibility flags, 5) one rewrite that would lift conversion. Be specific. End with the 1 change that has the highest ROI.

Design the empty state for [FEATURE]. What user has just done to land here: [PASTE]. What action moves them forward: [PASTE]. Output: 1) the headline (under 6 words), 2) the supporting microcopy (under 20 words), 3) the primary CTA label, 4) the secondary educational pathway, 5) the illustration concept in one sentence. End with the variant for the second-time user.

Design an onboarding flow for [PRODUCT]. Goal: [PASTE primary outcome]. Time-to-value target: [PASTE]. Output: 1) the welcome screen (single sentence), 2) the 2-3 information asks, 3) the magic moment screen and what triggers it, 4) the exit state, 5) the skippable / non-skippable rule. End with the data point I'd watch in week 1.

Redesign this form to reduce abandonment: [PASTE current fields]. Conversion goal: [PASTE]. Audience: [PASTE]. Output: 1) the fields to cut, 2) the fields to defer to post-submission, 3) the order change rationale, 4) inline-validation pattern, 5) the progress indicator decision. End with the 1 friction point most likely killing completion.

Rewrite this microcopy for clarity and tone: [PASTE]. Product voice: [PASTE]. Audience: [PASTE]. Output: 1) the new versions, 2) what each cut and why, 3) the variants for confirmation, error, success, 4) the words I should banish from the product entirely. End with the rule for myself on hedging language.

Run an accessibility audit on this design: [DESCRIBE]. Output: 1) the contrast issues, 2) the missing focus states, 3) the screen-reader gaps, 4) the touch-target failures, 5) the cognitive-load concerns. For each: the specific fix and the level (A, AA, AAA) it satisfies. End with the 3 fixes to ship before launch.

Write the rationale for this design decision: [PASTE]. Stakeholder: [PASTE]. Their concern: [PASTE]. Output: 1) the user problem in 1 sentence, 2) the design hypothesis, 3) the 3 alternatives I considered and why I rejected them, 4) the measurable success criterion, 5) the rollback plan if it fails. Under 250 words.

Design a dashboard for [ROLE]. The 3 questions this role asks every morning: [PASTE]. Data available: [PASTE]. Output: 1) the single hero metric, 2) the supporting context (max 4 elements), 3) the data layout (where each lives), 4) the interactions (drill-down? filtering? export?), 5) the rule for what to NOT show. End with the 1 chart most likely to be ignored.

Design the error states for [FEATURE or ACTION]. Common failure modes: [PASTE]. Output: 1) the message structure (what happened + why + what to do next), 2) the tone rules (no jargon, no blame, plural plurals), 3) the variant for recoverable vs unrecoverable, 4) the fallback for unknown errors, 5) the rule for what to log to support. End with the message I should never write.

Write the design spec for engineering handoff on this feature: [PASTE]. Output: 1) the user-facing summary, 2) the screens and their states (loading, empty, populated, error), 3) the interactions with explicit timing, 4) responsive behavior across breakpoints, 5) edge cases worth flagging. End with the open questions I owe answers to.

My current navigation has [N] items: [PASTE]. Product growth: [PASTE]. Help me restructure. Output: 1) the proposed grouping, 2) the labels, 3) the persistent vs contextual items, 4) the mobile pattern, 5) the deprecation path for renamed items. End with the analytics I'd track to validate the new IA.

Help me decide: should [INTERACTION] be a modal, a side panel, a sheet, or a dedicated page? Inputs from user: [PASTE]. Frequency of use: [PASTE]. Output: 1) the recommendation with reasoning, 2) the trade-offs of the runners-up, 3) the accessibility implications, 4) the mobile fallback, 5) the rule I should apply next time. End with the test that would invalidate the recommendation.

Design the UX for an AI feature that does [TASK] for [USER]. Output: 1) the entry point (when and where it appears), 2) the input pattern (free text, buttons, suggestions, mixed), 3) the in-flight feedback while AI works, 4) the result presentation including how to edit/regenerate, 5) the failure mode handling. End with the trust-building element and the explicit guardrail.

Design a pricing page for [PRODUCT]. Tiers: [PASTE]. Target conversion mix: [PASTE]. Output: 1) the headline above the tiers, 2) the tier-card structure (feature highlight rule, price prominence, CTA), 3) the comparison table beneath, 4) the FAQ to address common objections, 5) the proof element (testimonial, logo bar). End with the dark-pattern I'm tempted to use and should not.