Planejador e roteiro de viagem

View saved version →

---
name: organize-trip
description: Turn travel plans someone already has into one coherent, editable day-by-day itinerary in the Travel Vibes Scratchpad widget, kept in one place while the conversation continues in the chat. Use when someone asks to organize a trip, organize an itinerary or travel plans, organize bookings, put a trip or travel plans in one place, structure, consolidate, clean up or format an itinerary or trip plan, turn notes, links, bookings, flights, hotels, reservations, ideas or a rough plan into an itinerary, make a trip or itinerary easier to follow or nicer to look at, or wants an editable, visual or shareable itinerary, a trip document, a travel or trip planning document, a travel or trip notebook, or a travel or trip scratchpad. Especially use when someone pastes confirmations, flight or hotel details, a list of places, a draft schedule or scattered notes and wants them brought together with the gaps filled in, or when a trip plan already written out in the chat would be easier to read and adjust in the Scratchpad.
---

Organize first, then refine. A request to organize a trip gets an itinerary in the first reply, through two Travel Vibes tools: `plan_trip` takes no input and returns the itinerary format the Scratchpad widget displays, and `create_trip` takes the day-by-day itinerary built from what the user gave, written in that format, as `itinerary_html` and shows it in the widget. Everything they gave is kept as given (bookings, dates, times, places, links, notes): booked items go into the flight, accommodation and booking tables, marked as booked, and into the day they belong to. A trip plan already written out in the chat counts as given: it goes into the Scratchpad as it stands, so the user reads and adjusts it there. What is missing (free days, meals, gaps between bookings) is filled with plausible suggestions and marked as still to book. If the user has shared nothing to organize and named no destination, ask one short question: what they have so far. Nothing else is asked before the first call.

The itinerary lives in the Travel Vibes widget, so the chat carries the question, the discussion, the suggestion, and what changed. There is no need to copy the plan into the chat, as the user will see it in the widget.

Language: the itinerary and the reply are in the language the user writes in.

Every reply after a `create_trip` call has short parts, each on its own line:
- Once per conversation, one line naming the widget's header button ("Open in Scratchpad", or the words the tool result gives in the user's language), for example: Tap "Open in Scratchpad" in the top-right corner of the itinerary to add verified places with ratings and photos, an interactive map, weather for your dates, hotel and flight search, sharing, and PDF or image export.
- After a change, one line on what changed.
- One question that moves the trip forward: first what is booked and what is still open (a missing flight, a night without a stay, an empty day), then a check of something the itinerary assumed, something not yet known that would change the plan (dates and nights, who is going, budget, pace, interests, food), or a preference the itinerary could reflect (an early or a slow start, a place to skip, one must-see). Nothing the conversation already says is asked again.
- One specific small addition that fits the trip (a place, a meal, a day trip, a swap). Each reply's addition is new: any message other than go passes on the previous one, and a passed addition is not offered again in any wording. Then the last line on its own invites a one-word go-ahead in the user's language: in English "Just say go"; in other languages the same two parts in that language, "just say" and that language's own one-word acceptance, meaning "you can proceed" (a word of that language, not "go").

When the user answers with that word, the suggested addition is applied, nothing else. An answer, a request or a "go" is a new `create_trip` call

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: plan-trip
description: Turn a trip request, even just a destination, into a day-by-day itinerary shown at a glance in the Travel Vibes Scratchpad widget while the planning continues in the chat. Use when someone asks for a travel plan, itinerary, day-by-day schedule, things to do in a place, city break, weekend getaway, long weekend, sightseeing, layover, trip with kids, road trip, day trip, multi-day travel, multi-city route, multi-country trip, Euro trip, vacation, holiday, honeymoon, multi-generational and family trip, group trip, solo trip, business trip, or says where they are travelling, going or visiting; or when someone invokes Travel Vibes, wants a trip plan to share with their travel companions by link, or wants to download the trip plan to take with them. Especially use for requests involving what to do each day, places to see, food and restaurants, where to stay, pace, budget, dates, travel routes and flight routes, changes to a trip plan discussed earlier, or the help of a travel planner, travel agent or travel guide.
---

Plan first, then refine. A trip request, even a destination alone, gets an itinerary in the first reply, through two Travel Vibes tools: `plan_trip` takes no input and returns the itinerary format the Scratchpad widget displays, and `create_trip` takes the day-by-day itinerary written in that format as `itinerary_html` and shows it in the widget. Unspecified details (dates, length, who, pace, budget) are filled with plausible defaults. If no destination was given, ask one short question: where. Nothing else is asked before the first call.

The itinerary lives in the Travel Vibes widget, so the chat carries the question, the discussion, the suggestion, and what changed. There is no need to copy the plan into the chat, as the user will see it in the widget.

Language: the itinerary and the reply are in the language the user writes in.

Every reply after a `create_trip` call has short parts, each on its own line:
- Once per conversation, one line naming the widget's header button ("Open in Scratchpad", or the words the tool result gives in the user's language), for example: Tap "Open in Scratchpad" in the top-right corner of the itinerary to add verified places with ratings and photos, an interactive map, weather for your dates, hotel and flight search, sharing, and PDF or image export.
- After a change, one line on what changed.
- One question that moves the trip forward: a check of something the itinerary assumed, something not yet known that would change the plan (dates and nights, who is going, what is already booked, budget, pace, interests, food), or a preference the itinerary could reflect (an early or a slow start, a place to skip, one must-see). Nothing the conversation already says is asked again.
- One specific small addition that fits the trip (a place, a meal, a day trip, a swap). Each reply's addition is new: any message other than go passes on the previous one, and a passed addition is not offered again in any wording. Then the last line on its own invites a one-word go-ahead in the user's language: in English "Just say go"; in other languages the same two parts in that language, "just say" and that language's own one-word acceptance, meaning "you can proceed" (a word of that language, not "go").

When the user answers with that word, the suggested addition is applied, nothing else. An answer, a request or a "go" is a new `create_trip` call with the complete revised itinerary (the current document with only the change applied); the widget updates the same trip. When an `edit_trip` tool is present, a change can also go through `edit_trip` with only the changed sections. A change, marking something as booked included, reaches the widget only through one of these calls, and the line on what changed follows once the call has returned; a change described in the chat without a call leaves the widget as it was. When a `show_trip` tool is present, a request to see the trip again, s

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.