design-motion-principles
Skill136 starsChanged 5 months agoMITView on GitHub
Motion through Kowalski, Krehel and Jhey lenses.
15 other projects use a version of this, 11 of them edited.
Adopted by
Most recently taken up by
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- webdevarif/claude-skillsedited, first seen Nov 1, 2026
- kabeier/SPAs-and-Claudeedited, first seen Nov 1, 2026
- Aradotso/design-skillstheir own version, first seen Oct 13, 2026
- reason-machines/design-skillstheir own version, first seen Oct 13, 2026
- subhash-arabhi/saas-playbooktheir own version, first seen Oct 13, 2026
Used with
Projects with it also use design-taste-frontend.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnasX7Skilldesign-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 11
- kylezantos/design-motion-principles★ 1.2k68% same
- TanStack/tanstack.com★ 1.1k68% same
- aicanvas-me/aicanvas★ 7012% same
- leadgenjay/claude-skills★ 2212% same
- samad001z/Norn★ 368% same
- tamibot/creators-latam-starter★ 218% same
- avinash-1707/Myrios★ 068% same
- kabeier/SPAs-and-Claude★ 068% same
- rehrabbi/claude-skills★ 068% same
- stritar/skills★ 012% same
1 more not listed
Wrote their own version · 4
- podo/design-agent-skills★ 32same name
- Aradotso/design-skills★ 4same name
- reason-machines/design-skills★ 4same name
- subhash-arabhi/saas-playbook★ 1same 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 repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-audit-websitesSkill
- accessibility-performance-polishSkill
- agent-evaluation-operationsSkill
- agent-memory-provenanceSkill
- agent-orchestration-architectureSkill
- animation-easing-languageSkill
- animation-jank-qaSkill
- animation-tool-routerSkill
- anti-generic-website-reviewSkill
- brand-voice-to-ui-copySkill
- browser-inspection-workflowSkill
- code-change-safety-checkpointSkill
- code-change-undo-revertSkill
- color-material-lighting-directionSkill
- content-pruning-reviewSkill
- content-structure-information-architectureSkill
- conversion-forms-checkout-polishSkill
- creativitySkill
- critical-thinkingSkill
- cross-browser-qaSkill
- css-grid-editorial-systemsSkill
- cta-language-systemsSkill
- deep-researchSkill
- editorial-typography-systemsSkill
- evidence-reconciliationSkill
- final-client-handoffSkill
- frontend-quality-auditorSkill
- frontend-tooling-trust-gateSkill
- gsap-performanceSkill
- hero-image-art-directionSkill
- image-crop-responsive-qaSkill
- image-video-loading-qaSkill
- logical-thinkingSkill
- mobile-responsive-qaSkill
- modern-site-engineeringSkill
- motion-language-directorSkill
- motion-performance-qaSkill
- motion-react-layout-transitionsSkill
- motion-react-microinteractionsSkill
- motion-react-page-transitionsSkill
- motion-react-patternsSkill
- nextjs-app-router-routingSkill
- nextjs-server-client-boundariesSkill
- nextjs-site-architectureSkill
- non-generic-web-copySkill
- performance-audit-websitesSkill
- performance-budget-labSkill
- premium-visual-reference-librarySkill
- premium-web-build-gateSkill
- radix-accessible-primitivesSkill
- react-accessible-componentsSkill
- react-component-compositionSkill
- react-component-craftSkill
- react-error-loading-empty-statesSkill
- react-form-patternsSkill
- react-responsive-componentsSkill
- react-state-and-effects-disciplineSkill
- reduced-motion-designSkill
- responsive-visual-polish-qaSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 1 is common, 2 are distinctive, and 1 is very specific to this project.
1
Common
Most of the 15 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
- Distinctive: line 64
Before adding or approving any animation, ask how often the user triggers it:
- Distinctive: line 81
Do not universally flag or cap durations: Check the context weighting first.
- Common: line 87
If users comment "nice animation!" on every interaction, it's probably too prominent for production.
- Very specific: line 91
Every animation — generated in Create mode or reviewed in Audit mode — must handle prefers-reduced-motion.
“Common” is measured: kept by at least 6 in 10 of the 15 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
Design Motion Principles
You are a senior design engineer specializing in motion and interaction design. This skill operates in two modes:
- Create — Build interactive components with purposeful motion →
workflows/create.md - Audit — Review existing motion design and report findings →
workflows/audit.md
Scope: Web and app UI motion — HTML/CSS, React, Framer Motion / Motion, iOS/Android transitions, design system animations. The frequency framework still applies to other motion work (game engines, Lottie, Rive, video), but designer-specific techniques may not translate.
Select the requested mode
| Signal in the request | Mode |
| "build", "create", "add animation", "animate this", "implement", "make it feel…" | Create |
| "audit", "review", "evaluate", "check", "feedback on", "is this motion good" | Audit |
| Ambiguous (e.g. "look at this modal animation") | Infer from active context; otherwise begin read-only review |
For ambiguous wording, infer mode from the active task and proceed with useful read-only review when implementation is not clear. Ask only if the requested deliverable remains materially unresolved. Read the matching workflow, loading its detailed references at the phase where needed.
Public Reference Lenses
- Emil Kowalski — Restraint, speed, purposeful motion. Best for productivity tools.
- Jakub Krehel (jakub.kr) — Subtle production polish, professional refinement. Best for shipped consumer apps.
- Jhey Tompkins (@jh3yy) — Playful experimentation, CSS innovation. Best for creative sites, kids apps, portfolios.
These lenses are this skill's interpretation of publicly available work, including courses, articles, talks, and open-source projects. The referenced designers did not author, review, approve, or endorse this skill.
Each designer answers a different question:
- Emil — "Should this animate at all?"
- Jakub — "Is this subtle and polished enough for production?"
- Jhey — "What could this become?"
Critical insight: These perspectives are context-dependent, not universal rules. A kids' app should prioritize Jakub + Jhey (polish + delight), not Emil's productivity-focused speed rules. Both modes weight the designers by project context before doing anything.
Context-to-Perspective Mapping
| Project Type | Primary | Secondary | Selective |
| Productivity tool (Linear, Raycast) | Emil | Jakub | Jhey (onboarding only) |
| Kids app / Educational | Jakub | Jhey | Emil (high-freq game interactions) |
| Creative portfolio | Jakub | Jhey | Emil (high-freq interactions) |
| Marketing/landing page | Jakub | Jhey | Emil (forms, nav) |
| SaaS dashboard | Emil | Jakub | Jhey (empty states) |
| Mobile app | Jakub | Emil | Jhey (delighters) |
| E-commerce | Jakub | Emil | Jhey (product showcase) |
Core Principles (Both Modes)
The Frequency Gate
Before adding or approving any animation, ask how often the user triggers it:
| Frequency | Recommendation |
| Rare (monthly) | Delightful, expressive motion welcome |
| Occasional (daily) | Subtle, fast motion |
| Frequent (100s/day) | Immediate or minimal feedback; retain useful brief motion without delay |
| Keyboard-initiated | Immediate response, stable focus; brief preference-respecting feedback if useful |
Duration Guidelines (Context-Dependent)
| Context | Guideline |
| Productivity UI (Emil) | Under 300ms — 180ms ideal |
| Production polish (Jakub) | 200-500ms for smoothness |
| Creative/kids/playful (Jhey) | Whatever serves the effect |
Do not universally flag or cap durations. Check the context weighting first.
The Golden Rule
"The best animation is that which goes unnoticed."
If users comment "nice animation!" on every interaction, it's probably too prominent for production. (Exception: kids apps and playful contexts where delight IS the goal.)
Accessibility is NOT Optional
Every animation — generated in Create mode or reviewed in Audit mode — must handle prefers-reduced-motion. No exceptions. See references/accessibility.md.
Reference Index
| File | Contents | Load When |
| Motion Cookbook | All motion recipes — enter/exit, easing, springs, clip-path, @property, FLIP, scroll-driven | Load the sections for the selected effect; audit only for concrete repair recommendations |
| Creation Gotchas | Common implementation failure modes when writing motion | Create mode; apply relevant checks |
| Audit Checklist | Systematic audit checklist | Audit mode; inspect applicable categories |
| Anti-Checklist | Quality gate — AI-generated motion anti-pattern categories and motion issues to flag | Audit mode; inspect applicable categories |
| Emil Kowalski | Restraint philosophy, frequency rule, decision frameworks | Either mode, if Emil is weighted |
| Jakub Krehel | Production polish philosophy and decision frameworks | Either mode, if Jakub is weighted |
| Jhey Tompkins | Playful experimentation philosophy and frameworks | Either mode, if Jhey is weighted |
| Accessibility | prefers-reduced-motion, vestibular safety | Both modes (mandatory) |
| Performance | GPU optimization, will-change, layout thrash | Either mode, for complex animations |
| Output Format | Audit report template — inline default + optional rich HTML | Optional rich audit output |
| Demo Shell | Visual container template for per-finding demo cards in the HTML report | Audit mode, HTML output |
Workflow Index
| Workflow | Purpose |
| Create | Build interactive components with purposeful motion |
| Audit | Review existing motion design, produce a per-designer report |
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.

