China City Trip Planner
Overview
Build compact, city-aware travel plans by combining a shared planning core with a city-specific pack. Use the common rules for all cities, then load the matching city reference for local districts, food corridors, arts corridors, weather risks, and transit patterns.
City Selection
- Ask for the city if the user did not specify one.
- If the user asks for multiple cities, optimize each city separately and keep the handoff between cities explicit.
- Load references/common.md for shared planning rules.
- Load the matching city pack under references/cities/, such as references/cities/beijing.md, when the city is known.
- If a city pack is missing, use the shared core and say that the city-specific pack still needs to be added.
Template Selection
- Use the matching template directly when the user already names a scenario.
- If the user only gives trip length or a vague goal, pick the safest default:
- 1 day or first visit:
classic-first-visit - 2 days:
2-day - 3 days:
3-day - kids, elders, stroller, or slow pace:
family-friendly - rain, snow, haze, heat, or strong indoor preference:
rainy-day-backup - food-first request:
food-focused - theater, concerts, museums, or galleries:
arts-focused
- If multiple scenarios apply, choose the most restrictive one and say why in one sentence.
Planning Rules
- Keep each day anchored in one area.
- Prefer subway and walking. Use taxis or ride-hailing only when they clearly save time or solve luggage, late-night, or low-frequency transit problems.
- Avoid cross-city zigzags.
- For popular attractions, add security, queue, and reservation buffers.
- For date-specific plans, verify opening hours, reservation rules, closure days, and transport changes before finalizing.
- For family or slower trips, reduce stairs, transfers, and late-night moves.
- For first-time visitors, favor the classic route before niche detours.
- For food-focused plans, use ranking pages as discovery input, then pair meals with the day's anchor area unless the meal is the explicit destination.
- For arts-focused plans, use POI search and venue calendars, match the venue to the date, and leave buffer time before the performance start.
- For route feasibility, use route planning and weather data to decide whether a stop belongs in the same day.
- Treat ranking pages as discovery inputs, not as a guaranteed live API source.
Output Format
- Name the city and selected template first.
- State why it fits in one sentence.
- List the day-by-day plan in time order.
- For each day, include the theme, stops, transit, pace, one backup option, and any food or arts insertions.
- End with a short note on what needs live verification if the trip is date-specific.
Output Template
Use this structure for the final answer:
City: <city name>
Template: <classic-first-visit | family-friendly | 2-day | 3-day | rainy-day-backup | food-focused | arts-focused>
Why this fits: <one sentence>
Day 1
- Theme: <theme>
- Stops: <stop 1 -> stop 2 -> stop 3>
- Transit: <subway/walk/taxi plan>
- Pace: <fast / balanced / relaxed>
- Food: <meal or snack insertion, or "none">
- Arts: <venue insertion, or "none">
- Backup: <one fallback option>
Day 2
- Theme: <theme>
- Stops: <stop 1 -> stop 2 -> stop 3>
- Transit: <subway/walk/taxi plan>
- Pace: <fast / balanced / relaxed>
- Food: <meal or snack insertion, or "none">
- Arts: <venue insertion, or "none">
- Backup: <one fallback option>
Notes
- Live checks: <opening hours / reservation / weather / transit changes / performance dates / restaurant rules>
Reference Material
Use references/common.md for shared rules and references/cities/ for city packs.