Ship with Claude CodeFrom terminal-curious to a live site of your own
Work with Claude CoworkHand off real tasks to an AI that works on your computer
Land Your Next JobRun a real job search with Claude, from posting to interview
Claude DesignDesign work that wins clients, with Claude doing the heavy liftingAll 9 coursesPlan Your Whole Trip In An Afternoon
Start here. Give it your city and dates and it clusters each day into one or two neighbourhoods so you're not crossing the city twice, with how to get between stops and a time buffer built in. Run the Food prompt afterwards to fill the meal pegs.
Example · Input
Kyoto, 3 days in April. 2 adults, relaxed pace, mid budget in ₹. We love temples and food.
Example · Output
Per day: a "today's cluster" label, a table of Time | Place | Why | Duration | how to get to the next stop + fare, lunch and dinner pegs, an if-behind / if-ahead line, and a verify-before-you-go list.
You are my local trip planner. Build a day-by-day route for my trip. Before we start: I can plan and sequence, but I can't book anything, and my read on opening hours, closed days and last-entry times goes stale. Treat this as a draft to verify — turn on web search in Claude and confirm every timed entry on the official site before you rely on it. MY TRIP: - City / country: [FILL] - Travel dates (or the month): [FILL] - Who's going: [adults / kids + ages / seniors] - Budget level: [shoestring / mid / comfortable] — home currency: [₹ / R$ / $ / other] - Travel style: [packed / relaxed] - Diet & allergies: [veg / Jain / halal / vegan / none — plus any allergy] - My home country: [FILL] - Must-sees I already want: [LIST, or "you choose"] Reply in the language I wrote this in. If exactly one of these is missing and it would change the plan, ask me for that one thing and stop. Otherwise continue. How to build the route — these matter more than the list of sights: - Cluster each day into ONE neighbourhood, or two that sit right next to each other. Never send me across the city and back on the same day. - Judge whether two stops belong together by how hard it is to travel between them, not how close they look on a map. A river, a highway, or one metro change with no direct line makes near things far. - For every hop, tell me HOW: walk (X min) / which metro line / auto-rickshaw / rideshare, and a rough local fare in my currency, marked "approx". - Give me 2–3 fixed anchor sights a day. Everything between them — a meal, a rest break — is flexible glue, not a locked slot. - Leave a 15–20% time buffer. A day packed to the minute breaks on the first slow queue. - Order the day around heat, crowds and closing times: outdoor or uphill early, indoor or air-conditioned at midday, a sunset spot last. Watch for weekly closed days (many museums shut Mondays) and last-entry cutoffs, and say them. For each day give me: 1. A one-line "today's cluster" label, and one line on why this order. 2. A table — Time | Place | Why it's worth it (1 line) | Duration | → Next: how to get there + minutes + approx fare. 3. A lunch peg and a dinner peg slotted inside the cluster (I'll fill the exact place from the Food prompt). 4. One line: "If behind, cut ___. If ahead, add ___." End with a short "verify before you go" list: which sights need a timed or online ticket, which have a weekly closed day, and anything to book ahead — for me to confirm on the official site with web search on.
