Add travel-planning + event-planning journeys (GEPA-optimized)

plugin/skills/diagram-recipes/SKILL.md

@@ -162,6 +162,8 @@ type + the knobs that make it read, and adapt the named recipe (in `examples/`).
 | Geo / locations + routes | `component` `Map` (Leaflet+OSM) — markers + route polylines; table as legend | `map-routes` |
 | Video / tutorial reference | `component` `Video` — thumbnail card + play button (YouTube poster auto-derived); link-out or `embed:true` to play inline | (see `diy-project-plan`) |
 | Project / build / DIY plan | `component` **top-down report** — badges + materials `Table` + interactive `Checklist` steps + `Video` tutorials + `Map` (where to buy) + `VegaLite` budget | `diy-project-plan` |
+| Trip / travel itinerary | `component` **top-down** — badges (days/season/budget) + ordered per-day sections + `Map` of stops (color-coded pins) beside a legend `Table` + `VegaLite` budget + packing `Checklist`. Keep each day TIGHT (comprehension drops when dense) | `travel-planning` |
+| Event / conference plan | `component` **top-down** — badges (date/headcount/budget) + phase `Timeline` + task `Checklist` (owners) + `VegaLite` budget + RACI `Table` + venue `Map` | `event-planning` |
 | Agent run / long transcript | `component` `Timeline` window + **progressive windowing** | `agent-trace` |
 | Data flow across tiers | `flow` **zones** (Sources→Marts→Consumers) | `data-lineage` |
 | Event/queue topology | `flow` producers→broker→consumers, animate, `TB` | `event-driven` |

plugin/skills/diagram-recipes/component.md

@@ -170,6 +170,25 @@ pins 1..N in marker order (great for an ordered route).
 ] }
 ```
 
+### planning/travel-planning — `component` (trip itinerary, top-down)
+**When to use:** a trip/vacation **itinerary** the reader plans and follows. A cohesive **top-down**
+document (NOT a flat grid of peers): a `Title` + badge row (duration · season · region · budget);
+an **ordered per-day spine** of `Card`s (Day 1…N, each with a theme + 2–4 concise activities — the
+dominant vertical element); then a `Grid` pairing a `Map` of the stops (one **color-coded pin per
+day**, routes connecting them) **beside a legend `Table`** that keys each pin colour → day → stop; a
+`VegaLite` **budget** bar chart (or a transport/lodging logistics `Table`); and an interactive
+packing/booking `Checklist`. **Keep each day TIGHT** — GEPA optimization showed comprehension
+collapses when day sections get dense and the board clips, so prefer short activity lines and ≤8
+map pins over exhaustive detail. → `examples/travel-planning.component.json`.
+
+### planning/event-planning — `component` (event/conference plan, top-down)
+**When to use:** planning an **event** (conference, wedding, launch, festival, party). Top-down:
+a `Title` + badges (date · headcount · budget); a phase **`Timeline`** (Concept → Venue → Promotion
+→ Run-of-show → Wrap-up) as the spine; a `Grid` with a `VegaLite` **budget** chart beside an
+interactive task `Checklist` whose labels carry the **owner** (e.g. "Sign venue contract — Ops");
+a **RACI/responsibilities `Table`** (one **A** per row); and a venue **`Map`**. Same density rule —
+keep phases and tasks concise. → `examples/event-planning.component.json`.
+
 ### media/video — `component` (`Video` — YouTube-style thumbnail card)
 **When to use:** referencing a video (a tutorial, a demo, a recording) — show a real **thumbnail
 card with a play button**, not a bare link. Give it a `url`; for YouTube the poster + watch link +