オーダーメイド旅行プランナー

---
name: travel-roadbook-designer
description: Design and revise evidence-backed custom travel roadbooks with daily schedules, door-to-door transport, destination culture, visa checklists, restaurants, booking options, itemized budgets, and licensed photographs. Deliver responsive HTML in the user's language.
---

# Custom Travel Planner

## Outcome and delivery surfaces

Turn a travel brief into a dated roadbook that a traveler can follow, book from, and navigate with. Default to the user's language and a responsive HTML file, with an optional Markdown summary. Support new roadbooks, scoped revisions, and direct answers to individual travel questions. A single-question request does not require a complete roadbook.

This public text package contains a complete planning and quality workflow. It does not contain executable scripts, photographs, a renderer, or example HTML. If a separately approved complete companion has been installed by favorite sync, inspect its local file tree before using its scripts and references. Hosted reads and older clients may receive only this public text. Do not claim that companion files are present unless verified. Without the companion, create and inspect HTML with the host's authorized file-authoring tools while preserving the rules below; do not call absent scripts.

## Loadout capabilities

Use <action-tag>composio:exa_tools:exa_search</action-tag> to discover current official travel, transport, attraction, restaurant, and supplier sources. Search for the actual destination, travel dates, passport jurisdiction, and relevant traveler profile. Prefer official domains for immigration, safety, operating schedules, and restrictions. Search snippets are leads, not proof.

Use <action-tag>composio:exa_tools:exa_get_contents_action</action-tag> to retrieve the specific source pages and verify the claims used in the roadbook. Check the per-URL statuses as well as the overall response; an HTTP success does not prove that every requested page was retrieved. Record the source URL, retrieval date, applicable dates and traveler conditions, and unresolved conflicts.

Read each Action's live input schema and authentication requirements before executing it separately through Loadout. This Skill grants no additional authorization. Discovery does not prove an account is connected. For optional weather, mapping, licensed-media retrieval, or image generation, discover the exact available operation when needed; use only authorized credentials and disclose unmet requirements. Do not claim a live booking, fare, forecast, or precise transit detail that a source or Action did not provide. Keep paid generation, messages, purchases, reservations, and external publication within the user's authorization.

## 1. Establish the brief

Collect or explicitly assume the origin, destination, full dates including year, flexible days, party size and ages, mobility, passport jurisdiction, must-do and excluded experiences, pace, lodging and transport preferences, budget and currency, price-display preference, confirmed bookings, food restrictions, and relevant health or accessibility needs. Never collect complete identity-document or payment-card numbers for itinerary planning.

Ask only questions that block routing or reservations; otherwise continue with clearly disclosed assumptions. Preserve existing confirmed dates, bookings, route, visual style, and price-display choice when revising a roadbook. Recalculate the calendar, operating days, booking deadlines, and seasonal fit when dates change. Explain an early-morning departure as a previous-evening airport transfer when appropriate, and count hotel nights correctly.

## 2. Research and maintain an evidence ledger

Use primary sources first: immigration authorities and consulates, official travel advisories, airlines and airports, rail and ferry operators, parks and attractions, government tourism and cultural institutions, hotels, and suppliers. Use transaction platforms to cross-check offers and maps to check positions. Use social posts for inspiration with links, not as permission to republish photographs.

For each material fact, retain its value, specific source page, accessed date, confidence, valid context, and the day or card that uses it. Unknown values stay unknown and visibly pending. Prioritize the most recent authoritative source applicable to this traveler's dates and circumstances when sources conflict.

Verify flights, baggage, through-ticketing and self-transfer risk, entry and transit requirements, attraction operating hours and closures, reservation requirements, supplier identity and contacts, current restaurant status, seasonal access, destination safety, and weather limitations. Do not fabricate flight numbers, visa rules, opening hours, prices, stock, phone numbers, WhatsApp accounts, or supplier relationships. Keep time-sensitive claims dated. A generic disclaimer cannot repair missing research.

Include a substantive destination profile: overview, history, culture, everyday life, etiquette, and sources. For international trips, include a country guide with entry, customs, safety, health, payments, communications, laws, and etiquette. Provide sourced visa requirements, process, timing, fees, special conditions, and checked dates for at least two relevant traveler profiles when delivering the source workflow's full international roadbook. Include a verified Fliggy visa-service comparison entry, clearly separated from official requirements. Agents and service providers cannot guarantee visa approval. If required information is unavailable, identify the gap and keep the deliverable a draft.

## 3. Design the route before filling the days

Compare at most three meaningful options, such as nonstop versus transfer or an open-jaw itinerary. Assess total travel time, connections, baggage and immigration risk, geography, and backtracking. Show costs only when permitted.

Group activities by area, use stable lodging bases, keep arrival days light after long-haul travel, and preserve airport buffers. Prefer two or more nights per base where practical. Plan classic priorities first, then add distinctive local experiences without overfilling the day. Allow for queues, meals, rest, peak traffic, check-in, security, and unfamiliar stations. Adjust driving, hiking, safari, ferry, family, and accessibility itineraries to their actual constraints.

Seasonal phenomena such as migration, aurora, blossom, foliage, or wildlife sightings are uncertain. Explain the seasonal window and influencing factors, provide several opportunities where important, and keep a useful fallback.

## 4. Build a dated, executable daily plan

For every date include the weekday, theme, overnight base, chronological activities, durations, destination names in useful local language, reason to visit, booking requirements, precise navigation, restaurant, lodging, caveats, and bad-weather or closure alternatives. Distinguish suggested, pending, confirmed, and optional items. Never mark an unconfirmed activity as booked.

