Three d breakdown v1

3D Breakdown Format

Use this skill when a user asks an agent to make, inspect, or improve a Wiggly 3D Breakdown.

Start from one link

When the user sends only this Repo link:

1. Say: I can make this ad for you.
2. Ask: What brand or website is this for?
3. Wait for the answer.
4. Ask: Do you want Guide Me or Turbo?
5. Wait for the answer.
6. Research the site with your web tools.
7. Save the facts in research.json with the provided StoredWebsiteResearchResult shape.
8. Ask: What should the video focus on?
9. Offer product, brand story, customer problem, custom idea, or Pick for me.
10. If the user picks product, ask which product in the next message.
11. Show the run estimate.
12. Ask: Ready to start?

Ask only one question in each message. Use short sentences and simple words. Never ask for a budget or spend limit. Never ask the user to pick a model, tool, or technical setting.

If you cannot browse the web, ask for a Wiggly research export. Do not ask for anything else in that message. Turn the research into the provided StoredWebsiteResearchResult input. Keep a source URL for each fact. Never invent a fact.

Progress

Use this line during the run:

Research → Story → Script → Images → Clips → Final

Start every work update with Step X of 6: Name. Never send a work update without it. Add the current item when a step has more than one part:

• Step 4 of 6: Images — Storyboard
• Step 4 of 6: Images — Key image 2 of 4
• Step 5 of 6: Clips — Clip 1 of 2
• Step 6 of 6: Final — Done

Keep the update short. In Turbo, send an update after each step but do not ask a question unless blocked.

Work modes

Guide Me

• Show each big deliverable.
• Explain it in plain words.
• Ask for approval before the next big step.
• Ask before each paid call.
• Show all five story ideas.
• Let the user pick the idea.

Turbo

• Pick the strongest story and creative choices.
• Show the run estimate before any provider call.
• Ready to start? is approval for one normal attempt at each listed step.
• Do not ask again during a clean run.
• Stop if work looks wrong, a tool fails, or a retry is needed.
• Explain the problem in one short note.
• Ask before any retry or replacement call.

Run estimate

Before Ready to start?, check the current provider prices and show:

Run estimate

- Story ideas and plan: 3 NIM calls — about $X
- Storyboard: 1 image — about $X
- Key images: 4 images — about $X
- Video clips: 2 clips, 10 seconds each — about $X
- Voice: 1 voice track — about $X
- Final video: local render — $0

Total: about $X
Time: about X-Y minutes

Use current prices. Do not guess. If a price is not public, say price not listed. The estimate covers one attempt per item. A retry needs a new estimate and a new yes.

Rules

• Read requirements.json, inputs.json, pipeline.json, scene-contract.json, assets.json, goldens.json, and quality.json.
• Watch FinalStraw first, then the supporting videos in goldens/. They show the creative bar; do not copy their brands, claims, shots, or wording.
• Use the packaged runner and the canonical Wiggly modules. Do not rebuild the renderer, timing model, prompt builders, or scene contract.
• Product focus requires a catalog product with a usable image. Brand and customer-problem stories do not require a product.
• Treat website research as evidence. A custom brief changes the creative focus but does not authorize new factual claims.
• In Guide Me, show the five story directions before selecting one. In Turbo, save all five and pick the strongest one.
• Validate the selected plan before any image call.
• In Guide Me, one explicit approval covers one image call only. In Turbo, the approved run estimate covers one attempt for each listed image. Never batch provider requests. Record a separate approve or reject review for every current artifact.
• In Guide Me, ask once before the two planned video clips. In Turbo, use the approved run estimate. Submit one clip at a time and inspect clip 1 before spending on clip 2.
• Generate one explicitly approved Fish narration only after both clips pass inspection.
• Render the final MP4 locally through the packaged Remotion entry and AdRenderSurface. Never rebuild or replace the renderer.
• Never print secret values. Report only missing key names.
• Fail loudly. Do not switch providers, repair model output, retry automatically, or hide an error.

Agent loop

1. Run check --stage=plan.
2. Run init with the exported Wiggly website research and the chosen story subject.
3. Use the approval for the three planning calls: one story-slate call, then one script call and one scene-plan call. Run directions.
4. In Guide Me, show all five directions and let the user choose. In Turbo, pick the strongest saved direction.
5. Run select, then validate.
6. Compare the selected direction with the production references. State the concrete hook, the job of the blue explanation world, the visible transformation, the product or subject carried through the story, and the final payoff. If any answer is vague, revise before an image call.
7. Let the user inspect the script, storyboard plan, image prompts, and CTA. The MVP runner does not edit these fields; if the plan is wrong, stop and start a new run from the saved research instead of spending on media.
8. In Guide Me, ask before each image command. In Turbo, use the approved run estimate.
9. Generate and review the storyboard first, then generate and review full-quality endpoint frames 1, 3, 4, and 6, one approved image call at a time. All six frames stay in one Style B blue/cyan blueprint-grid explanation world while camera, scale, props, and physical state change.
10. Run inspect.
11. After explicit approval, generate video clip 1, review it, then generate video clip 2. Each clip may use motivated cuts or transitions to deliver three readable visual beats, but it must keep the approved world and demonstrator identity.
    • If a clip is still processing, its Replicate prediction ID is saved. Run the same command again without new approval to check that job; never submit a replacement.
    • If a ready clip is wrong, reject the current attempt with a reason before explicitly approving one replacement generation.
    • Clip 2 must complete meaningful action by global second 16 because the final four seconds belong to the product and CTA.
    • If clip 2 is good but late, use the packaged local retime-clip command and review the retimed file instead of buying another generation.
12. Run inspect again and review video-contact-sheet.jpg.
13. Run voice --approve-voice, then render.
14. Run inspect, watch the final MP4, and compare it with at least two production references. Technical completion alone is not a pass.
15. Use finalize --approve-final only if the creative result is genuinely usable, then return the finalized MP4 to the user.

Good result

• The story is understandable without knowing the brand.
• The first two seconds show a concrete product, customer tension, or false assumption. An abstract brand fact is not enough.
• Every factual claim maps to the saved website evidence.
• The five beats sound spoken, not like production notes or AI copy.
• The six-frame plan shows different physical actions in one coherent blue-grid CGI world. Object-only frames do not invent people.
• The blue world explains an invisible mechanism or change. It is not a decorative background.
• Every major narration beat causes a visible action, object change, or result.
• The approved product or subject remains recognizable through the world change and returns in the payoff.
• All four video endpoints are sharp, use the approved recurring subjects, and show the exact intended start or end state.
• Storyboard panel crops guide endpoint generation but never become Seedance inputs.
• Both 480p clips use three readable visual beats, follow the approved physical actions, and do not jump to another person, unapproved setting, or visual style.
• Renderer captions preserve the exact approved script words.
• Narration ends before the 20-second video ends and is not clipped.
• The final MP4 is 1080×1920, 20 seconds, contains exactly one audio stream, and preserves the approved two-clip story.
• A finished file that cannot credibly sit beside the Kiala and Theragun production references must not be finalized.