Prompt library · AI · 19 prompts
Prompts from the guide
A custom travel itinerary: day by day, without hours of planning
19 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.
Seven things the brief must include
Plan a trip to [destination] for [number] days, dates [start date—end date]. Don't give me a list of sights, I want a day-by-day plan. Who's traveling: [e.g. 2 adults (32 and 34) and kids aged 5 and 9] Where we're staying: [neighborhood / address / name of lodging] Getting around: [public transit / car / on foot, how much we're willing to walk per day] Budget: [amount] per person per day, covering [food, admission, local transport] Pace: [max 2 bigger things a day, afternoon break 1—3 pm, nothing before 9 am, evenings dinner at most] Interests: [architecture, food, views, markets] What we don't want: [long lines, shopping malls, anything not stroller-friendly] Fixed points: [day 4 at 6 pm concert downtown; arrival day 1 at 2 pm, departure last day at 11 am] Before you start planning, do two things: 1. Repeat back in your own words which constraints you understood. 2. Write 5 questions that, if I answered them, would make the plan noticeably more precise. Only then, once I've answered, propose the plan.
How much actually fits into a day
Here's my plan for [day X]: [paste the day's plan] Calculate it realistically: - how many hours the program itself takes (excluding transfers) - how many hours of transfers between points, noting for each what mode of transport and how long - how much time is left for food, breaks, and unexpected delays - what time this plan would have me back at my lodging in the evening Then give a verdict: is this day realistic for [who's traveling and at what pace]? If not, say exactly what to cut so the point of the day survives. Don't phrase it as a suggestion — phrase it as a cut: what goes.
A skeleton in half-days with transfer times
Based on the brief and answers above, build a day-by-day itinerary. Format for each day: ### Day [number] — [date], [the day's theme in one sentence] - Morning: [what, where, how much time] - Transfer: [from where to where, by what, how many minutes] - Afternoon: [what, where, how much time] - Transfer: [from where to where, by what, how many minutes] - Evening: [what, where] - Food: 2 tips at our price level, each with neighborhood and what it is - Bonus if there's time left: [1 nearby thing] - Estimated spend for the day: [amount per person, broken into admission / food / transport] Rules: - Points within one day must be close to each other. Never send me from one end of the city to the other and back. - Respect the fixed points; build the rest of the day around them. - Leave at least 90 unscheduled minutes in every day. - For each point, note whether it's suited to rain (indoor / outdoor / mixed). - Don't make anything up. If you're not sure a place exists or is open, say so instead of guessing. At the end, give a list of everything that needs verifying or booking.
A geography check: where the plan is traveling for no reason
Take my whole itinerary and regroup it purely by geography: 1. Cluster all the places by neighborhood or area. 2. For each cluster, note how long it would take to see it in full. 3. Show me which points are currently on a different day than they geographically should be — and how many extra minutes a day that's costing me. 4. Propose a regrouped version where each day = one or two neighboring clusters, keeping my fixed points intact. Give me a comparison: total transfer minutes in the original versus the new version.
Iterate — don't start over
Adjust the plan, leave the other days unchanged: - Day 3 is too packed — keep it to two things at most, and make sure there's a relaxed lunch. - Drop [place] entirely, we don't want to go there. - Add a half-day outside the city, ideally within 60 minutes by train. - Leave evenings 2 and 4 completely free, we don't want the whole vacation scheduled into the night. - Cut the spend: nothing with admission over [amount] per person — propose a cheaper alternative that serves the same purpose. Give me the whole itinerary again in the same format, and above it a short list of exactly what you changed.
A budget check for the whole trip
Here's the full itinerary: [paste the itinerary] Put together a budget for the trip for [number of people]: - break it down by day: admission, food, local transport, other - list one-time items separately (airport transfers, day passes, trips outside the city) - add it all up and compare it to my limit of [amount] - if I'm over, propose 5 specific cuts ranked from least to most painful For every price, say whether you're estimating it or whether I should verify it. Don't present anything as a current price — prices change and you don't know them.
An indoor alternative for every outdoor block
For every outdoor point in my itinerary, add a backup option for rain or extreme heat. Requirements for the alternative: - must be in the same neighborhood or at most 15 minutes from the original point - must be indoors and open on the day I'd be there - must take roughly the same amount of time as the original point - must be at the same price level Format: day | original point | replacement | how to get there from the original spot | why this replacement makes sense. At the end, tell me which days are the most weather-sensitive and which ones I should swap with each other if the forecast turns bad.
What to do when something falls through
I'm at [place], it's [time], and [what happened: the museum is closed / it's raining / the subway isn't running / we're feeling sick from the heat]. My plan for the rest of the day was: [paste the rest of the day] Suggest 3 alternatives: A) something similar nearby, so the day stays in the same spirit B) a low-key option — a café, a park, something with no walking C) reshuffling the schedule: what from the following days could get moved up so the rest of the trip doesn't collapse For each option, note how far it is from here and how to get there. Then tell me what I should verify right now, before heading over.
A list of everything that needs arranging ahead of time
Here's my finished itinerary: [paste the itinerary] Traveling [start date—end date], [number] people. Give me a checklist of everything that needs to be arranged before departure. A table with columns: what to arrange | why | how far ahead | where it's done (website / phone / on site) | deadline (specific date) | done Include: - timed-entry tickets and anything with limited capacity - restaurant reservations where those are typically needed - tickets and seat reservations for trains, ferries, and long- distance buses - day or multi-day transit passes — worth it or not - insurance, documents, passport validity, visas, any required registrations - car rental, downtown parking, toll roads - anything on my plan that has a fixed time Sort by deadline, most urgent first. For each item, note how I'd confirm it still applies for my specific dates — those details I need to verify on the official website.
Documents and what to print
I'm traveling [date] to [country], [number of people, including children's ages]. I'm traveling [by plane / by car]. Put together a checklist of documents and things to arrange: - what I need to carry (ID, confirmations, cards) - what's worth having printed as well as on my phone, and why - what I should email myself as a backup - what I should photograph in case of loss Write it as a checkable list. For items governed by specific rules by country or carrier, don't give me a claim — tell me exactly where to verify it. I don't want binding statements from you about visas, document validity, or carriage conditions.
What to always verify, and what a spot check covers
Here's my itinerary: [paste the itinerary] Build me a verification list. For every place I'm going to specifically according to the plan, one line: place name | day and time I'm supposed to be there | exactly what to verify (opening hours, last entry, reservation needed, price) | where to verify it (official website, phone, carrier) Sort by day. Put the 5 places where a mistake is most expensive at the top — where being closed would cost me half a day or an excursion. Don't state opening hours or prices yourself. I want a list to verify, not answers.
After verifying: write down what changed
I verified the opening hours and connections and here's what doesn't match: - [Place A] is closed on [day]. - [Place B]'s last entry is at [time], not what I had planned for. - The train to [place C] only runs at [times], not throughout the day. - [Other finding.] Rework the itinerary so it reflects these facts. Change as little of the rest of the plan as possible — I want to see exactly what shifted because of this. Give me the whole itinerary again, with a list of changes above it.
A family vacation with kids
Planning [number] days in [destination] with kids [age and age] and [number] adults. We're staying [where]. Budget [amount] per day total. Build an itinerary that respects a kid's rhythm: - we head out no earlier than [time], we need a break in the afternoon [times] - at most one “big” thing a day, the rest looser - for each day, note where there's a playground, a park, or somewhere to just sit nearby, and where the public restrooms are - for each point, note whether it works with [a stroller / a tired five-year-old], and roughly how long kids can handle it - food: places where kids will actually eat, and what to do if they refuse a restaurant - one indoor rain alternative per day At the end, give me 5 things not to do with kids in [destination], and why.
A city weekend
I only have [2] days in [city] — arriving [day, time], leaving [day, time]. Staying [where]. We're [who]. A brisk pace is fine. Build a plan that makes the most of the time: - start from the fixed points (arrival, departure) and tell me how many hours I actually have - split the city into 2 areas, one per day, so we're not crossing back and forth - put 3 things into the plan I'd regret missing, and flag them as priorities - for each point, note how many minutes are enough to make it worth visiting, and what's visible from outside for free - where lines tend to form, note what time has the smallest crowds - an evening program for both days near our lodging At the end, tell me what I had to sacrifice given the time, and what would fit if I stayed one more day.
A road trip
Planning a road trip: [start] — [destination / loop], [number] days, by car, [who's traveling]. Lodging [booked in advance / as we go]. At most [3] hours of driving a day, with kids we need a stop every [90] minutes. Break the trip into legs: - each day: from where to where, how many kilometers, how many hours of actual driving - stops along the way: what, where, how much time, why it's worth stopping for - where to sleep each night and why there specifically - for each leg, note the last sensible spot for gas, food, and a break - how many nights to spend in one place — favor longer stays over driving every day Note separately: - what I should verify about parking in each town - where the plan suffers most if I'm running an hour behind Driving times are your estimate — tell me which stretches I should verify on a map, since the estimate could be way off there.
One page you also have offline
Turn my finished itinerary into one clean page I can open on my phone. Requirements: - a summary at the top: dates, lodging with address, emergency contacts, reservation numbers (leave these blank, I'll fill them in myself) - then the days one after another, each collapsible - for each point: name, time, address, how to get there - outdoor points clearly marked with their rain alternative - checkboxes for things that get checked off (reservations, tickets) - large, easy-to-read-in-sunlight text, works on mobile - no outgoing links, has to work with no connection Keep the text exactly as it is in the itinerary, don't add anything.
Sharing with family and travel companions
Make two condensed versions of my itinerary: 1. For travel companions: what to bring, where and when we're meeting up each time, what needs to be on hand and when (tickets, documents), and each other's phone numbers. No sightseeing descriptions. 2. For family staying home: where we're sleeping each night, lodging address and phone number, a one-sentence daily program, arrival and departure times, and when we'll likely be unreachable. Make both as short as possible so they fit in a single message. Don't put reservation numbers or anything else that shouldn't be in a message into the version for family.
Packing based on the forecast and the plan
Here's my itinerary and here's the weather forecast for [destination] for [dates], which I looked up myself: [paste the itinerary] [paste the forecast: daytime and nighttime temperatures, precipitation] Build a packing list for [who's traveling], [number] days. Split it into: clothing | footwear | electronics | toiletries and first aid | documents | carry-on | buy there. Rules: - base it on what's actually in the plan: where there's a lot of walking, where I need to dress up, where I'll be sitting outside in the evening - for each item, note why it's there (which day or weather it's for) - flag what can be bought there in a pinch and what can't - assume [an 8 kg carry-on / a checked bag] - no generic advice, only things tied to my specific plan At the end, give me 5 things people most often forget for this kind of trip.
Phrases in the local language
I'm going to [country] and don't speak [language]. Put together a phrase card with phrases I'll realistically use based on my plan — it's mostly [restaurants, public transit, markets, museums]. For each phrase: - what I'm saying, in English - how it's written in [language] - how to pronounce it, transcribed so an English speaker would read it right Include: - greetings, please, thank you, excuse me - ordering in a restaurant, the bill, an allergy to [what] - buying a ticket and asking about a connection - “I don't understand,” “do you speak English?,” “I need help” - 3 phrases that are useful in [country] and that foreigners usually don't know At most 20 phrases, ordered by how often I'll use them. No table, a plain list stacked vertically so it fits on a phone.