Not another motion checklist — a panel. The skill distills the published work of three motion designers into three attributable lenses that each answer a different question: Emil Kowalski asks “should this animate at all?”, Jakub Krehel asks “is this subtle and polished enough for production?”, and Jhey Tompkins asks “what could this become?” The sharp idea is that the lenses are weighted by project context before anything else happens — a productivity tool leads with Emil, a kids’ app leads with Jakub and Jhey — which turns “it depends” from a shrug into an actual lookup table.
The frequency gate is the hardest-working rule in it: rare interactions earn expressive motion, daily ones get subtle-and-fast, hundred-times-a-day ones get nothing, and keyboard-initiated actions never animate. Two modes — Create builds components with purposeful motion, Audit reviews existing motion and emits a self-contained HTML report with looping demos of each finding.
There’s a meta angle for Canon readers: two of the three distilled designers are already in this gallery first-hand (Emil’s Improve Animations and Design Eng skills, Jakub’s Make Interfaces Feel Better). This is the synthesis view — useful precisely when you want the voices weighed against each other rather than one philosophy applied pure.
Install: the repo bundles a skills/ folder — copy skills/design-motion-principles/ into your .claude/skills/ directory (references and workflows come with it).
Gotcha: the author is explicit that the lenses are his interpretation of each designer’s published work, “named in tribute; not authored or endorsed by the designers themselves.” Honest framing, worth knowing before you cite a finding as “what Emil would say.”