mirror of
https://github.com/hanzoai/video.git
synced 2026-11-03 04:21:39 +00:00
11 production pipelines, 47 tools, 124 agent skills. Supports cloud APIs (fal.ai, OpenAI, ElevenLabs, Suno, HeyGen, Runway) and free local providers (diffusers, Piper TTS, WAN 2.1, Hunyuan, CogVideo). Co-authored-by: Hanzo Dev <[email protected]>
1.6 KiB
1.6 KiB
Idea Director - Animation Pipeline
When To Use
Use this pipeline when the video should be built primarily through designed motion: motion graphics, kinetic typography, diagram-led explainers, math visuals, or illustrative animation.
Do not use this pipeline when the project is really footage-led with a few overlays. That belongs in hybrid.
Reference Inputs
docs/animation-best-practices.mdskills/creative/animation-pipeline.mdskills/creative/storytelling.md
Process
1. Classify The Animation Mode
Choose the primary mode:
diagrammaticmotion_graphicskinetic_typemath_animationillustrativemixed_animation
2. Decide The Visual Path Early
Figure out which tools are supposed to do the work:
diagram_genmath_animatecode_snippetimage_selectorvideo_selectoror a concrete video provider tool- source-provided art
If the requested mode depends on unavailable tools, say so in the brief metadata immediately.
3. Choose A Reuse Strategy
Animation gets expensive when every scene is unique. Define:
- recurring motifs,
- layout system,
- transition family,
- typography hierarchy.
4. Build The Brief
Recommended metadata keys:
animation_modevisual_pathnarration_strategyreuse_strategytiming_styleblocked_capabilities
5. Quality Gate
- the animation mode is explicit,
- the visual path is feasible,
- the project is designed for reuse,
- the brief is honest about missing tools.
Common Pitfalls
- Treating all animation as one generic category.
- Planning bespoke visuals for every scene.
- Hiding missing tool paths until the asset stage.