Zebrafish Long-Form Animated Video
Use for animated explainers, multi-scene narrative or campaign films, educational animation, and longer product or brand stories whose timeline, continuity, voice, music, captions, or cutdowns need whole-film judgment.
Do not impose a one-to-ten-minute range, fixed phase sequence, or mandatory artifact inventory. Let the brief and justified beats determine length and planning depth. Use UGC for creator-native ads, Cinematic Scene for one focused scene, and Product Demo Film when real product proof is the spine.
Follow the shared production kernel from the Zebrafish root. This skill owns long-form narrative, animation, audio, and timeline judgment; the current job owns its brief, script, storyboard, prompts, references, timing, budget, and deliverable set.
Load by Need#
| Need | Read |
|---|---|
| Define audience, premise, arc, sequence architecture, duration, or script | Shape |
| Establish visual language, scene staging, animation, edit, voice, or sound | Craft |
| Plan assets, references, generation topology, assembly, live models, or spend | Generation |
| Compile timeline acceptance or review the actual film and cutdowns | Critique |
| Diagnose and repair a scene, handoff, audio, or whole-film failure | Polish |
Load only what the current action needs. Before spend on a multi-scene film, read Shape, Generation, and Critique so story state, execution, and evidence agree.
Non-Negotiables#
Trace factual product, customer, legal, and compliance claims to supplied or Project sources.
Maintain a coherent story and visual system across scene boundaries without forcing identical shot construction.
Reconcile each generated opening state with its requested first action and each scene ending with the next scene's handoff.
Review the continuously played final assembly, not only its component clips, and include audible content when audio matters.
Deliver only the exact admitted generation or final bytes bound to their review SHA-256 and runtime provenance.
Direct operations and workflows are both valid when live runtime capabilities accept them. Stop when required claims, identity rights, spend, or artifact evidence remain unresolved.