mooboard-create-decision-board

name	mooboard-create-decision-board
description	Creates a new Mooboard / Moobird structured decision board on an infinite canvas. Use for comparisons, research, planning, option evaluation, evidence gathering, and recommendation boards.
disable-model-invocation	true

Mooboard Create Decision Board

Create a new board under the Mooboard library in a structured, comparison-friendly decision board layout on an infinite board.

This style is for understanding a topic, comparing options, and moving toward a decision.

Core idea

The canvas is infinite, so groups may be spread out as needed. The board does not need to fit into a single compact page.

However, placement must be intentional and structured:

• define clear regions or lanes
• group related evidence with the option it supports
• size images and cards deliberately
• use whitespace to separate options and ideas
• avoid overlap entirely

Do not rely on a layout script. Use agents to inspect structure, spacing, and clarity.

Best use cases

• Product comparisons
• Car comparisons
• Wedding venue choices
• Holiday planning
• Software tool evaluation
• Research boards
• Pros / cons boards
• Project planning or decision framing

Style rules

A decision board usually includes:

• a clear title and question
• 2–6 options or categories
• per-option clusters
• images, files, and links grouped with each option
• short notes such as pros, cons, unknowns, price, or key facts
• a summary / recommendation area
• an action list or next steps

It should not look like:

• a loose expressive collage
• a Pinterest wall
• a dense text document
• a diagram with unclear group boundaries

Layout character

Desired feel

• Structured
• Readable
• Evidence-based
• Easy to compare across options
• Spacious enough to think visually

Common patterns

Pick one pattern based on the task:

1. Columns by option
   • best for direct comparisons
2. Rows by criterion
   • best when criteria drive the decision
3. Cluster map with summary zone
   • best for broader research

Default to columns by option unless another structure is clearly better.

Spacing expectations

• Gap between major option regions: 180–320px
• Gap between objects within one option region: 80–160px
• Hard minimum gap between substantial content boxes: 60px

Required multi-agent workflow

Agent 1 — Information Architect

Determines:

• the decision question
• the option set
• the criteria or evidence categories
• the best structure: columns, rows, or clusters

Agent 2 — Region Planner

Defines:

• board regions
• x/y zones for each option or category
• where the summary and next steps will live

Agent 3 — Layout Planner

Chooses:

• image sizes
• card sizes
• note placement
• the order of objects inside each option area

Agent 4 — Collision Auditor

Checks:

• no overlaps across or within regions
• enough whitespace
• option regions remain visually distinct
• image sizing preserves ratio
• notes and links remain legible

Agent 5 — Logic Critic

Checks:

• claims are near supporting evidence
• each option has enough information
• the board is understandable at a glance
• the summary area actually reflects the content

Agent 6 — Final Manifest Reviewer

Checks the final manifest after writing.

Workflow

Decision Board Progress:
- [ ] 1. Confirm theme, board name, and destination folder
- [ ] 2. Gather options, images, links, and notes
- [ ] 3. Identify comparison structure (columns, rows, or clusters)
- [ ] 4. Define board regions
- [ ] 5. Choose object sizes and place anchor content
- [ ] 6. Place supporting notes, links, and evidence
- [ ] 7. Add summary area and next actions
- [ ] 8. Multi-agent review for spacing and logic
- [ ] 9. Write .mooboard.json — every image `presentation: "interactive"`, every link `previewMode: "card"`
- [ ] 10. Remove orphan media files not referenced by interactive images
- [ ] 11. Final manifest review (confirm no `presentation: "file"`)

Regions

A decision board should usually contain:

• Title / question region
• Criteria or framing region (optional)
• Option regions
• Summary / recommendation region
• Todo / next steps region

Do not let these blur together. Use whitespace as a structural tool.

Images

For every image on the canvas:

• use type: "image"
• store at board root
• include naturalWidth and naturalHeight
• MUST set presentation: "interactive" — this is preview / collage mode
• preserve aspect ratio

Critical: interactive vs file mode

Mooboard treats images differently based on presentation:

Value	What the user sees	When to use
"interactive"	Full image preview tile (correct for boards)	Always for collage / decision / masonry images
"file"	Generic file card (180×150-ish, no real preview)	Never for these skills

Hard rules:

1. Every image object in .mooboard.json must have "presentation": "interactive".
2. Never write "presentation": "file".
3. Do not leave orphan media in the board folder. Mooboard auto-imports loose files as presentation: "file" cards and can wipe a careful layout. Only keep files that appear as interactive objects in the manifest.
4. After writing the manifest, verify every image on disk is referenced by an interactive image object (or delete unused files before the user opens the board).
5. Link cards must use previewMode: "card" with a real previewImage URL — not plain/button.

Sizing guidance

Decision boards usually benefit from more consistency than collages. Typical display heights:

• hero / main reference: 280–420
• supporting image: 200–300
• thumbnail evidence: 150–220

You may vary sizes, but keep each option region internally coherent.

Supporting cards and notes

Useful object types:

• link cards (previewMode: "card" + previewImage)
• native text notes
• todo card
• optional arrows

Do not add type: "file" cards or images with presentation: "file" for option evidence.

Suggested note labels:

• “Pros”
• “Cons”
• “Price”
• “Unknowns”
• “Standout feature”
• “Risk”
• “Best for”

Arrows

Use arrows sparingly. Good uses:

• note → image
• claim → supporting source
• summary → winning option

Avoid decorative arrow overload.

Placement method

Column-by-option default

1. Define each option region width
2. Place an option header
3. Place the main image or evidence card
4. Place supporting link cards and notes below or beside it
5. Repeat for each option
6. Put the summary / recommendation region to the right or below all options

Structured reasoning rule

If a note makes a claim, it should sit near the evidence or item it refers to. Do not place free-floating insights with no clear target.

Titles and summary

The title should clearly frame the question. Examples:

• “Which hybrid should I buy?”
• “Best wedding venue options”
• “Choosing a local-first note tool”

The summary region should include:

• current favourite or leaning
• open questions
• next actions

Camera and envelope

Typical envelope:

{
  "version": 1,
  "createdAt": 0,
  "lastOpenedAt": 0,
  "objects": [],
  "camera": { "x": 500, "y": 350, "zoom": 0.42 },
  "background": "default",
  "showGrid": true
}

Output to the user

Report:

1. Absolute board path
2. Number of options or regions
3. Counts of images, links, notes, and todos
4. Any skipped assets or unresolved evidence
5. That they should open or refresh the board in Mooboard

Anti-patterns

• Mixing all options together with no visual grouping
• Overlapping notes, cards, or images
• Collage-like scattering when comparison is needed
• Too much text with no hierarchy
• Claims far away from evidence
• Summary with no relationship to board content
• Relying on scripts instead of agent review
• Writing images with presentation: "file" (shows as file cards, not previews)
• Leaving unused media in the board folder (auto-imports as file cards)
• Link cards without previewMode: "card" / previewImage