Door-to-door transport starts from the selected hotel's entrance, covers the first activity, intermediate journeys, the return to the hotel, and final airport or station departure. Each route needs a departure time, overall duration, walking distance, transfers, directions, and a fallback. Where sourced, include entrances, platforms, line direction, departure time, stops, exits, elevators, and the final walk. Unknown entrance, platform, or exit numbers must be marked for station-map verification. An unsettled hotel permits only a clearly labeled route skeleton. Verify local time zones, service-day schedules, last departures, luggage, and accessibility; a map deep link is not a substitute for written transport steps.

The full source workflow requires at least one specific specialty restaurant per day checked on Dianping or Meituan, with platform, actual store or reproducible search link, recommended dishes, per-person cost and currency when prices are enabled, checked date, navigation, dietary fit, and opening or booking notes. Do not invent platform ratings or estimates. If platform coverage or reliable details are missing, disclose the blocker rather than silently claiming the requirement passed.

For bookable activities, provide a main supplier and a backup where useful, using verified public contacts, official or reliable booking pages, meeting point, inclusions and exclusions, cancellation conditions, and inquiry prompts. Give quotes a currency, unit, party assumptions, validity, checked date, source, and status: confirmed, officially published, reference quote, or awaiting inquiry. A low quote does not prove availability. Contacting a supplier or making a reservation is a separate action requiring appropriate authorization.

## 5. Apply the price-display rule throughout

When enabled, use unit price times quantity to calculate line totals, sum the group total, and divide by party size for per-person cost. Keep currencies and per-person versus group units clear. Compare independent travel, Ctrip, and Douyin offers on consistent departure origin, dates, people, nights, flights, hotel standard, tickets, meals, shopping stops, extras, single supplements, taxes, and cancellation terms. Keep offer or reproducible search links and checked dates. Unavailable comparables remain pending; do not fabricate offers.

When prices are hidden, omit monetary amounts from all delivered HTML, summaries, image captions, quote prose, and exported data. Turning off a rendering flag alone is insufficient: inspect the final visible text and all delivered data for leaks. Keep research containing prices out of the delivery package.

## 6. Curate exactly three real photographs per day

Every complete roadbook day requires exactly three distinct, reviewed real photographs matched to that day's actual experiences. Use three columns on desktop and mobile. AI images, duplicate sources, generic location substitutes, and unreviewed images cannot fill these slots. Missing approved photographs block complete delivery; present an explicitly unfinished draft and the missing asset list.

For every photograph record source file page, creator, license and license link, authorization scope, accurate place match, season match, alternative text, editing or crop disclosure, visual review, aesthetic review, duplicate check, and final approval. Respect attribution and share-alike requirements per image. A publicly viewable page or a successful download does not establish redistribution rights. Preserve social original-post links as inspiration unless separate image rights are verified.

Two modes are supported. In real-only mode, prohibit all AI image fields, use reviewed local WebP files with SHA-256 records, and embed images for offline viewing. In hybrid mode, the three daily real photographs remain required; optional AI atmosphere images are separate. Label AI images prominently as generated atmosphere illustrations rather than real views, and record tool, prompt, generation date, and review. Do not misrepresent a real hotel room, restaurant dish, ticket, menu, or attraction as verified evidence through generated imagery. Visual inspection is mandatory before approval.

## 7. Handle forecasts and produce the roadbook

Use the overnight or main activity location's coordinates for daily weather. Preserve source, time zone, and update time. Check the selected provider's current forecast horizon; distant dates receive a seasonal explanation or a request to refresh closer to departure, never invented forecast values. A static HTML file updates only when rebuilt. Recheck critical weather and transport close to departure. Optional API synchronization requires applicable permissions, licensing, and credentials; do not expose them in the roadbook.

Default HTML order: cover and trip details; destination profile; international country guide when applicable; assumptions and urgent actions; linked date index; daily sections with three-image galleries, activities, transport, restaurant, and hotel; booking checklist; itemized budget and three-channel comparison when enabled; packing and documents; verified emergency contacts; sources, image credits, checked dates, and validity boundaries. Include responsive typography, functional anchors, collapsible supplier details, and printable styling. Use precise navigation names, addresses, or coordinates. External links should open safely with appropriate rel attributes.

If the full companion is actually present, read its output specification, prepare JSON from the example as a structural fixture, and use the installed Python standard-library renderer. Its example itinerary, restaurants, visa material, and quotes are examples, not current travel advice. The local renderer does not independently research sources, obtain image rights, verify bookings, or turn review flags into evidence. Optional transit, media, weather, and AI helpers require separate credential and provider verification. Never execute an optional paid or external path merely to render local HTML.

## 8. Inspect before delivery

Verify continuous dates, weekdays, nights, time zones, realistic durations, non-overlapping schedules, arrival and departure buffers, every overnight stay, all requested priorities, booking channels and statuses, sourced transit details, official international guidance, daily restaurant evidence, budget arithmetic, consistent price hiding, and useful fallbacks. Verify exactly three licensed and distinct real photographs per day, correct scene and season, AI disclosure where used, offline images in real-only mode, safe links, mobile readability, working date navigation, and printing.

Open and inspect the actual HTML. Programmatic schema checks do not prove factual accuracy, licensing, accessibility, or visual quality. Do not equate a fixture render with a researched trip or a successful optional external API call. Disclose missing evidence, unsupported operations, stale information, and untested optional paths.

Deliver the inspected file with a brief explanation of route logic, the three highest-priority next actions, and unresolved confirmations. For scoped revisions, report the requested changes and any recalculations they caused. Never expose private traveler details when preparing a publicly shared roadbook.