User Onboarding Design Prompts

Account Onboarding Flow

Prompt preview

Guide users through goals, workspace setup and optional personalization with a review step.

Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Account Onboarding Flow.

## Required content and structure

Guide users through goals, workspace setup and optional personalization with a review step.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm white, ink text and restrained mint selected states; generous spacing and simple controls. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Define the minimum setup needed to reach a usable workspace, required answers and optional personalization. Prepare the validation rules for each step.

## Layout and behavior

Keep the sequence short and show which steps are optional. Let users review their choices before completion and return to earlier answers without starting over.

## Task-specific acceptance check

- Retain answers on back navigation and distinguish required steps.
- Go back after completing several fields, skip optional personalization and trigger validation.
- Completion should reflect actual setup success rather than simply reaching the last screen.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Account Onboarding Flow. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Guide users through goals, workspace setup and optional personalization with a review step. Use the following task-specific layout guidance when translating the image into editable elements: Keep the sequence short and show which steps are optional. Let users review their choices before completion and return to earlier answers without starting over.

## Visual direction from the example brief

warm white, ink text and restrained mint selected states; generous spacing and simple controls.

## Interaction specification

The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Guide users through goals, workspace setup and optional personalization with a review step. Retain answers on back navigation and distinguish required steps. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

AI-generated visual concept for sign-in and recovery

AppsTechnical

Prompt preview

Design sign-in, recovery request, sent confirmation and invalid-link states.

View Prompt

Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Sign-In and Recovery.

## Required content and structure

Design sign-in, recovery request, sent confirmation and invalid-link states.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Define sign-in inputs, recovery states and approved authentication messages. Use fictional credentials and specify the behavior of expired or invalid recovery links.

## Layout and behavior

Separate entering credentials, requesting recovery and confirming that a request was received. Make the return to sign-in clear while avoiding messages that reveal whether an account exists.

## Task-specific acceptance check

- Avoid exposing account existence and do not collect real credentials in a demo.
- Test invalid input, a failed request and an expired link.
- A prototype should demonstrate states without collecting real passwords or pretending to authenticate a real account.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Sign-In and Recovery. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Design sign-in, recovery request, sent confirmation and invalid-link states. Use the following task-specific layout guidance when translating the image into editable elements: Separate entering credentials, requesting recovery and confirming that a request was received. Make the return to sign-in clear while avoiding messages that reveal whether an account exists.

## Visual direction from the example brief

light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy.

## Interaction specification

The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Design sign-in, recovery request, sent confirmation and invalid-link states. Avoid exposing account existence and do not collect real credentials in a demo. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

Team Invitation Flow

AppsMinimal

Prompt preview

Invite collaborators by email with role selection, pending invitations and resend states.

View Prompt

Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Team Invitation Flow.

## Required content and structure

Invite collaborators by email with role selection, pending invitations and resend states.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm white, ink text and restrained mint selected states; generous spacing and simple controls. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Define invite permissions, available roles, duplicate-email handling and pending or expired states. Use sample addresses instead of sending actual invitations.

## Layout and behavior

Keep each address paired with its role and validation message. Let users review invitations before sending, and show which individual requests succeeded or need correction.

## Task-specific acceptance check

- Handle duplicate addresses and permission limits without losing entered values.
- Enter duplicates and invalid addresses in the same batch.
- Preserve valid entries after errors and avoid presenting resend or revoke actions to users who lack the required permission.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Team Invitation Flow. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Invite collaborators by email with role selection, pending invitations and resend states. Use the following task-specific layout guidance when translating the image into editable elements: Keep each address paired with its role and validation message. Let users review invitations before sending, and show which individual requests succeeded or need correction.

## Visual direction from the example brief

warm white, ink text and restrained mint selected states; generous spacing and simple controls.

## Interaction specification

The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Invite collaborators by email with role selection, pending invitations and resend states. Handle duplicate addresses and permission limits without losing entered values. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

Application Empty States

AppsTechnical

Prompt preview

Design first-use, no-results, permission-limited and deleted-content states.

View Prompt

Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Application Empty States.

## Required content and structure

Design first-use, no-results, permission-limited and deleted-content states.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Identify why content is absent in each case: first use, no matching results, limited permissions or deleted content. Define the action the user can actually take for each reason.

## Layout and behavior

Use a concise explanation and one relevant next action. Preserve useful context such as active filters or the current folder instead of replacing the whole screen with an illustration.

## Task-specific acceptance check

- Give each state a truthful explanation and a relevant next action.
- Compare all four states side by side.
- A no-results state should offer filter recovery, while a permission-limited state must not promise that creating new content will solve access restrictions.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Application Empty States. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Design first-use, no-results, permission-limited and deleted-content states. Use the following task-specific layout guidance when translating the image into editable elements: Use a concise explanation and one relevant next action. Preserve useful context such as active filters or the current folder instead of replacing the whole screen with an illustration.

## Visual direction from the example brief

light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy.

## Interaction specification

The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Design first-use, no-results, permission-limited and deleted-content states. Give each state a truthful explanation and a relevant next action. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

Design a Better Onboarding

A Suggested Sequence

Account Onboarding Flow

Team Invitation Flow

Application Empty States

No Prompts Match Yet.

Turn Your Prompt into a Design.