mooboard-create-palette

name	mooboard-create-palette
description	Creates a new Mooboard / Moobird color and materials palette board on an infinite canvas. Use for brand colors, interior finishes, fashion textiles, and mood-driven material boards.
disable-model-invocation	true

Mooboard Create Palette

Create a new board under the Mooboard library as a palette / materials board on an infinite board.

Core idea

Swatches, material photos, and references are grouped by role (primary, accent, neutral, texture, reject). Native geo rectangles are encouraged as color swatches.

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

Best use cases

• Brand color systems
• Interior finishes
• Fashion fabric boards
• Packaging material exploration
• Art direction palettes

Style rules

Usually includes:

• title + short design intent sentence
• 4–12 color swatches (geo, filled, dash: "draw" ok)
• 4–10 material / reference images
• labels for hex/name/role
• optional “do / don’t” lane
• optional todo for sampling/orders

It should not look like a product comparison or a dense masonry catalog.

Layout character

Desired feel

• Calm, curated, designerly
• Swatches readable at a glance
• Materials near the colors they support

Default pattern

1. Title + intent top-left
2. Swatch row or swatch cloud under title
3. Material images grouped beside/below related swatches
4. Reject / alternatives further right

Spacing expectations

• Gap between swatches: 40–80px
• Gap between material images: 100–180px
• Hard minimum gap: 50px

Required multi-agent workflow

Agent 1 — Palette Strategist

Defines roles (primary/accent/neutral/texture) and constraints.

Agent 2 — Swatch Planner

Chooses geo sizes/colors and label copy.

Agent 3 — Reference Planner

Places material images near related swatches.

Agent 4 — Collision Auditor

Checks overlaps and label legibility.

Agent 5 — Taste Critic

Checks whether the palette feels coherent.

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

Palette Progress:
- [ ] 1. Confirm brand/space theme and board name
- [ ] 2. Gather colors + material images + refs
- [ ] 3. Place swatches with labels
- [ ] 4. Place supporting materials
- [ ] 5. Multi-agent coherence review
- [ ] 6. Write .mooboard.json
- [ ] 7. 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.

Useful tldraw geo colors include yellow, light-red, blue, green, violet, black, grey.

Anti-patterns

• Unlabeled mystery swatches
• Materials disconnected from the colors they illustrate
• Overlaps hiding swatch identity
• 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.