Quest Maps and Helpful NPCs

Picture the town square. The quest giver does not mumble lore, they hand you a clear map, a deadline, and what counts as “done.” Good NPCs turn wandering into progress. Your AI can too, if you brief it like a quest. Think of the output as a quest map you can actually follow.

Try this, small and strict
• 🎯 Role and goal, “You are a UX mapper, produce a user flow for account sign up.”
• 🧱 Scope, “Mobile first, 5 to 7 nodes, one happy path, one recovery path.”
• 🏷️ Naming, “Use node names like Start, EmailEntry, OTPVerify, Success. Use edge verbs like tap, submit, error.”
• ✅ Acceptance, “Return a list of nodes with IDs, edges with verbs, one sentence per node describing intent.”
• 🧪 Example, “Sample output, Start → EmailEntry via tap, EmailEntry → OTPVerify via submit.”
Add one line of context if needed, “Audience is first-time users, no saved sessions.” Keep a prompt log so the team can replay the quest and compare outputs.

Clear roles cut fluff, tight scopes prevent sprawl, explicit names make linking easy later, acceptance criteria keep the output testable. When the map is legible, tomorrow’s prototype links cleanly and testing focuses on truth, not translation.