agentleFS
kevinbadikevinbadi/claude-motion-faceless-skills/skills/motion-styles/SKILL.md

motion-styles

Skill9 starsChanged 22 days agoMITView on GitHub

Claude Motion style suite: 74 animated-explainer looks (whiteboard, chalkboard, watercolor, stained glass, risograph, shadow puppet, claymation, manga, ukiyo-e, CRT terminal, Game Boy, Win95, synthwave, isometric, voxel, film noir, neon sign, transit map, isotype, kinetic type, psychedelic and more) built as code-drawn canvas animations with a synthesized sound score, rendered to MP4 at 16:9 or 9:16. Use when the user asks for an animated explainer, a motion graphic or B-roll "in the style of" a medium, a "<style> version" of a topic or to compare looks for a video.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. BintzGavin/helios★ 130same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every style is original code: a canvas renderer + synthesized sound, rendered frame by frame in headless Chrome.

    line 8
  2. Distinctive:

    Write original code for every look.

    line 64
  3. Very specific:

    Follow STYLE_CONTRACT.md, keep the primitive signatures identical so scenes can swap styles, verify with landscape and portrait stills, …

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Motion styles (74 explainer looks, one engine)

Every style is original code: a canvas renderer + synthesized sound, rendered frame by frame in headless Chrome.

Layout

PathWhat
index.jsonevery style: id, name, family, one-line look, built flag
styles/<id>.jsthe style module (MS.register): surface, finishing pass, lettering, arrows, boxes, counters, emphasis, transition, sound palette, and a 12 s demo
styles/<id>.mdthe style card: look, motion, how it explains, palette, fonts, signature techniques, when to use it
STYLE_CONTRACT.mdthe module API every style implements (read before writing or editing a style)
engine/kit.jsK: seeded rng/noise, easing + beat timing, camera, paper/grain textures, wobble + draw-on paths, arrows, text, counters, portrait layout
engine/sound.jsSND: synthesized SFX (pop, stamp, thud, whoosh, tick, click, blip, pluck, chime, ding, wrong, riser, glitch, paper, swell, scribble[marker/chalk/pencil/brush/pen/spray], type, count) + beds (room, tape, hum, vinyl, space, ocean, crowd), limiter on the master
engine/player.htmllive preview with scrub + sound (?style=<id>&scene=<file>&w=&h=)
engine/render.mjsMP4 / stills renderer (Chrome -> ffmpeg, audio via OfflineAudioContext)
engine/gallery.mjscontact sheet of every built style
templates/scene.jsstarting point for a custom explainer on any topic

Setup once: cd engine && npm i (puppeteer-core; uses the installed Google Chrome, override with CHROME_PATH). Needs ffmpeg on PATH.

Families

Popular Explainer Looks, Hand-Drawn, Painterly, Print, Paper & Craft, Illustration, Art & Design Movements, Retro Digital, Retro UI & Neon, Dimensional, Light & Imaging, Data & Information, Generative & Type, Cosmic & Psychedelic. Pick by the story: data and process explainers read best in Hand-Drawn, Data & Information, Dimensional and the Popular looks; nostalgia and humour in Retro Digital / Retro UI; premium launches in Light & Imaging / product-launch; culture and history in Illustration / Art movements. When the user names a look loosely ("make it look like an old newspaper"), search index.json names and looks and offer the 2 or 3 closest.

Make an explainer

  1. Pick the style and read its styles/<id>.md. Watch its demo first: node engine/render.mjs --style <id> --out /tmp/<id>.mp4 (or open engine/player.html?style=<id>).
  2. Write the scene for the topic: copy templates/scene.js into the project (e.g. projects/<slug>/scene.js) and fill SCENE = { duration, draw(ctx, W, H, t, S), score(k, S) } using the style's primitives (S.background, S.title, S.label, S.arrow, S.box, S.counter, S.emphasis, S.transition, S.finish). Beats: a hook out of the way within ~2 s, something changing every 1 to 2 s, arrows that draw on to show cause, labels landing on what they label, one medium-true scene change, an emphasis on the key number, a held takeaway (~1 s). Keep elements continuous between beats (move, grow, morph) and cut only when the story really moves on. With a voiceover: time beats to the Whisper word stamps of the narration, never to guessed pacing.
  3. Storyboard check: render stills at every beat and look at them before the full render: node engine/render.mjs --style <id> --scene /abs/path/scene.js --stills 1,3,5,7,9,11 --out /tmp/sb
  4. Render: node engine/render.mjs --style <id> --scene /abs/path/scene.js --out renders/<slug>.mp4 Vertical: add --size 1080x1920 (layouts must read on a phone: use K.layout(W, H), fractions of W/H in portrait). A 12 s 720p explainer renders in a few seconds.
  5. Narration: render with --voiceover (SFX sit lower, beds and music drop out) and mux the narration on top with ffmpeg (-filter_complex amix=inputs=2:normalize=0).
  6. Save finished videos with a readable name the user can find (e.g. ~/Downloads/<Readable Name>.mp4).

Rules

  • Frames are pure functions of t. Seeded K.rng / K.noise only, never Math.random. Cache static textures.
  • The finishing pass sells the medium (grain, ink pooling, misregistration, scanlines, glow). Never skip it.
  • Phone legible: headlines >= 44px, labels >= 28px, key numbers >= 64px at 1280x720 (scaled by K.layout).
  • No em or en dashes in on-screen text (they read as AI-written).
  • Facts on screen must be right. Draw the real subject for the topic, not the demo's props.
  • Write original code for every look; never paste third-party source into a style.

Adding or fixing a style

Follow STYLE_CONTRACT.md, keep the primitive signatures identical so scenes can swap styles, verify with landscape and portrait stills, then set built: true in index.json. Run renders one at a time on smaller machines.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.