Design & UX21 categories
Which states does this flow not handle?
The happy path is designed and nothing else is.
List the states this flow does not handle: loading, empty, error, partial permission, and the user returning three days later. For each one missing, say what the user currently sees and what they should see instead. Rank by how often it will happen, not by how interesting it is. Flow:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Flows and forms. Whole journeys rather than single screens: onboarding, missing states, and forms field by field.
Related prompts
Critique this onboarding flowSign-ups are healthy and activation is not.Review this form field by fieldAny form with more than three fields, before it goes anywhere near users.Find the gaps in this user flowThe happy path is designed and nothing else is.What would a first-timer miss?Before shipping something to people who have never seen it before.Tighten this formAny form that has quietly gained a field per quarter.Rewrite the microcopy on this screenBefore shipping a screen where the words started as placeholders you never revisited.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser โ free