| name | mooboard-create-lookbook |
| description | Creates a new Mooboard / Moobird fashion lookbook board on an infinite canvas. Use for outfit sets, capsule wardrobes, seasonal edits, and styled looks with shop links. |
| disable-model-invocation | true |
Mooboard Create Lookbook
Create a new board under the Mooboard library as a fashion lookbook
on an infinite board.
Core idea
Each “look” is a deliberate outfit cluster (hero + details + shop links),
not a random collage and not a giant masonry dump.
Infinite canvas lets you sequence looks (Look 1, Look 2, …) or seasons.
Do not rely on a layout script. Use multi-agent review.
Best use cases
- Seasonal capsules
- Wedding guest outfits
- Travel packing outfits
- Brand lookbooks
- Personal style edits
Style rules
Usually includes:
- title + season/occasion
- 3–8 look clusters
- 2–5 images per look (hero larger)
- short callouts (“tailoring”, “shoes”)
- shop/source link cards near items
- optional todo (buy / tailor / return)
It should not look like an unsorted Pinterest masonry wall.
Layout character
Desired feel
- Editorial, intentional, stylish
- Looks separated by whitespace
- Shop links attached to the right garment
Default pattern
Look columns or look bands
- Title
- Look 1 cluster, then large gap, Look 2, etc.
- Within look: hero left/top, details around, links below
Spacing expectations
- Gap between looks: 180–300px
- Gap within a look: 80–140px
- Hard minimum gap: 60px
Required multi-agent workflow
Agent 1 — Style Director
Defines occasion, palette, and look count.
Agent 2 — Look Planner
Assigns garments/images to each look.
Agent 3 — Layout Planner
Sizes heroes vs details and places links.
Agent 4 — Collision Auditor
Checks spacing and link attachment.
Agent 5 — Edit Critic
Checks whether each look feels complete.
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
Lookbook Progress:
- [ ] 1. Confirm occasion/season and board name
- [ ] 2. Gather outfit images + shop URLs
- [ ] 3. Group into looks
- [ ] 4. Place look clusters + links + callouts
- [ ] 5. Multi-agent edit 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.
Anti-patterns
- One undifferentiated image pile
- Shop links in a dump far from garments
- Looks bleeding into each other
- Duplicate photos of the same item without reason
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:
- Absolute board path
- Layout pattern used and key region counts
- Counts of images, links, notes/todos, and other objects
- Any skipped URLs or assets
- 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.
