Communitygithub.com

hozanBaydu/animated-explainer-shorts

Rules for writing and animating short explainer videos (YouTube Shorts, Reels, TikTok and longer explainers) that people actually watch. Use when planning, scripting, storyboarding, animating or reviewing an animated explainer video, its hook, pacing, camera, characters, captions or voiceover.

What is animated-explainer-shorts?

animated-explainer-shorts is a Claude Code agent skill that rules for writing and animating short explainer videos (YouTube Shorts, Reels, TikTok and longer explainers) that people actually watch. Use when planning, scripting, storyboarding, animating or reviewing an animated explainer video, its hook, pacing, camera, characters, captions or voiceover.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/hozanBaydu/animated-explainer-shorts/tree/HEAD/plugins/animated-explainer-shorts/skills/animated-explainer-shorts

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Animated explainer videos

Apply these rules when you plan, write, animate or review a video. Story rules come first: a beautiful video with a flat script still fails.

Making the video

When the user wants an actual video file, build it with Remotion (and Three.js for 3D) from the template in this skill.

  1. Story first. Write the script as beats (one idea per beat) using the Story rules below. Check the first sentence and the opening seconds before anything else.
  2. Project. Copy template/ to a new folder, run npm install. Read reference/remotion.md before writing code, and reference/threejs.md before any 3D scene.
  3. Voice. If the user gives a voiceover (their recording or any text-to-speech file), put it in public/ and set "voice" in public/plan.json. If they don't, put each line in its scene's "text" and run npm run voice (free Kokoro voice, English): it writes public/voice.wav and sets every scene's start and end. Pick a voice with node scripts/voice.mjs am_michael (male) or the default af_heart (female).
  4. Timing. Run npm run captions for word timestamps. With your own voice file, start each scene at the first word of the line it shows; with npm run voice this is already done.
  5. Scenes. Write one component per scene in src/scenes/, register it, and list the scenes in plan.json. Every spoken line gets its own visual.
  6. Check. Render stills (npx remotion still Main out/still.png --frame=N) at the start, middle and end of each scene, look at them, and fix anything that breaks the rules below.
  7. Render. npm run render writes out/video.mp4. Watch the first 3 seconds again before calling it done.

Requirements: Node.js 18+ and ffmpeg. Remotion downloads its own headless Chrome on the first render.

Story

  1. Every video is a small story: a character wants something, something blocks it, a twist happens, there is a payoff. A list of facts is not a story.
  2. The first sentence is a bold claim, a contradiction of something people believe, or a character with a problem.
    • Good: "Something in your kitchen is killing you." / "I always thought computers were better at math than people." / "This is Uncle Don, and he's got a huge problem."
    • Bad: "How does X work?" / "Here are 3 tools that…" / "Today we'll look at…". If the video answers a "how" question, move that question to the second sentence.
  3. Open a question or a tension in the first 3 seconds and keep the answer for later. Don't spend the twist in the hook.
  4. Pick broad or timely topics. A niche topic needs an everyday angle that anyone can feel.
  5. A strong opener doesn't save a weak topic. Decide the topic first, then write the hook.
  6. Every video stands on its own. No "Part 2", no openers that continue an earlier video, no generic utility lists.
  7. Show, don't tell: every spoken line has its own visual. If the video makes sense on mute, the scenes work.
  8. One idea per scene. If a line holds two ideas, split it into two scenes.
  9. Escalate: each beat raises the stakes or the surprise a little more than the one before.
  10. End on a line the viewer can repeat or use (a question to ask, a rule of thumb), not on a summary.
  11. Length is a free choice: use the length the story needs. In long videos, give a small payoff at least every 60-90 seconds.

Framing (vertical 1080x1920 unless stated)

  1. Keep the main subject in the upper-middle band, about y = 500-1100.
  2. The bottom ~20% (y > 1500) sits under the platform's UI: no key visuals there. Put captions just above it.
  3. Keep ~60 px margins on the sides. Keep the right edge (x > 960, y 900-1700) free of key information, because the like and comment buttons sit there.
  4. Center framing usually works best in vertical video. Use thirds for scenes with two subjects.
  5. One dominant element per frame. Everything else is smaller, darker or less saturated.
  6. A character's face should be at least ~15% of the frame width in key moments.

Opening seconds

  1. Start speaking at frame 0. No silent intro, no logo.
  2. Something visibly changes within the first 1-2 seconds: a new object, a move, a transformation. No static title card.
  3. Big text in the first frame is optional. If you use it, it states the claim; it isn't decoration.
  4. A face in the first frame is optional. A strong character or image works just as well.

Camera (2D and 3D)

  1. Every camera move has a motive: it follows a character, reveals information or adds emphasis. No decorative motion.
  2. Never move linearly: always ease in and out.
  3. Reveal = slow push-in (scale 1.0 to 1.1-1.25 over 1-3 s). Shock = fast punch-in (0.15-0.25 s) with a small shake.
  4. New location: wide shot first, then closer.
  5. Low angle = power or threat, high angle = small or helpless, eye level = neutral.
  6. If two characters face each other, keep each one on its own side for the whole scene.
  7. In 3D: FOV 35-50 degrees, depth from foreground, middle and background layers. Move the camera (dolly) rather than changing the FOV (zoom).
  8. In 3D cartoon scenes, use linear tone mapping and a slight saturation boost; filmic tone mapping washes cartoon colours out.

Editing and pacing

  1. After the opening, pacing follows the style. A fast first moment matters more than a fast whole video.
  2. Eye trace: the point of interest in a new shot starts where it was in the previous shot.
  3. Match cuts: a shape or colour from the end of one scene becomes the start of the next.
  4. After a joke or a punchline, hold 0.3-0.6 s before cutting.
  5. Slow down before the key moment, speed up after it.
  6. Cut on action: change shots in the middle of a movement, not after it stops.
  7. No white flashes or strobe transitions. Use whip pans, match cuts and wipes.

Character animation

  1. Squash and stretch on every impact and jump (scale 0.8-1.25, volume roughly kept).
  2. Anticipation: a small move the opposite way before a big move (0.1-0.2 s).
  3. Follow-through: hair, antennas and arms keep moving and settle after the body stops.
  4. Limbs and thrown objects move on arcs, never on straight lines.
  5. Blinking, breathing and idle sway never stop, even while a scene waits.
  6. Timing sells weight: heavy things move slowly and land hard, light things move fast.
  7. Exaggerate emotions: huge eyes, big mouth shapes, a flying sweat drop.
  8. One clear silhouette per pose. If the pose doesn't read as a black shape, change it.

Text and captions

  1. Captions: 2-5 words per chunk, synced to the voice, popping in, high contrast (white with a dark outline).
  2. Big kinetic words only at punch moments, and only one big word group on screen at a time.
  3. Numbers on screen exactly match the narration and the source.

Voice

  1. Short sentences, a spoken rhythm, contractions ("it's", "didn't").
  2. About 170-200 words per minute.
  3. 0.2-0.4 s of silence between beats, 0.6-1.0 s before the final line.

Honesty

  1. Every number on screen has a real source and matches it.
  2. Never put first-person claims into the narration that the creator didn't actually do.
  3. Parody headlines use clearly made-up names, never imitations of real outlets.

Related Skills