motion-craft
Skill1 starsChanged 42 days agoMITView on GitHub
Motion-design law for Remotion - rules, patterns, verify loop.
- Installs packages
6 other projects use a version of this.
Adopted by
Most recently taken up by
- XuHo-IT/Content-Agent-Kittheir own version, first seen Nov 8, 2026
- EnamTiga/motion-crafttheir own version, first seen Nov 8, 2026
- sithumdgomez/claude-skillstheir own version, first seen Oct 11, 2026
- jakubsuplicki/codumenttheir own version, first seen Oct 4, 2026
- propiter/motion-crafttheir own version, first seen Jun 15, 2026
- augchan42/inkstonetheir own version, first seen Jun 7, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- jakubsuplicki/codument★ 48same name
- augchan42/inkstone★ 5same name
- XuHo-IT/Content-Agent-Kit★ 3same name
- EnamTiga/motion-craft★ 1same name
- propiter/motion-craft★ 1same name
- sithumdgomez/claude-skills★ 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.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aegntic-videoSkill
- live-demoSkill
- remotion-coreSkill
- shotcraft-cardsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
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
- Very specific: line 21
No linear interpolation: Every interpolate() gets an easing curve.
- Distinctive: line 39
Render, extract frames, look at them, fix, re-render: Never deliver an unverified render.
- Distinctive: line 82
Look at every extracted frame.
“Common” is measured: kept by at least 6 in 10 of the 6 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 craft
Remotion renders React components frame-by-frame. Code quality is not the bottleneck; motion-design craft is. Untrained output has linear easing, opacity-only fades, simultaneous entrances, flat colors, no texture - the generic AI-video look. This skill is the cure. Read it fully before writing any Remotion code.
Ten non-negotiable rules (apply to every composition)
- No linear interpolation. Every
interpolate()gets an easing curve; entrances preferspring(). AlwaysextrapolateLeft/Right: "clamp". - Entrances animate 2-3 properties together (opacity + translateY + scale). A lone fade is forbidden.
- Stagger everything. Lists, words, cards: 3-6 frame offsets. Nothing enters simultaneously.
- Exits exist and are faster than entrances (~10 frames vs ~20).
- Five-layer stack in every scene, bottom to top: background mesh -> assets -> graphics/type -> color grade -> grain + vignette. Never a flat solid background.
- Every still gets Ken Burns (slow scale 1 -> 1.08 + pan). Every video
asset uses
<OffthreadVideo>, never<Video>. - Idle elements breathe: anything on screen over 2s gets sin-wave micro-motion.
- All timing derives from
fpsviauseVideoConfig(). No magic frame numbers. - One theme object (colors, easings, spring presets, fonts) at the top of the project. Never inline a hex color or easing in a component.
- Render, extract frames, look at them, fix, re-render. Never deliver an unverified render.
Setup
npm install remotion @remotion/cli react react-dom
# optional: @remotion/transitions @remotion/motion-blur @remotion/google-fontsCopy this skill's assets/theme.ts into src/theme.ts, adjust the palette
to the brand. Structure: src/index.ts (registerRoot) -> src/Root.tsx
(Composition with duration/fps/size) -> src/scenes/*.tsx ->
src/components/*.tsx.
Scope first: duration, fps (30 default; 60 only for heavy fast motion),
dimensions (1080x1920 vertical, 1920x1080 landscape), what assets exist, and
whether this is a new composition or an edit. When editing an existing
project, read src/ fully, find or create the theme, and fix rule
violations before adding features.
Component library
references/motion-patterns.md has working implementations: premium
entrance, staggered children, word-by-word reveal, background mesh, color
grade, procedural grain, vignette, Ken Burns, counters, sparks, exits,
breathing, parallax, transitions. Import theme from the project's
src/theme.ts. Read it before writing components. Both reference files are
vendored from haidrrrry/claude-remotion-skill
(MIT) with notice.
references/design-rules.md has palettes, typography, pacing, sound design,
and the pre-delivery checklist. Read it before designing scenes and again
before final delivery.
Verification loop (mandatory, never skip)
npx remotion render src/index.ts <CompId> out/video.mp4 --codec h264 --crf 17
ffmpeg -v error -i out/video.mp4 \
-vf "select='eq(n\,15)+eq(n\,45)+eq(n\,90)+eq(n\,N-10)'" -vsync 0 check_%d.pngLook at every extracted frame. Fix, in order of frequency:
- Spacing bugs:
gap/margininemresolves against the parent font size, not the text size - use px in flex containers around large type. - Text overflowing or touching frame edges (keep critical content in the middle 75% vertically for 9:16 - platform UI covers the extremes).
- Elements visible before their entrance or after their exit (missing clamp).
- Color/contrast failures: at most one hero-colored element per frame; dim text unreadable over the grade.
- Layer order mistakes: grain and vignette on top, grade above content.
Fix, re-render, re-extract, re-inspect. Only deliver after a clean pass, then
run the checklist at the end of references/design-rules.md.
Escalation path
Need a specific shot treatment (camera move, data viz, typographic effect)?
Load shotcraft-cards and pick a recipe card. Need current framework API?
Load remotion-core. Building on real captured pages? Capture first
(shotcraft-cards capture script or the live-demo lane), then compose
here.
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.

