motion-film
Skill2 starsChanged 46 days agoMITView on GitHub
Produce a professional motion video (product film, advert, explainer or tutorial) as deterministic code: authored vector scenes in HTML canvas, a frame-exact timeline, original synthesized sound, FFmpeg render and measured QC. Use when someone asks for a marketing video, an ad, a launch film, an educational explainer, a social cut (16:9, 9:16, 1:1) or a motion study, and wants a finished MP4 they can publish, not a storyboard alone.
- Installs packages
3 other projects use a version of this.
Adopted by
Most recently taken up by
- arhen/motion-filmtheir own version, first seen Nov 8, 2026
- tonyprots/motion-film-skilltheir own version, first seen Oct 11, 2026
- Neelshah1810/Claude-Video-Skillstheir own version, first seen Oct 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- arhen/motion-film★ 11same name
- tonyprots/motion-film-skill★ 7same name
- Neelshah1810/Claude-Video-Skills★ 6same 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
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read references/process.md before starting.
- Distinctive: line 15
Truth boundaries: Every claim on screen is either true today, labelled ("Illustration", "Planned", "Testnet", "Example figures"), or cut.
- Very specific: line 18
Deterministic time: Every scene reads only t. No Date.now(), no requestAnimationFrame state, no unseeded randomness.
- Distinctive: line 20
Readable holds: After every material statement, hold long enough to read it twice on a phone: about 0.3 s per word, never under 1.2 s for a …
“Common” is measured: kept by at least 6 in 10 of the 3 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 film
A film made the way software is made: a script that becomes a timeline, scenes that are pure functions of time, a renderer that captures every frame, and a QC report that proves the export. Nothing depends on playback speed, so the same source always renders the same film.
Read references/process.md before starting. It holds the gates. The other references are loaded when their phase begins.
The non-negotiables
- Approval gates. Brief, then direction, then script and storyboard, then a 6 to 8 second motion study, then the full build. Never render the full film before the motion study is approved. A change of direction after the study costs minutes; after the build it costs hours.
- Truth boundaries. Every claim on screen is either true today, labelled ("Illustration", "Planned", "Testnet", "Example figures"), or cut. No invented customers, metrics, testimonials, partner logos or prices. Write the boundaries down in the brief and check every frame against them at QC.
- Original pixels and sound. Authored vector art, the client's real logo and fonts, original synthesized foley and score. References are studied for pacing and devices, never copied. No stock footage, stock music or generated imagery unless the client asks for it in writing, and then credited.
- Voice. The client's recorded voice by default. A synthetic voice only with explicit approval, and its licence is stated in the delivery notes. Captions are taken from the delivered audio, never from the script.
- Deterministic time. Every scene reads only
t. NoDate.now(), norequestAnimationFramestate, no unseeded randomness.window.setTime(t)draws frametexactly. - Object continuity. Each transition carries an object or idea from one scene into the next (a message becomes an agreement, a receipt becomes a record). A cut between unrelated cards is a slideshow, not a film.
- Readable holds. After every material statement, hold long enough to read it twice on a phone: about 0.3 s per word, never under 1.2 s for a line that matters.
- Measure, don't eyeball. Deliver
qc.json(frames, duration, codec, dimensions, hash, decoder errors),audio-qc.txt(integrated loudness, true peak) and a contact sheet. A film is done when QC passes and the frames have been looked at, not when the encode finishes.
Workflow
| Phase | Output | Reference |
| 1 Brief | Goal, audience, channel, length, aspect ratios, voice, truth boundaries, brand assets, deadline | process.md |
| 2 Reference study | Contact sheets and dense frame strips of each reference, notes on pacing and devices | process.md |
| 3 Directions | Two to four directions, each with a one-line idea, a time table, motion character and truth boundary | formats.md |
| 4 Script and storyboard | Spoken lines or on-screen text per beat, with timings | formats.md |
| 5 Motion study | 6 to 8 s at final finish, rendered | motion-grammar.md |
| 6 Build | film.js scenes on the approved timeline | motion-grammar.md |
| 7 Sound | Foley, score, voice placement, ducking, loudness | sound-design.md |
| 8 Render | Silent master, mixed master, sound-only, captions, social cuts | templates/render.cjs |
| 9 QC and delivery | qc.json, audio-qc.txt, contact sheet, transition strips, poster, notes | qc-checklist.md |
Starting a film
Copy templates/ into a new working folder, then:
npm install # playwright-core for headless Chromium
npx playwright install chromium
node render.cjs proof # stills at the times listed in film.config.json
node render.cjs study # the motion study window only
node render.cjs render # full silent master, then sound.cjs, then the mix
node render.cjs qc # measured checks and contact sheetsfilm.config.json holds title, size, fps, duration, proof times and the study window. film.js holds the scenes. sound.cjs writes the original sound bed from cue times. mix.cjs places voice clips and normalises loudness.
Open film.html in a browser while building: Space plays and pauses, arrow keys seek one second, , and . step one frame.
Formats
- Advert (6 to 30 s): one product, one benefit, one action. Hook in the first second, logo and call to action held for at least 2 s at the end.
- Marketing film (30 to 60 s): one person, one situation, one change. A beginning, a turn and an ending; the product earns its entrance.
- Educational explainer (60 to 180 s): chapters with numbered titles, a running example with consistent figures, diagrams where every line means something, a recap.
- Tutorial: real product captures for the actions that need proof, authored scenes for the ideas a recording cannot show.
Details, time tables and script patterns are in references/formats.md.
When to stop and ask
- The brief has no truth boundary for a claim the script needs.
- A reference would have to be copied to meet the request.
- The client asks for a synthetic voice, stock music or generated imagery without stating the licence.
- Render resources are short (under 3 GB free memory): render on a remote machine or in a bounded container, one render at a time.
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.

