UI/UX & Website Prompts

App Onboarding UX Flow Writer

Design a clear onboarding flow for a website or app, including screen flow, copy for each step, and friction risks.

✱ By PiSkill TeamFreeClaudeChatGPTGeminiMicrosoft Copilot

Best for

Product designers, founders, and UX writers who need to design a clear, well-written onboarding flow for a new or existing app or website.

Suitable LLM groups

FrontierReasoning

Prompt

You are acting as a UX writer and product designer who helps me design an onboarding flow for a website or app. You must not invent user research findings, analytics data, conversion rates, or user behavior statistics that I have not provided.

Here is my information:

Onboarding goal: {{goal}}
Who the users are: {{audience}}
What the product does: {{context}}
Key actions a new user should complete: {{desired_output}}
Constraints, such as number of screens or platform: {{constraints}}
Tone or brand voice: {{tone}}

If important details about the product, user segments, or key actions are missing, ask me clarifying questions before designing the flow.

Please produce a structured response with the following sections:

1. Onboarding goal: Restate what this onboarding flow should accomplish.
2. User segments: Describe the different types of users this flow may need to account for, based on what I provided.
3. Screen flow: List each screen in the onboarding sequence in order, with a short description of its purpose.
4. Copy for each step: Write the actual headline and supporting text for each screen.
5. Empty states: Describe what a user sees if they skip a step or have no data yet.
6. Success state: Describe what the user sees once onboarding is complete.
7. Friction risks: List points in the flow where users might get confused, frustrated, or drop off.
8. Improvement checklist: Provide a checklist to review the onboarding flow before shipping it.

Do not invent analytics numbers, conversion rates, or user research findings. If such data would strengthen a design decision, note that it should come from real testing rather than assumption.

How to use

Describe your onboarding goal, user segments, and key actions in the placeholders.
Specify any screen count or platform constraints.
Run the prompt in your preferred AI tool.
Answer clarifying questions if the product or user segments are unclear.
Use the screen flow and copy as a first draft for your design and development team.

Example input

Onboarding goal: get new users to create their first project within the first session. Users: small business owners new to project management tools. Product: a simple project management app. Key actions: create an account, create a first project, invite a team member. Constraints: mobile app, maximum five screens.

Example output

Onboarding goal: guide a new small business owner to create their first project during their initial session in the app.
User segments: first-time project management tool users who may feel overwhelmed by features, and users switching from another tool who want a quick setup.
Screen flow: screen one welcome and account creation, screen two a short explanation of what the app does, screen three creating the first project, screen four inviting a team member, screen five a success confirmation screen.
Copy for each step: screen one reads Welcome, let's get your first project started in under two minutes. Screen two reads Manage tasks, deadlines, and your team all in one place. Screen three reads Give your first project a name to get started. Screen four reads Invite a teammate to collaborate, or skip for now. Screen five reads You're all set, here's your new project.
Empty states: if a user skips inviting a teammate, the project view shows a friendly prompt to invite someone later from the settings menu.
Success state: the user lands on their new project dashboard with a clear next step highlighted, such as adding their first task.
Friction risks: users may feel pressured if the team invite step feels mandatory, and the project creation screen could cause drop-off if it asks for too many details up front.
Improvement checklist: confirm every screen has a clear single action, confirm skip options are available where appropriate, confirm copy matches the brand tone, confirm the success state clearly shows the user what to do next.

Customization tips

— Add real user quotes or feedback if you have them for more grounded friction risk analysis.
— Request a shorter flow if you want a leaner, faster onboarding experience.
— Ask for alternative copy versions if the initial tone does not match your brand voice.
— Combine this with the SaaS Dashboard UX Reviewer prompt for a full first-session experience review.

FAQ

No, it avoids inventing conversion rates or research findings and recommends gathering real data through testing.

Rate this prompt

How helpful was this?

Comments

Sam O.

Used this to ship 6 SEO articles in a week — the FAQ block alone is worth it.

Ines P.

Wish it had a Spanish voice preset, but overall very solid.

Related skills coming soon — browse all skills.

Related articles coming soon — visit the Learn hub.