Skip to content

skywain/trip-planner-skill

trip-planner

Unverified

End-to-end international trip planning: turns "I want to go to X for N days" into a verified, bookable plan — route skeleton across cities, flight price scans (international + domestic legs), train-vs-fly decisions, hour-by-hour daily timelines with opening hours, dwell times, holiday collisions and tappable turn-by-turn map links (小时级行程+地图导航+离线KML), hotel shortlists by neighborhood, budget rollup, and a booking checklist with deep links. Use this whenever the user asks to plan a trip, vacation, itinerary or honeymoon, compare flight dates/prices, pick between cities or routes, schedule a travel day hour by hour, fill a spare block of time ("I'm near X with 2 free hours"), turn a finished plan into a designed page (eight themed renders: illustrated / clay / noir / glass / journal / zine / splash / portal — 插画/黏土/夜航/玻璃/手账/Zine/闪屏/穿越版), or asks 旅行规划/行程安排/机票比价/去某国玩N天怎么安排/现在有空档干嘛/把行程做成好看的网页 — even if they only mention one piece (just flights, just hotels, or just navigation), the playbook and verification rules here still apply.

FileKindSize
SKILL.mdskill md32.9 KB
assets/plan.example.jsonconfig12.1 KB
examples/README.mdmarkdown13.0 KB
examples/china-2026/china-splash.htmlother937.1 KB
examples/china-2026/china.art.jsonconfig6.4 KB
examples/china-2026/china.geo.jsonconfig58.3 KB
examples/fixtures/bad/bracketed-note.geo.jsonconfig7.8 KB
examples/fixtures/bad/brief-card-not-text.geo.jsonconfig943 B
examples/fixtures/bad/decision-point-date-two-days-before.geo.jsonconfig848 B
examples/fixtures/bad/decision-point-day-date-not-iso.geo.jsonconfig7.8 KB
examples/fixtures/bad/decision-point-no-if-no.geo.jsonconfig715 B
examples/fixtures/bad/decision-point-same-what.geo.jsonconfig8.2 KB
examples/fixtures/bad/decision-point-src-not-http.geo.jsonconfig803 B
examples/fixtures/bad/decision-point-t-not-hhmm.geo.jsonconfig764 B
examples/fixtures/bad/decision-points-null.geo.jsonconfig594 B
examples/fixtures/bad/driver-enum.geo.jsonconfig711 B
examples/fixtures/bad/driver-self-no-driving-card.geo.jsonconfig736 B
examples/fixtures/bad/driving-card-no-as-of.geo.jsonconfig861 B
examples/fixtures/bad/driving-card-no-desk.geo.jsonconfig800 B
examples/fixtures/bad/driving-card-no-legality-line.geo.jsonconfig811 B
examples/fixtures/bad/driving-card-no-verdict.geo.jsonconfig939 B
examples/fixtures/bad/driving-card-zh-verdict-trailing.geo.jsonconfig967 B
examples/fixtures/bad/hotel-checkout-null.geo.jsonconfig786 B
examples/fixtures/bad/hours-as-of-not-date.geo.jsonconfig674 B
examples/fixtures/bad/hours-bare-string.geo.jsonconfig655 B
examples/fixtures/bad/hours-src-not-http.geo.jsonconfig662 B
examples/fixtures/bad/hours-text-empty.geo.jsonconfig647 B
examples/fixtures/bad/kind-enum.geo.jsonconfig7.9 KB
examples/fixtures/bad/must-false.geo.jsonconfig914 B
examples/fixtures/bad/must-no-stand.geo.jsonconfig755 B
examples/fixtures/bad/must-no-view.geo.jsonconfig758 B
examples/fixtures/bad/must-not-boolean.geo.jsonconfig798 B
examples/fixtures/bad/must-see-unmatched.geo.jsonconfig963 B
examples/fixtures/bad/must-see-view-empty.geo.jsonconfig910 B
examples/fixtures/bad/pending-no-checklist-row.geo.jsonconfig1021 B
examples/fixtures/bad/refundable-not-boolean.geo.jsonconfig686 B
examples/fixtures/bad/rental-leg-no-driving-card.geo.jsonconfig829 B
examples/fixtures/bad/review-counts-disagree.geo.jsonconfig1.0 KB
examples/fixtures/bad/review-lens-enum.geo.jsonconfig1.1 KB
examples/fixtures/bad/review-no-driving-lens.geo.jsonconfig1.3 KB
examples/fixtures/bad/review-not-object.geo.jsonconfig611 B
examples/fixtures/bad/review-single-pass-with-counts.geo.jsonconfig1.0 KB
examples/fixtures/bad/review-two-lenses.geo.jsonconfig959 B
examples/fixtures/bad/self-drive-no-driving-card.geo.jsonconfig635 B
examples/fixtures/bad/sub-stop-no-name.geo.jsonconfig763 B
examples/fixtures/bad/sub-stop-no-query.geo.jsonconfig763 B
examples/fixtures/bad/sub-stops-null.geo.jsonconfig578 B
examples/fixtures/bad/tour-confirmed-prefix.geo.jsonconfig902 B
examples/fixtures/bad/tour-not-boolean.geo.jsonconfig562 B
examples/fixtures/bad/tour-on-day-object.geo.jsonconfig7.8 KB
examples/fixtures/bad/tour-unconfirmed.geo.jsonconfig837 B
examples/fixtures/strict/clean.plan.geo.jsonconfig4.5 KB
examples/fixtures/strict/hours-as-of-after-asof.geo.jsonconfig4.1 KB
examples/fixtures/strict/hours-missing-in-window.geo.jsonconfig4.0 KB
examples/fixtures/strict/hours-stale-as-of.geo.jsonconfig4.1 KB
examples/fixtures/strict/no-generated.geo.jsonconfig3.8 KB
examples/fixtures/strict/refundable-no-clause.geo.jsonconfig3.8 KB
examples/fixtures/strict/rows-without-clock-or-kind.geo.jsonconfig3.7 KB
examples/fixtures/strict/self-drive-not-legal-no-decision.geo.jsonconfig4.4 KB
examples/fixtures/strict/t-n-date-mismatch.geo.jsonconfig3.8 KB
examples/fixtures/strict/tour-no-review.geo.jsonconfig3.4 KB
examples/fixtures/substops.plan.geo.jsonconfig9.1 KB
examples/gates-sample.icsother11.5 KB
examples/japan-2026/japan-illustrated.htmlother1.4 MB
examples/japan-2026/japan.art.jsonconfig6.2 KB
examples/japan-2026/japan.geo.jsonconfig65.5 KB
examples/kyoto-sample.htmlother13.0 KB
examples/kyoto-sample.kmlother1012 B
examples/kyoto-sample.plan.geo.jsonconfig7.2 KB
examples/mexico-2026/mexico-journal.htmlother2.0 MB
examples/mexico-2026/mexico.art.jsonconfig9.4 KB
examples/mexico-2026/mexico.geo.jsonconfig77.1 KB
examples/morocco-2026/morocco-glass.htmlother1.3 MB
examples/morocco-2026/morocco-portal.htmlother13.8 KB
examples/morocco-2026/morocco.art.jsonconfig3.8 KB
examples/morocco-2026/morocco.geo.jsonconfig85.1 KB
examples/nordic-2026/nordic-noir.htmlother686.8 KB
examples/nordic-2026/nordic.art.jsonconfig8.7 KB
examples/nordic-2026/nordic.geo.jsonconfig58.5 KB
examples/turkey-2026/turkey-clay.htmlother1.3 MB
examples/turkey-2026/turkey.art.jsonconfig3.5 KB
examples/turkey-2026/turkey.geo.jsonconfig75.8 KB
examples/vietnam-2026/vietnam-zine.htmlother2.5 MB
examples/vietnam-2026/vietnam.art.jsonconfig10.8 KB
examples/vietnam-2026/vietnam.geo.jsonconfig85.1 KB
references/art-schema.mdmarkdown318 B
references/country-quick-notes.mdmarkdown58.6 KB
references/cover-titles.mdmarkdown10.6 KB
references/data-sources.mdmarkdown49.2 KB
references/navigation.mdmarkdown23.6 KB
references/output-template.mdmarkdown49.2 KB
references/phase-0-intake.mdmarkdown12.4 KB
references/phase-1-brief.mdmarkdown22.8 KB
references/phase-3-legs.mdmarkdown10.5 KB
references/phase-4-days.mdmarkdown13.6 KB
references/phase-6-assemble.mdmarkdown22.3 KB
references/scheduling.mdmarkdown28.8 KB
references/themes.mdmarkdown37.9 KB
scripts/build_site.pyscript47.8 KB
scripts/flight_scan.pyscript18.9 KB
scripts/plan_lint.pyscript58.4 KB
scripts/render_plan.pyscript28.2 KB
scripts/route_tools.pyscript90.0 KB

