motion-director
Skill1 starsChanged 47 days agoMITView on GitHub
Use when the user asks to make, design, storyboard, score or animate any motion video: a promo, ad, explainer, product or launch video, brand film, website case study, portfolio reel or showreel, animated deck, a UI animation loop, or a social reel (16:9, 1:1, or 9:16 for Reels, Shorts and TikTok). Also use when they share a website URL, screenshots, a Figma file, a PDF or pitch deck, a screen recording, or only a text brief and want a video made from it; when they ask for kinetic typography, sound effects, a music bed or voiceover on a video; or when adding reference videos to evolve the style. Use it alongside /hyperframes, which stays the render engine, never instead of it.
- Reads credentials
7 other projects use a version of this.
Adopted by
Most recently taken up by
- JimLiu/baoyu-designtheir own version, first seen Nov 8, 2026
- hideewsj-maker/motion-skillstheir own version, first seen Nov 8, 2026
- frankxai/awesome-motion-design-agent-skillstheir own version, first seen Nov 5, 2026
- imMamdouhaboammar/motion-graphics-skillstheir own version, first seen Nov 1, 2026
- sharbelxyz/motion-directortheir own version, first seen Nov 1, 2026
- Rohith2989/motion-directortheir own version, first seen Oct 11, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- JimLiu/baoyu-design★ 6.2ksame name
- frankxai/awesome-motion-design-agent-skills★ 102same name
- imMamdouhaboammar/motion-graphics-skills★ 50same name
- hideewsj-maker/motion-skills★ 1same name
- Rohith2989/motion-director★ 1same name
- BlueSoul2003/motion-director★ 0same name
- sharbelxyz/motion-director★ 0same 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
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Every layout follows these.
- Very specific: line 52
Setup (first video on a machine): If a script fails on a missing tool, run node ~/.claude/skills/motion-director/scripts/doctor.mjs and …
- Very specific: line 57
Intake: If /hyperframes already wrote BRIEF.md, read it and ask nothing it answers.
- Distinctive: line 82
Beat sheet: Use the layout's structure and references/story-structures.md for durations.
- Very specific: line 92
Sound: Write cues.json at the same timestamps as the tweens, run scripts/sound.mjs, and reference assets/audio/mix.wav with an <audio id>.
- Very specific: line 94
Audit and verify: Run references/audit.md, then npx hyperframes lint and check (0 errors), render a draft, look at every beat …
- Very specific: line 102
Every applier is fn(tl, target, at, opts): it adds tweens to your paused timeline at an absolute time and returns the time its move settles.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Motion Director
A motion design system distilled from five reference films plus a personal portfolio reel. It is not one template. Each presents differently, so the skill keeps eight layouts (different structures, pacing, camera, and audio) on top of one shared type-and-motion language, with interchangeable color flavors. Everything runs locally and free by default; API keys are only for optional voice providers.
Division of labor. This skill decides how it looks, moves, and sounds. HyperFrames
(/hyperframes → /general-video, /motion-graphics, /product-launch-video …) builds, checks, and
renders. The handoff is the project's frame.md (read first by HyperFrames, per
hyperframes-creative/references/design-spec.md), the runtime in assets/, and assets/audio/mix.wav.
The shared language: ten laws
Every layout follows these. They're what all five references have in common.
- Type is the lead actor. Lines build word by word (rise + de-blur) or type on behind an accent caret. Text arrives; it never just appears. That's what makes the viewer read.
- One keyword per line. The payoff word gets the accent: a filled pill, marker sweep, selection brackets, or accent color with a heavier weight. Two highlights cancel each other out.
- One accent, full stop. Base (dark or light-neutral) + ink + ONE saturated color. The accent is ~10% of the pixels, except for full-bleed accent panels used as punctuation.
- Weight contrast inside a line. Regular body with a bold/black keyword; single-word hero hits go oversized, all-caps, tight. Serif narration lines are available where the layout calls for them.
- Transitions carry continuity. Morphs, push/pull-throughs, whips, panel wipes, and camera moves. Hard cuts only on the beat; how many is a layout decision (see layouts.md).
- Ride the beat grid. Music BPM (96–128) sets the grid: something changes every beat, a new idea every 1.5–3 s, one breathing hold before the end. Voice layouts follow word timestamps instead.
- Show the real thing. UI cards in 3D, prompts typing, chips popping, real screenshots and dashboards. Proof beats show the work, not stock.
- Atmosphere, never flat. Blurred orbs, grain, glow, vignette. Depth even behind one sentence.
- Every visible landing has a sound. Impacts on slams, pops on chips, keyboard ticks on typing, risers into big moments, a music bed on the grid, voice where the layout is narrated.
- Thread a motif, end on a question. A guide element (spark, dot, caret, mark) leads the eye; close with a brand lockup and a question or call to action.
Workflow
- Setup (first video on a machine). If a script fails on a missing tool, run
node ~/.claude/skills/motion-director/scripts/doctor.mjsand relay its fixes. Whose brand is this? For the user's own brand, use the skill-folderbrand.json; if it doesn't exist, ask for the fields in brand.example.json once and write it there. For a client, writebrand.jsonin the project folder instead, so the user's own brand never leaks into client work. Intake. If
/hyperframesalready wroteBRIEF.md, read it and ask nothing it answers. Get the message, audience, length, aspect, brand, and real assets (screens, footage, numbers). Never invent stats or client names. Route every input with references/intake.md: a URL, a local app, screenshots, a Figma link, a PDF or deck, a screen recording, a logo only, or a text brief with no assets. Runscripts/prep-media.mjson any images you're given. Before picking a layout, write the asset inventory (the block in intake.md) and show it to the user:Asset inventory Have: <each real asset: file · shape · how big it can appear> Missing: <what the story needs that nobody supplied> Build in HTML: <UI or diagrams recreated as code, labeled as concept> Numbers: <every figure on screen and where it came from, or "none">- Pick the layout with references/layouts.md (the choosing table), then
the flavor with references/flavors.md (layout default, a different
flavor, or one derived from the brand;
media-report.jsonsuggests an accent from screenshots). State both picks in one line each. - Scaffold from the matching demo, which is the fastest way to a working piece:
node ~/.claude/skills/motion-director/scripts/scaffold.mjs <project-dir> --demo <layout> [--aspect 9:16] [--brand <file>] [--dry-run](--listshows every demo and its ready-made aspects; it never overwrites existing files). It fills the brand into the copy and seeds any image you haven't supplied with a SAMPLE placeholder: replace every one it lists before the final render. Then writeframe.mdfrom assets/frame-template.md. - Beat sheet. Use the layout's structure and references/story-structures.md for durations; assign moves from references/signature-moves.md. Motion numbers are in references/motion-grammar.md.
- Voice. Narrated layouts, or a sparse line per scene when the user asks for voice. Write
vo.json, runscripts/voice.mjs, get word times withscripts/transcribe.py --words, and land each key word on its visual. Kokoro is the default; if the user wants ElevenLabs or their own cloned voice, set"provider"and follow the consent, licence and cost checks in references/sound-design.md §5 (run--dry-runbefore any paid call). - Build the composition: replace the demo copy and media with the project's, keep the move structure, keep the helpers' determinism rules.
- Sound. Write
cues.jsonat the same timestamps as the tweens, runscripts/sound.mjs, and referenceassets/audio/mix.wavwith an<audio id>. - Audit and verify. Run references/audit.md, then
npx hyperframes lintandcheck(0 errors), render a draft, look at every beat (scripts/beat-frames.mjs <render> --bpm Ntiles one frame per beat), runscripts/transcribe.py <render>.mp4to confirm every voice line is intelligible, and check loudness. Fix, then do the final render.
Runtime (assets/motion-director.js, global MotionDirector)
Every applier is fn(tl, target, at, opts): it adds tweens to your paused timeline at an absolute
time and returns the time its move settles.
| Move | Call | |
| Build a line + keyword | buildSentence(tl, "#line", 0.4, { keyword, highlight: "fill"|"sweep"|"bracket"|"color", times? }) | |
| Exit a line (incl. highlight) | exitSentence(tl, "#line", 2.9) | |
| Typewriter / cycling word | typeOn(tl, el, t, { cps, caret, blinkUntil }) · swapWord(tl, el, ["a.", "b."], t) | |
| Echo type | echoStack(tl, "#hero-word", t, { count: 2 }) (call before tweening the source) | |
| Accent flash / wipes | flashCard(tl, "#flash", t, { hold }) · wipeIn(tl, el, t, { from }) | |
| Hard-cut hit | slam(tl, el, t, { from: 1.2 }) | |
| Transitions | panelPush · whip · zoomThrough · camera(tl, world, t, { scale, x, y }) | |
| UI / product | tiltFloat · chipPop(…, { select }) · slotFocus · countUp · drawPath | |
| UI morph + cursor | morphTo(tl, shape, t, { width, height, borderRadius, backgroundColor }) · contentSwap(tl, old, next, t) · `cursor(tl, el, t, { x, y, click | drag })` |
| Word transitions | textPortal(tl, maskText, t, { origin, overlay }) · listSpin(tl, list, t, { land }) · strikeToUnderline(tl, line, t, { drop }) · breathe (final hold) | |
| Craft add-ons | hudFrame(tl, layer, 0, total, { bpm, chapters, label }) · selectBox(tl, el, box, t) · easeGraph(tl, svg, t, { ease }) | |
| Motif / atmosphere | motifPath(tl, el, [{ x, y } | { to, dx, dy }], t) · ambientDrift | |
| Generic in/out | arrive · leave | |
| Timing math | snapToBeat · beatGrid · readHold(words) · seededRandom · repeatCount |
Determinism (HyperFrames): no clocks, seeded randomness only, finite repeats, set-based typing,
tween transforms/opacity (not letter-spacing), never tween a .clip element's visibility, and
register window.__timelines[id] after the build. Measure elements only in clips active at build
time; otherwise pass coordinates.
Evolving the style
To add a reference, make contact sheets and a cut report (the HyperFrames student kit's
motion-showreel/scripts/analyze-reference.mjs <video> <out-dir> --fps 4 does both; plain
ffmpeg -i ref.mp4 -vf "fps=4,scale=480:270,tile=4x4" sheet_%02d.png covers the sheets), read every
sheet, and run scripts/transcribe.py ref.mp4 to see whether it has voiceover. A new presentation becomes a new layout (plus a demo); a pattern shared
by most references becomes a law.
Files
- references/intake.md: what to do with each kind of input (URL, screenshots, Figma, PDF, footage, brief only) + the asset inventory
- references/layouts.md: the eight layouts (structure, pacing, moves, audio), the HUD add-on, and how to choose
- references/website-case-study.md: recipe + capture rules + gotchas for films that present a website
- references/sound-design.md: cue sheets, SFX palette, music styles, voiceover, loudness
- references/flavors.md: palettes and deriving one from a client brand
- references/design-language.md · references/motion-grammar.md · references/signature-moves.md · references/story-structures.md · references/audit.md
assets/motion-director.js·assets/motion-director.css·assets/fonts/(Inter, Instrument Serif, Dancing Script; OFL) ·assets/frame-template.mdassets/demos/<layout>/(index.html with{{brand.*}}tokens, cues.json, vo.json for voiced ones;<layout>-9x16/and-1x1/for other ready-made aspects) ·assets/demos/MEDIA.md(what each demo image should show) ·assets/demos/_placeholders/(committed SAMPLE media) ·assets/demos/_media/(optional, never committed: your own images, used before the samples)brand.example.json→brand.json(who the video is for;scripts/brand.mjsvalidates and fills it)scripts/doctor.mjs(setup check) ·scripts/scaffold.mjs·scripts/prep-media.mjs(any image in → WebP + shape, size and palette report) ·scripts/sound.mjs·scripts/voice.mjs(+scripts/voice/providers,scripts/env.mjsfor keys,.env.example) ·scripts/capture-site.mjs·scripts/beat-frames.mjs(one frame per beat, tiled) ·scripts/transcribe.py·scripts/make-placeholders.mjs(maintainers only)- PROMPTS.md: copy-paste prompts for users
- Tests:
node --test tests/*.test.mjs
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
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.

