The mobile navigation under pressure prompt I actually kept
I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.
Help me choose a mobile navigation pattern for frequent and infrequent actions. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Otherwise
This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For mobile navigation under pressure, I would start with these checks: - Name the user decision first - Check the keyboard path - Remove one competing action If you share real material, remove anything private first and replace bracketed fields with concrete details.