I packaged motion design taste + tool knowledge into four Claude Code skills so I'd stop re-explaining the basics every session. Free, MIT, ~15-min install.
The problem
Generative AI is great at "a thing moves." It's bad at why it moves that way. Every session I'd re-explain easing, stagger, anticipation, follow-through — the stuff a senior motion designer internalizes. So I moved that knowledge into skills Claude loads automatically.
What it is Four skills:
motion-design — tool-agnostic foundation (principles, easing, timing, composition)
aftereffects-motion — ExtendScript/JSX, expressions, text + shape animation, render
blender-motion — bpy keyframing, materials, lighting, cameras, geometry nodes
motion-design-critique — diagnostics for when something looks wrong or a script throws
How it's built
SKILL.md vs references split. The SKILL.md is a thin behavior contract; the heavy knowledge lives in lazy-loaded reference files. Keeps the trigger surface clean.
Two execution modes for AE. Single live MCP commands for small tweaks, generated JSX for anything multi-step.
Idempotent everything. Scripts clean up before they build, so re-running never stacks duplicates.
Works without MCP. No AE/Blender attached? You still get planning and critique.
Install
Clone, optionally install the AE/Blender MCP servers, copy the skills into ~/.claude/skills/. Full steps in the README.
Repo: github.com/LobzyJay/motion-design-with-claude
If you're building skills for a non-dev creative domain, I'd love to compare notes in the comments
Top comments (0)