mooboard-create-trip-board

name	mooboard-create-trip-board
description	Creates a new Mooboard / Moobird travel trip board on an infinite canvas. Use for itineraries, city guides, packing + places + reservations in one visual trip plan.
disable-model-invocation	true

Mooboard Create Trip Board

Create a new board under the Mooboard library as a trip planning board on an infinite board.

Core idea

Organize a trip by day columns or place clusters, with bookings, maps/photos, and logistics nearby. Infinite canvas = room for each day.

Do not rely on a layout script. Use multi-agent review.

Best use cases

• Weekend getaways
• Multi-city itineraries
• Honeymoon / anniversary trips
• Conference travel
• Road trips

Style rules

Usually includes:

• trip title + dates + travelers
• day columns (Day 1 / Day 2 / …) or city sections
• place photos + booking links
• logistics notes (flights, lodging, transport)
• packing / prep todo
• optional budget callouts

It should not look like a pure mood collage with no schedule.

Layout character

Desired feel

• Exciting but organized
• Days/places visually distinct
• Reservations attached to the day they matter

Default pattern

Day columns

1. Header band with title/dates
2. One column per day
3. Within day: morning / afternoon / evening notes + images + links
4. Logistics strip above or left of all days
5. Packing todo on the right

Spacing expectations

• Gap between day columns: 160–260px
• Gap within a day: 70–120px
• Hard minimum gap: 60px

Required multi-agent workflow

Agent 1 — Itinerary Architect

Chooses day vs place structure and outlines each day.

Agent 2 — Region Planner

Sets column/section geometry.

Agent 3 — Evidence Planner

Places photos, booking links, and notes.

Agent 4 — Collision Auditor

Checks spacing and that bookings sit with the right day.

Agent 5 — Traveler Critic

Checks whether the plan is actually doable (pacing, travel time).

Final Manifest Reviewer

Checks the written .mooboard.json:

• coordinates match the approved plan
• every image is presentation: "interactive"
• every link is previewMode: "card" with previewImage
• folder media matches referenced paths exactly

Workflow

Trip Board Progress:
- [ ] 1. Confirm destination, dates, board name
- [ ] 2. Gather places, bookings, photos, links
- [ ] 3. Choose day columns vs place clusters
- [ ] 4. Place logistics + day content
- [ ] 5. Add packing todo
- [ ] 6. Multi-agent pacing review
- [ ] 7. Write .mooboard.json
- [ ] 8. Remove orphan media; final review

Images and media (hard rules)

For every image on the canvas:

• use type: "image"
• store media at the board root
• include naturalWidth and naturalHeight
• preserve aspect ratio
• MUST set presentation: "interactive" (preview tiles)

Never use presentation: "file" for images meant to be seen as previews.

Link cards must use:

• previewMode: "card"
• a real previewImage URL

Audio / PDF / other attachments use type: "file" with presentation: "interactive" when the user should open/play them.

No orphan media. Every media file in the board folder must be referenced by a canvas object. Extra loose files get auto-imported as file cards and can destroy the layout.

Bounding boxes

Maintain a placement table of (id, type, x, y, width, height, region). Treat images, links, todos, native text, geo, and file cards as blocking boxes. Arrows may cross freely and are not blockers. Never allow accidental overlap between blocking boxes.

Anti-patterns

• Days blurred together
• Bookings far from the day they apply to
• Impossible pacing (too many places per day) with no warning note
• presentation: "file" images or orphan media

Camera and envelope

{
  "version": 1,
  "createdAt": 0,
  "lastOpenedAt": 0,
  "objects": [],
  "camera": { "x": 400, "y": 300, "zoom": 0.4 },
  "background": "default",
  "showGrid": true
}

Use epoch-ms timestamps. Object IDs: UUIDs for moobard objects; shape:<id> for native shapes.

Output to the user

Report:

1. Absolute board path
2. Layout pattern used and key region counts
3. Counts of images, links, notes/todos, and other objects
4. Any skipped URLs or assets
5. That they should open or refresh the folder in Mooboard to see it

Do not claim the app rendered the board unless that was observed.