references/phase-1-brief.md

View on GitHub
# Phase 1 — Country brief (the procedure)

Read this at the start of Phase 1, before any fact about the destination is written.
SKILL.md Phase 1 is the contract — inputs, outputs, and the gates that decide pass/fail;
this file is the whole procedure it points at. Every line here ends up in a `brief`
card (output-template.md §Brief templates, canonical order) or a checklist row, and
every line carries its source and as-of date.

Inputs: destination(s) and dates, the traveller's passport and origin (`prefs`,
`meta.party`), `prefs.drivers` when a self-drive option exists, the route skeleton
candidates. Outputs: the `brief` cards — visa · emergency · safety · health · holidays ·
weather · money · connectivity · insurance (+ season and driving when triggered —
inserted after `baggage`, output-template.md §Brief templates order) — the Phase 1
checklist rows (visa lead time, arrival registration, travel-clinic consult,
yellow-fever vaccine + ICVP, insurance, hazard gate, copies + registration), and
the facts every later phase inherits and no city agent may overrule.

## Where the facts come from

Read the destination's section of references/country-quick-notes.md first. **Destination
not in that file (Mexico, Morocco, Turkey and Vietnam all weren't)** → work through its
"Destination not listed? — the checklist" section instead of improvising: it is the
list of things every new country costs a first planner 6-9 searches to rediscover.

**Then read how travellers who share the user's language do this destination** — one
budgeted search (Hard rule 4) on the platform where that community posts
(mainland-China travellers: Xiaohongshu 小红书 / Mafengwo 马蜂窝 / Qyer 穷游; otherwise
that language's largest travel forum — platform list: data-sources.md §Traveller consensus). It is evidence for the trip's **shape** — self-drive
or tour, where to sleep, which viewpoint is the point of going, what disappoints — never
for prices, hours or rules (Hard rule 2). One `decisions[]` row records the consensus
and its source; a platform that cannot be read (login wall, no browser pane) is written
"community consensus not checked", never guessed from memory. Where it disagrees with the
default you were about to take, both go to the user at checkpoint (a) — headless: into
the assumptions block — and the user chooses.

## The fact lines (visa · holidays · events · weather · money · insurance · safety)

- **Visa/entry** for that passport: official government/embassy sources only; put the
  processing lead time on the booking checklist. Rules change — never answer from memory.
  Read the conditions printed on a multiple-entry visa, not only its validity (a
  first-entry condition says where or how the first entry must be made), and any
  digital arrival registration the entry country runs before landing — that gets its
  own checklist row with the official link; the traveller fills it in (Hard rule 1).
  Transit countries count too: a separate-ticket connection can force ENTERING the hub
  country to re-check bags (references/phase-3-legs.md §International, the separate-tickets
  bullet) — run
  that audit here, before writing "no visa needed" anywhere.
  **This judgement is the assembler's alone**: city subagents (Phase 4) do not make
  visa/entry calls, and anything they say about it is overwritten by this line.
- **Holidays colliding with the window**:
  `curl -s "https://date.nager.at/api/v3/PublicHolidays/{year}/{ISO2}"` (keyless ✓).
  A national holiday means closures + crowds + hotel spikes — annotate affected days.
- **What the holiday API can't see** — one budgeted search per city
  (`{city} festival OR events {month} {year}`) plus, where relevant: seasonal
  operating windows for mountain/garden/boat anchors, per-venue annual maintenance
  shutdowns of headliners, and Ramadan dates in Muslim-majority destinations (daytime
  food logistics, shifted hours, packed evenings). A local festival closes streets and
  triples hotel rates while every holiday feed says the day is ordinary.
- **User-named events get verified before anything else is planned.** A match,
  concert or festival in the request is the hardest pin in the whole trip — confirm
  team/venue/city, date, local kickoff time and ticket on-sale status FIRST, because
  the skeleton hangs off it ("Columbus vs Miami" is a home game in Ohio, and a route
  built around the wrong coast is a 13-day bug). US listings put the home side first
  in "A vs B" — but verify, never parse. Kickoff times can move for TV ⚡: re-check
  close to travel.
- **Weather for those dates**: Open-Meteo recipes in data-sources.md (first call can
  take ~10 s). One line: temps, rain odds, daylight — stamped with its mode
  (forecast / 5-yr normals + climate model) and as-of date per data-sources.md
  §Weather; the Phase 6 exit criteria check the stamp.
- **Money & connectivity — fixed lines, not a vibe.** `brief.money` carries the five
  lines of output-template.md §Brief templates (refuse DCC · card FX fee → buffer ·
  ATM rule · cash number · which cards and wallets work) plus the **origin-conditional
  block** when it applies (mainland-China origin: UnionPay vs Visa/MC acceptance,
  Alipay+/WeChat coverage, foreign-cash pre-order); `brief.connectivity` opens with the
  **handset line** — every phone in the party by model and market variant, and whether
  each takes an eSIM, a physical SIM or both (variants differ: some markets' models
  have no eSIM, some have no SIM tray); models unknown → the pick per hardware type,
  and the assumptions block asks for the models. Then the eSIM ballpark — a voice- and
  SMS-capable local number, not data only, where operators, tours or small hotels confirm
  by phone; and whether the eSIM only activates once in the country (install at home,
  activate on landing) — then plug type and the digital-safety line (home-number SMS 2FA
  reachable abroad, phone-theft plan, cloud + offline copies of passport / visa / policy)
  — and, only when the traveller wants to keep the local number after the trip, the
  keep-alive line last (output-template.md §Brief templates, `brief.connectivity`).
  Recipes and thresholds: data-sources.md §FX → Money safety.
- **Insurance line**: travel-medical insurance with destination-appropriate coverage
  goes on the checklist (US target: ≥$100k medical + medical evacuation — an ER visit
  is four figures before insurance). Tours never substitute for it. When the plan
  carries a monitored hazard gate, the insurance row's deadline is NOW, not "before
  departure" (the user buys — Hard rule 1); the agent's jobs are the read-side ones:
  verify the issued policy rather than the product page, and match the plan's
  activities against the exclusion list by name — data-sources.md §Travel insurance.
  The local half of the operating card (emergency numbers, the ER per base, the
  assistance line) lives in `brief.emergency` — §Emergency card below.
- **Driving licence, whenever a self-drive option exists** — `brief.driving`, written
  before any skeleton recommends a car: legality first, rentability second (§Driving
  card below).
- **Advisory line, emergency card, health line, hazard line** — four procedures of
  their own below (§Advisory line, §Emergency card, §Health line, §Hazard line). All
  four draw only on official pages (the traveller's foreign-ministry advisory, CDC /
  TravelHealthPro, WHO, the insurer's schedule) — never from memory; a fact the fetched
  page does not carry → "n/a — see advisory" + that page's URL and as-of in the card,
  not silence — and never before the page was actually read.
- **Safety, written to the `brief.safety` template** (output-template.md §Brief
  templates — six named lines: the destination's named scams · pickpocket hotspots ·
  the taxi rule · the after-dark avoid list per base · what to do when it happens ·
  legal & customs red lines, medicines in luggage included — country-quick-notes.md
  §Medicines in luggage). More useful than warnings: design the plan so night
  movement is door-to-door by car — a route that never needs a dark walk beats a
  list of cautions. **A saving never buys down a safety or legality margin**: an option
  cheaper only because it drops a buffer, a lit route, a booked ride back or a valid
  licence is never the default. Sources: country-quick-notes.md (the destination's
  section, or the "Street safety" line of the not-listed checklist).

## Advisory line — level · source · date, line 0 of `brief.safety`

1. **Primary source = the traveller's passport**, always cross-checked with one second
   source (US or UK — both are keyless JSON, data-sources.md §Travel advisory): mainland
   China → 中国领事服务网 旅行风险等级 + 安全提醒 (browser pane); US → State Department
   advisories API; UK → gov.uk foreign-travel-advice API; Australia → Smartraveller;
   any other passport → its own foreign ministry in the browser pane. Two sources that
   disagree on level → the stricter one drives the plan and the disagreement goes into
   `unverified`.
2. **Level drives the plan.** "Do not travel" / US Level 4 / UK "avoid all travel" /
   CN 暂勿前往 on any base, leg or day trip → stop the pipeline and ask the user
   (Interaction contract moment 0 or a); Level 3 / "avoid all but essential" → the user
   decides with the line in front of them; a regional status ("… to parts of") → check
   every base, intercity leg and day trip against the named areas — a hit moves the
   base or asks.
3. **Write it** as line 0 of `brief.safety`: `advisory: {level} · {source} · as-of
   {date} (second source: {level})`. The T-14 and T-3 rows of the pre-departure ladder
   re-read both sources (output-template.md §Pre-departure re-check ladder).
4. The advisory page's "Safety and security", "Local laws and customs", "Health" and
   "Getting help" sections are the sources for `brief.safety` lines 1-6,
   a cross-check of `brief.health` lines 2-4, and `brief.emergency` lines 1-3 — one
   read feeds three cards.

## Emergency card — `brief.emergency`, six lines

Every number comes from the advisory page's "Getting help" / emergency section, the
mission's own site or the insurer's schedule, stamped as-of; none from memory.
1. Local emergency numbers: police · ambulance · fire — copied from the advisory page's
   "Getting help" section and stamped as-of (the familiar ones — 112 / 911 / 110 — are
   still copied and stamped from the page, never typed from memory).
2. The home consular hotline: CN 12308 / +86-10-12308 · US +1-202-501-4444 · UK +44 20
   7008 5000 · AU +61 2 6261 3305 (all four verified 2026-09-03) — printed with
   "verify at link" + the ministry page's URL; the T-14 row re-reads it.
3. The nearest mission per base: name · address · phone · office hours · link.
4. Insurer assistance line + policy-number placeholder + the first-call rule
   (approval-first clauses; hospital ER over storefront clinics; itemised bill;
   police report within the policy's window) — data-sources.md §Travel insurance.
5. Lost passport: police report first (keep the receipt) → nearest mission for an
   emergency travel document (photos + copies + the report) → the destination's
   exit-record rule before flying out ⚡.
6. Per base: one 24-hour ER with an international department (name · address · map
   link, from the browser Google Maps place card — no search budget) and the local word
   for pharmacy + one near the hotel. A base more than 2 h from an ER (desert camp,
   fjord, park lodge) gets that fact in the day note and the insurer's medical-transport
   clause checked against it.
Checklist rows this card adds: "copies ×2 (passport / visa / policy / tickets) + cloud
copies + 2 passport photos" (before departure) and the trip-registration row by
passport (中国领事 APP 出行登记 · US STEP · Smartraveller subscription — the user
registers in their own app / account; the plan lists the row and the official link,
Hard rule 1).

## Health line — `brief.health`, and the yellow-fever audit

One WebFetch per destination — not a search — of the CDC destination page (static,
sections Travel Health Notices · Vaccines and Medicines · Non-Vaccine-Preventable
Diseases · Stay Healthy and Safe · Packing List) or the TravelHealthPro country page;
zh plans also cite the 海关总署 / 国际旅行卫生保健中心 health notice as the user-facing
pointer (recipes: data-sources.md §Travel health). Five lines:
1. Vaccines and prophylaxis: the page's "recommended for most / some travellers" rows,
   copied, plus activity tags from the route (rural nights, hiking, animal contact,
   altitude) → one checklist row **"travel-clinic consult (vaccines / prophylaxis)"**,
   deadline departure − 4 to 6 weeks — or NOW when departure is already inside 6 weeks
   (the row then says "book this week; a late series may not cover the whole trip"), its
   note = that agenda; the row sorts second in the booking checklist, right after visa
   (output-template.md §Final deliverable item 3). The plan writes the consult
   date and the agenda; it never doses or prescribes (country-quick-notes.md §Travel
   clinic) — the Diamox rule generalised.
2. Vector-borne diseases present and their season (dengue, malaria, Japanese
   encephalitis, chikungunya, tick-borne …): name + months. Where the line names a
   mosquito-borne disease, dusk blocks in wetlands, paddies, forest or river boats
   carry the repellent note once per base — not on every row.
3. Water and food: tap water drinkable / bottled only · ice caution · raw and street
   food line, from "Eat and drink safely"; on bottled-water destinations the first
   street-food meal block of each base carries "hot cooked food, no raw, no ice" once.
4. Rabies and animals: the page's rabies line + "no touching dogs / monkeys / bats;
   any bite → wash 15 min → ER the same day".
5. Notice level + as-of (CDC Travel Health Notice level, or "none"), and the page URL.
**Yellow-fever certificate audit** — an entry document, run with the visa audit. The
inputs are the **departure country, every transit airport and every entry country** —
the passport is irrelevant to yellow fever (a Chinese passport flying GRU → NBO: Brazil
is a WHO risk country and Kenya requires the ICVP from anyone arriving from one → the
row must exist). For each of them read WHO Annex 1 (data-sources.md §Travel health): is
it a risk country, and does it require the certificate from travellers arriving from one (the transit footnotes: > 12 h / > 4 h / any duration / > 24 h in
Brazil-Bolivia-Peru-Venezuela — read the footnote per country). Any hit → checklist row
"yellow-fever vaccine + ICVP" (小黄本), deadline departure − 10 days −
clinic lead time (the certificate is valid 10 days after the jab, for life since 2016;
mainland China vaccinates only at ITHC clinics); that date already passed → stop and
ask before the skeleton is fixed — the certificate cannot be back-dated and the entry
country can refuse boarding.

## Hazard line — the season card and the hazard gate

1. **Season table first**: country-quick-notes.md §Hazard seasons — does the travel
   window intersect a typhoon / hurricane / monsoon / wildfire / heat / avalanche season,
   or sit on a volcano or earthquake exposure? Then the live feeds (data-sources.md
   §Hazard feeds: GDACS, USGS, NOAA NHC; JMA / BoM / CWA in the browser pane) — is
   anything active on the route now?
2. **A hit produces four things**: the `brief.season` card (hazard · months · official
   source URL · what the plan does about it, ≤ 5 lines); a **hazard gate** — the
   official source URL and the decision it gates (cancel / reroute / swap the island
   day) as **one named checklist row beside the ladder — not folded into T-14 / T-7 /
   T-3** (the T-7 row only re-reads the season card), deadline = the exposed booking's
   free-cancellation cutoff or the official forecast horizon, whichever is earlier, with
   its own `.ics` VEVENT every time; the insurance row's deadline set to NOW (data-sources.md
   §Travel insurance "buy before the world moves"); every exposed booking (ferry, island
   day, mountain hut, park lodge, balloon) kept refundable until the gate, and one
   buffer day when the window sits on the season's peak.
3. Volcano and aurora days keep the base-rate rule of Phase 4 (phase-4-days.md): plan
   the day to work without the phenomenon; the official forecast horizon sets the gate.
4. No hit → no card, no `unverified` line, no prose: silence is correct here; the exit
   criteria only ask that the table was consulted.

## Driving card — `brief.driving`, legality before rentability (triggered)

Triggered whenever a self-drive option exists for any segment — a rental leg in any
skeleton candidate, or a car-first segment priced as a pair; absent otherwise. In the
plan, **a self-drive option exists** when any of four holds (the one prose list — the
card gate and the independent-review trigger key on it): `prefs.travel_style` is
`self-drive` or `mixed` · `prefs.drivers` is set · a `legs[]` row is a rental · a stop
carries `driver: self`. `plan_lint.py` FAILs a plan with no card when one holds.
Whether the law lets this licence drive here and whether a rental desk hands over keys
are separate questions: a clean rental confirmation proves nothing about legality. One line per jurisdiction driven — licensing is sub-national in some
countries (US states, Canadian provinces, Australian states), so a multi-state route has
several — and each driver in `prefs.drivers` is checked by the licence's issuing
country, not the passport. Each line takes one labelled form, in the plan language, so
the lint can read it (as it reads `brief.safety`'s `advisory:` line):
`{jurisdiction} · {licence country} licence — legality: {verdict} · desks: {brand policy, …} · {source} · as of YYYY-MM`
(zh: `{辖区} · {签发国}驾照 — 合法性:{结论} · 租车柜台:{…} · {来源} · 截至 YYYY-MM`).
`plan_lint.py` reads every line that carries the legality label and FAILs one with no
verdict from step 1 right after the label (followed by ` ·` or the end of the line; after
a zh label the English enum word is accepted too),
no desk part after the verdict or no as-of stamp, and a card
with no legality line at all; it WARNs when no line of the card carries an insurance
word (step 3).
1. **Legality** — the verdict, one of `legal` · `legal with IDP` · `legal with official
   translation` · `not legal` · `unverified` (zh: 合法 · 持 IDP 合法 · 持官方翻译件合法 ·
   不合法 · 未核实), with source + as-of ⚡. Sources: the jurisdiction's transport authority
   or statute (it decides); the traveller's own foreign-ministry or consulate notice
   for that jurisdiction (a cross-check); which road-traffic convention each side is
   party to (1949 Geneva, 1968 Vienna, both or neither) — an IDP counts only under a
   convention the jurisdiction applies, and a licence from a country party to neither
   has no IDP to fall back on. Two sources that disagree → the stricter reading goes on
   the card and the disagreement into `unverified`.
2. **Rentability** — the line's desk part: each candidate brand's published licence
   policy for that licence (IDP required · official translation accepted · not
   accepted) + as-of ⚡. Where to read the brands' terms: data-sources.md §Car rental;
   a dated US reading: country-quick-notes.md §USA.
3. **Insurance, stated once on the card**: rental damage waivers and travel policies
   normally require a licence valid where the car is driven — quote the clause from the
   brand's terms and the issued policy; with legality `not legal`, a stop can mean a
   criminal charge (copy the jurisdiction's penalty, dated ⚡) and an accident a refused
   claim.
4. **Verdict**: `not legal` or `unverified` → the plan does not recommend self-drive
   there; the guided or transit option is priced beside it (phase-3-legs.md §Driving
   legs) and both columns are shown to the traveller, who may still choose to drive.
   That choice, named as self-drive / 自驾, and its source go into `decisions[]` (risk stated once — SKILL.md
   Interaction contract). A self-drive wish stated in the request was voiced before
   this fact and is not that choice: headless, the days are built on the legal option
   and the assumptions block shows the self-drive column beside it.
5. **Rules that differ from home** (optional, not gated): one line for the whole card,
   from the jurisdiction's driver handbook ⚡ — whichever of turn on red, all-way stops,
   stopped school buses and roundabout priority differ from the licence's home rules
   (a dated US reading: country-quick-notes.md §USA).
(live case: a US state that recognises only 1949 Geneva Convention licences while the
major rental desks there rent to holders of other licences ⚡ — country-quick-notes.md
§USA.)

## Exit criteria — tick every line before Phase 2

- [ ] `brief` cards present in canonical order — visa · emergency · safety (line 0 =
      advisory) · health · holidays · weather (mode + as-of) · money · connectivity ·
      insurance · baggage (+ season when the window hits and driving when a self-drive
      option exists, after `baggage`) — every line
      with source + as-of, no
      line from memory, every absent fact written "n/a — see advisory" beside the URL +
      as-of of the page read for it (an "n/a" with no page read behind it is a fail).
- [ ] The visa audit covered every entry country and transit airport; the yellow-fever
      audit covered the departure country, every transit airport and every entry country
      (passport irrelevant).
- [ ] No base, leg or day trip inside a "do not travel" or regional-avoid area; a
      Level-4 hit stopped the pipeline and asked.
- [ ] Checklist rows: visa lead time · arrival registration (when the entry country
      runs one) · travel-clinic consult (when the health page
      recommends any vaccine or prophylaxis) · yellow-fever vaccine + ICVP (when the
      audit hits) · insurance (deadline NOW if a hazard gate exists) · hazard gate (when
      exposed) · copies + registration.
- [ ] User-named events verified: venue, date, local kickoff time, on-sale status.
- [ ] §Hazard seasons was consulted for the window, whether or not it hit.
- [ ] When a self-drive option exists: `brief.driving` has one labelled line per
      jurisdiction driven, each carrying the three parts — a verdict from step 1 right
      after the legality label, the desks, an as-of stamp — with its source; the
      insurance line once; and no skeleton recommends self-drive where legality is
      `not legal` / `unverified`.
- [ ] `brief.connectivity` opens with the handset line (models known, or the pick per
      hardware type and the models asked for in the assumptions block).
- [ ] The same-language community consensus is a `decisions[]` row with its source, or
      reads "community consensus not checked"; a disagreement with the default went to
      the user.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall