/VOX-COLLAGE-BROLL

name: collage-broll-explainers
description: Turn a ~5-second voiceover line, opinion sentence, or abstract concept into a premium editorial halftone paper-collage B-roll clip — optionally with a fitted voiceover. Load this skill whenever the user says "collage b-roll", "paper collage b-roll", "halftone collage", "collage-style visuals", "collage explainer" (or the Chinese triggers 纸拼贴 b-roll / 半调拼贴 / 拼贴风格配画面), or wants a script line turned into a collage visual metaphor. Enforces a mandatory three-gate approval flow — propose visual metaphors only, generate color collage stills only after the user confirms, and only after the stills are confirmed generate the assemble-from-empty animation. Video model is gemini-omni-flash, locked — no other video model is ever used and the choice is never offered to the user.

Collage B-roll Explainers

Compress a ~5-second voiceover line into one sharp visual idea, then turn it into a premium editorial paper-collage assembly animation.

Default pipeline:

1. Design the visual metaphor only, then wait for the user to confirm 2. Generate the final still frame only, then wait for the user to confirm 3. Automatically generate the video with first/last-frame references and run QA 4. Optionally generate a fitted voiceover and mux it in

The two confirmation gates are part of the workflow, not overhead. They let the user spend their attention on aesthetics and direction, and prevent a wrong metaphor or a wrong still from burning video-generation cost.

Runtime requirements

• **MaxFusion MCP** connected and authenticated (`https://mcp.maxfusion.ai/mcp`). All image, video, and speech generation runs through it. If it is not connected, stop and walk the user through connecting before doing anything else.
• **Local file access and ffmpeg** (e.g. Claude Code): frame preparation, video QA, silent delivery, and voiceover fitting download assets and process them locally. A sandboxed agent (no local downloads) can still run all three gates and display results in the MaxFusion widget, but must tell the user that frame preparation falls back to prompt-only color matching and that frame-by-frame self-QA, audio stripping, and voiceover fitting were skipped — the user should judge the clip by eye and mute it in their editor.

Mandatory approval protocol

Gate 1: Metaphor confirmation

When you receive the script line(s), propose visual metaphors first. Do not generate any image, do not generate any video, do not call any generation tool.

Deliver, for each line:

• Core meaning
• Emotion
• One-sentence visual proposition
• 3–6 key objects
• Suggested background color and local accent colors
• Intended assembly order

Then stop explicitly and wait for the user to reply "approved", "all approved", or give per-item revision notes.

If the user approves only some of the numbered items, only the approved items advance to Gate 2; keep iterating on the metaphors for the rest.

Gate 2: Still-frame confirmation

Only after the metaphor is confirmed do you write the visual spec and the image prompt, and generate the final still with `maxfusion_generate_image`.

Save the originals into the project directory, build a numbered still contact sheet, display every still to the user (`maxfusion_display_generation`, one call per image, plus the numbered mapping), and stop again. At this stage you still do not generate any video.

If the user approves only some stills, only the approved items advance to Gate 3; regenerate the rejected stills and re-confirm them first.

Gate 3: Video generation

Once the stills are confirmed, generate immediately. The video model is locked:

video_model: gemini-omni-flash

No other video model is ever used. Do not offer a model choice, do not ask the user which model to use, do not fall back to anything else on failure — apply the repair playbook and re-run on gemini-omni-flash.

Success criteria

• One line expresses exactly one clear metaphor
• A batch shares one design language, but is not forced onto a single blue background
• The background is a strong, flat, uniform color field, varied by meaning
• Subjects are built from black-and-white halftone photographic cut-outs
• Key cards, buttons, film strips, rulebooks etc. may use red, yellow, teal, orange, purple, or cream colored cardstock
• Every paper piece has crisp cut edges, a cream keyline, a soft low-opacity shadow, and paper grain
• Motion is assemble-from-empty — not gentle drift, wobble, or slow zoom
• No subtitles, no full script text, no logos, no watermark, no UI
• Default delivery: 9:16, 5 seconds, 720p, silent MP4 (audio track stripped) — or the voiced version when the user wants voiceover

When NOT to use this skill

• Precise control of layers, occlusion, camera fly-throughs, or an editable timeline is needed: use a layered animation tool instead (e.g. an HTML-rendered layered video approach)
• The user only wants a video prompt, not a finished clip: just write the prompt, skip this flow
• The user needs a real-person product ad or an on-camera presenter: do not use this collage flow
• The user explicitly needs per-layer editable transparent assets: this skill does not deliver separated transparent layers

Default project directory

Local working folder, named with the user's local date:

~/collage-broll-projects/YYYY-MM-DD-<title>/

Recommended structure for batch projects:

<project>/
├── brief.md
├── visual-spec.json
├── imagegen-prompts.md
├── omni-jobs.json
├── gate2-qa.md
├── gate3-qa.md
├── still-contact-sheet.jpg
├── omni-contact-sheet-all.jpg
├── video-first-frame-all.jpg
├── end-frame-comparison-all.jpg
├── 01-<concept-name>/
│   ├── omni-prompt.txt
│   ├── voiceover-raw.mp3            (optional voiceover stage)
│   ├── voiceover-trim.mp3
│   ├── frames/
│   │   ├── last-frame-original.png
│   │   ├── first-frame.png
│   │   └── last-frame.png
│   └── omni/run-v01/
│       ├── final-5s.mp4
│       ├── final-5s-no