What this prompt does
This prompt hands the AI a complete design brief for a travel itinerary planner app and asks it to produce screen-by-screen UX for seven modules: trip dashboard, trip overview, a day-by-day itinerary builder, place discovery, packing lists, an expense tracker, and a framework-specific implementation section. Instead of a vague "design a travel app" request, it pins the output to your actual product through [app_name], [target_travelers], and [differentiator], so the AI designs for your audience rather than a generic one.
The structure works because it separates what the screens are from how they're built. The [trip_types] and [planning_style] variables shape the information architecture — a backpacking app needs different defaults than a luxury concierge tool — while [framework] (defaulting to React Native + Mapbox + Realm) forces the model to reason about offline maps, sync, and performance rather than handing back screens that can't run on a plane.
When to use it
- You're scoping a travel or trip-planning app and need a full screen inventory before writing code.
- You want a day-by-day itinerary builder with drag-and-drop and travel-time estimates designed up front.
- You're deciding how detailed vs. flexible the planning flow should be via
[planning_style]. - You need the offline-maps and expense-splitting requirements documented before you commit to a stack.
- You're pitching a client and want a coherent feature map tied to a clear
[differentiator].
Example output
Expect a structured design document: each of the seven modules broken into named screens, with component-level detail (card carousels, timeline blocks, map views, budget summaries) and the interactions between them. The final [framework] section reads as an implementation checklist covering offline tiles, calendar export, push notifications, and performance targets — not finished code, but a spec a developer can build against.
Pro tips
- Set
[differentiator]to one sharp idea (the default is AI smart-scheduling). A diffuse differentiator produces diffuse screens. - Match
[framework]to your real constraints — if you're not using Realm or Mapbox, swap them so the offline section stays accurate. - Narrow
[trip_types]if your MVP only handles a subset; listing all seven makes the AI design for breadth you may not ship. - Use
[planning_style]to bias the itinerary builder: "hour-by-hour" yields a denser timeline than "day themes." - Run it once for the full map, then re-prompt module by module ("expand the Day-by-Day Itinerary Builder into wireframe-level detail") to go deeper.
- The drag-and-drop builder with travel-time estimates is the riskiest module — prototype that screen first before trusting the rest.
