Manim Video

Use this skill for Python-based Manim projects that need a clean planning phase, strong visual direction, reusable scene structure, and a deterministic render pipeline.

The output contract is usually a workspace project directory containing plan.md, script.py, concat.txt, draft renders, and optionally a stitched final.mp4.

Creative Standard

This is educational cinema, not animated slides.

• Make it beautiful and professional. The draft should feel intentional, polished, and presentation-ready, not like a rough internal diagram dump.
• Before writing code, define the narrative arc: confusion -> visual hook -> mechanism -> payoff -> recap.
• Geometry before algebra. Show the shape, motion, system flow, or data change before the formal equation.
• Every scene teaches one dominant idea. If a scene has two unrelated claims, split it.
• Direct attention with opacity layering: primary elements at 1.0, contextual elements around 0.35-0.45, and structural elements like axes or grids around 0.12-0.2.
• Give reveals breathing room. Add self.wait() after every important animation and make the main aha moment the longest pause.
• Keep one cohesive visual language across the whole project: shared palette, shared timing constants, shared font rules, and stable concept-color meaning.
• Avoid repetitive scenes. Vary dominant color, layout, and entry animation across scenes while keeping the overall palette consistent.
• First-render quality matters. If the layout is cluttered, the typography is inconsistent, or the pacing feels rushed, the scene is not done.