← ClaudeAtlas

travel-itinerary-plannerlisted

Plan realistic, delightful trips — day-by-day itineraries with geographic clustering, travel times, opening hours, budget ranges, bookings checklist, packing list, local etiquette and backup plans for bad weather. Use when someone asks to plan a trip, vacation, honeymoon, business trip, weekend getaway or multi-city route.
RaveenDi/Skilloadout · ★ 0 · AI & Automation · score 78
Install: claude install-skill RaveenDi/Skilloadout
# Travel Itinerary Planner Great itineraries feel effortless because the hard constraints were handled up front. Work in this order: **constraints → skeleton → days → logistics → polish.** ## 1. Collect constraints (ask only what's missing) Dates & flexibility · origin · travelers (ages, mobility, kids) · budget level (shoestring / mid / luxury, and currency) · pace (relaxed ≈ 2 anchors/day, active ≈ 3–4) · interests (top 3) · must-sees / must-avoid · accommodation style · dietary needs · visa/passport situation. If the user gave little detail, pick sensible defaults and state them in one line. ## 2. Skeleton - Decide **bases** (where to sleep) first: minimize hotel changes; ≥ 2 nights per base unless it's a road trip. - Allocate days per base by interest density; add a **buffer day** for trips > 7 days. - Order cities to avoid backtracking; note transfer mode + duration between bases (train/flight/drive). ## 3. Day design rules - **Cluster by neighborhood** — each day lives in 1–2 adjacent areas; never cross the city twice. - One **anchor** in the morning (best light, fewer crowds), one in the afternoon, a flexible evening. - Check **opening days/hours** (museums often close Mondays/Tuesdays) and flag anything needing advance tickets. - Put jet-lag-friendly, low-commitment plans on arrival day; nothing unmissable on the last morning. - Meals: suggest *areas or types* of places plus 1–2 well-known examples; mark reservations-needed. - Always include a **rain / low-ener