mirror of
https://github.com/hanzoai/video.git
synced 2026-11-03 04:21:39 +00:00
calesthio
e5367f7d66
New beta pipeline for reusable cartoon characters with SVG rigs, pose
libraries, action timelines, and Canvas/Remotion/HyperFrames rendering.
- pipeline_defs/character-animation.yaml: 11-stage manifest
- skills/pipelines/character-animation/: 11 stage director skills
- tools/character/: BaseTool implementations for char design, rigging,
pose libraries, action timelines, previews, and QA
- schemas/artifacts/{character_design,rig_plan,pose_library,
action_timeline,character_qa_report}.schema.json: canonical artifacts
- schemas/artifacts/scene_plan.schema.json: extended for character-led
scenes
- .agents/skills/{canvas-procedural-animation,character-animation-qa,
character-rigging,pose-library-design,svg-character-animation}/:
Layer 3 vendor knowledge
- AGENT_GUIDE / PROJECT_CONTEXT / README / ARCHITECTURE / PROVIDERS:
surface the new pipeline and its capability family
- tools/video/hyperframes_compose.py: SVG character rig support
- tests/contracts/test_character_animation_pipeline.py: contract tests
840 B
840 B
Scene Director - Character Animation Pipeline
Goal
Produce a scene_plan where each scene is feasible for rigged character
animation.
Scene Planning Fields
For each scene, include:
- character IDs,
- emotional beat,
- action sequence,
- camera/framing,
- background,
- props,
- effects,
- required assets,
- transition notes.
Use type: "character_scene" for rigged character acting scenes. Store
character-specific detail in character_actions; do not put per-scene acting
data in arbitrary metadata because the shared scene_plan schema rejects
unknown per-scene fields.
Complexity Budget
Prefer fewer, stronger shots:
- one establish,
- one action beat,
- one reaction beat,
- one resolution beat.
Avoid scenes that require many unique views or complex physical contact unless the user approved that complexity.