Prompt
You are a Senior UX Designer and Information Architect with 10+ years of
experience designing complex digital products. I need you to generate a
complete UX architecture document for my product.
---
PRODUCT CONTEXT
- Product name: [NAME]
- Product type: [Web app / Mobile app / Both]
- Industry: [e.g. Fintech / Health / E-commerce / SaaS]
- Target users: [Describe your primary user, who they are, their goals,
tech comfort level]
- Core problem it solves: [1–2 sentences]
- Key user actions (the 3–5 things users must be able to do): [List them]
- Any known competitors or inspiration: [Optional]
---
WHAT I NEED YOU TO GENERATE
1. INFORMATION ARCHITECTURE (IA)
- Full sitemap of every screen/page in the app
- Grouped by section (e.g. Onboarding, Dashboard, Settings)
- Hierarchy shown clearly (parent → child pages)
- Navigation structure (bottom nav / sidebar / top nav, recommend which
and why)
2. USER FLOWS
Generate step-by-step user flows for these core journeys:
- Onboarding & account creation
- Core action flow (the main thing the user comes to do)
- Settings & profile management
- Error recovery flow
For each flow: show every screen the user touches, the decision points,
and what happens on each path (success, error, edge case).
3. FULL SCREEN-BY-SCREEN BREAKDOWN
For EVERY screen in the app, provide:
- Screen name
- Purpose (what the user is trying to do here)
- Key UI elements on the screen
- Primary action (main CTA)
- Secondary actions
- Navigation options available
4. MICROCOPY FOR EVERY SCREEN
For each screen, write the actual copy for:
- Page/screen title
- Subheading or supporting text
- CTA button labels
- Input field placeholder text and labels
- Tooltip or helper text (where relevant)
5. ERROR STATES
For every screen or action that can fail, write:
- The error scenario (what went wrong)
- Error message headline (short, clear)
- Error body copy (explain what happened + what to do)
- CTA label to recover (e.g. "Try Again", "Go Back", "Contact Support")
Cover at minimum: form validation errors, network/connection errors,
permission denied, session expired, payment failure (if applicable).
6. EMPTY STATES
For every screen that can appear empty (no data yet), write:
- Empty state illustration description (what to show visually)
- Headline
- Supporting copy
- CTA to help user take their first action
Cover: first-time user empty states AND zero-result search/filter states.
7. LOADING & TRANSITION STATES
For key screens, describe:
- What loading state looks like (skeleton screen, spinner, etc.)
- Loading copy if any (e.g. "Getting your dashboard ready…")
- Transition message after a completed action
(e.g. success toast, confirmation screen)
8. STRUCTURAL RECOMMENDATIONS
Based on the product type and user goals:
- Recommend the best navigation pattern and why
- Flag any screens that might cause confusion or drop-off
- Suggest any flows that could be simplified or merged
- Identify where progressive disclosure should be applied
- Call out any accessibility considerations per screen
---
OUTPUT FORMAT
Structure your response like a UX specification document with clear
headings for each section. Use tables where it helps clarity
(especially for microcopy and error states). Be exhaustive, I want
this to be thorough enough to hand directly to a developer or use as
a Figma annotation reference.How to use
- 01
Fill in every [...] field under PRODUCT CONTEXT: name, type, industry, target users, core problem, and key actions. [Optional] can stay as is or be deleted.
- 02
Paste the completed prompt into Claude or ChatGPT.
- 03
If the answer stops partway, ask it to continue from the last section.
- 04
Take one section at a time into review with your team rather than accepting the whole document at once.
Tips
- The more specific the target user and key actions, the less generic the sitemap and flows.
- For deeper work on one part, follow up with the single-purpose prompts linked under Related prompts.