manim-explainer-animations

Manim Explainer Animations (Manim Community Edition, latest stable v0.20.x)

What this skill produces

A produced-feeling explainer sequence, not just technically-correct code: a hook, a build-up, a visual payoff, a release — using the right mobject/animation combination for the idea, not just the first one that works. Treat camera work, color, pacing, and text choices as part of the deliverable.

Always use Manim Community Edition (pip install manim, import as from manim import *), not manimlib (Grant Sanderson's personal fork), unless the user explicitly asks for exact 3b1b source parity. CE is what's documented, pip-installable, and actively maintained.

Setup

pip install manim --break-system-packages
apt-get install -y libcairo2-dev libpango1.0-dev ffmpeg 2>/dev/null || true
python3 -c "import manim; print(manim.__version__)"   # confirm before building anything nontrivial

Optional but high-value plugins (check if the task needs them before installing):

pip install manim-voiceover --break-system-packages   # narration-synced timing, TTS or recorded audio
pip install manim-physics --break-system-packages     # rigid body / fluid / pendulum simulations

Workflow

1. Identify the idea's shape before picking mobjects. Is this a transformation (Transform-family), a process over time (updaters/ValueTracker), a relationship (Graph/graph theory), a function (Axes/ParametricFunction), a proof/derivation (MathTex + TransformMatchingTex), or a spatial object (3D mobjects)? The category determines which reference file to read.
2. Storyboard in beats (5-8 beats, ~5-20s each): hook → build-up → core demonstration → payoff. Comment each beat in the construct() method so timing can be adjusted independently later.
3. Read the relevant reference file(s) below before writing code — don't guess class names or signatures from memory; the API surface is large and easy to misremember (e.g. ShowCreation was renamed Create in CE; TexMobject/TextMobject were renamed MathTex/Tex).
4. Render low-quality first, iterate on timing, then final-render:

   manim -pql scene.py SceneName    # quick preview, 480p15
   manim -pqh scene.py SceneName    # 1080p60 final
   manim -pqk scene.py SceneName    # 4K60, only if actually needed
   

5. Apply the style-guide conventions (color, camera, pacing) from references/style-guide.md — don't leave default Manim styling (pure black background, default primary colors) unless the user asked for a plain/utilitarian look.