kinematic-motion-choreography
Skill4 starsChanged 3 months agoMITView on GitHub
Designs physics-based UI motion systems using harmonic spring oscillator equations (mass, stiffness, damping), asymmetric entrance/exit curves, staggered cascading delays, and mandatory reduced-motion fallbacks. Use when: spring animation, physics motion, cubic-bezier, enter exit animation, staggered list animation, modal transition, interactive gestures, agentway gen:spring.
In this repository46 other files it gives its agents.
- accessibility-reviewSkill
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- business-model-thinkingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-layout-patternsSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-system-builderSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- product-strategySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- security-privacy-reviewSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-hierarchy-reviewSkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Never use the same timing curve for entrances and exits:
- Distinctive: line 62
When animating collections (lists, grids, dashboard widgets): $$t_{\text{delay}}(n) = \min(n \times 35\text{ms}, 350\text{ms})$$ Cap total …
- Distinctive: line 68
Ensure motion originates from the trigger element:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
🌊 Skill: Kinematic Motion Choreography
Purpose
Standard web transitions often feel robotic because they use arbitrary linear or symmetrical curves (ease-in-out). Real-world physical objects possess mass, friction, and momentum. This skill equips agents with harmonic oscillator physics and asymmetric choreography protocols to create natural, high-performance UI motion.
Trigger Phrases
| Phrase | Activation |
| "spring animation" / "spring physics" | ✅ |
| "asymmetric motion" / "enter exit animation" | ✅ |
| "staggered animation" / "choreography" | ✅ |
| "modal animation" / "drawer physics" | ✅ |
| "kinematic tokens" / "motion curves" | ✅ |
| "agentway gen:spring" | ✅ |
Protocol: 5-Step Kinematic Motion Engine
STEP 1 — Physical Parameter Definition
Define the harmonic oscillator parameters for each UI element category:
- Mass ($m$): Weight of the element ($0.5\text{kg}$ for tooltips, $1.0\text{kg}$ for cards, $2.0\text{kg}$ for dialog modals).
- Stiffness ($k$): Spring tension/snap ($120\text{N/m}$ to $400\text{N/m}$).
- Damping ($c$): Friction resisting motion ($10\text{Ns/m}$ to $35\text{Ns/m}$).
$$\text{Damping Ratio } \zeta = \frac{c}{2\sqrt{km}}$$
- Snappy Spring ($\zeta \approx 0.65$): Micro-interactions, button presses, like animations.
- Natural Smooth ($\zeta \approx 0.85$): Dropdowns, tooltips, toasts, tab indicators.
- Critically Damped ($\zeta = 1.0$): Heavy modals, route transitions (Zero overshoot).
STEP 2 — Asymmetric Directional Choreography
Never use the same timing curve for entrances and exits:
- Entrances (High Energy Deceleration):
- Duration: Fast ($150\text{ms}–220\text{ms}$).
- Curve:
cubic-bezier(0.16, 1, 0.3, 1)(Decelerates sharply as it snaps into place).
- Exits (Deliberate Acceleration):
- Duration: Slightly slower ($250\text{ms}–320\text{ms}$).
- Curve:
cubic-bezier(0.7, 0, 0.84, 0)(Accelerates off-screen so user isn't kept waiting).
STEP 3 — Cascading Stagger Calculations
When animating collections (lists, grids, dashboard widgets): $$t_{\text{delay}}(n) = \min(n \times 35\text{ms}, 350\text{ms})$$ Cap total stagger at $350\text{ms}$ so large lists don't introduce perceived latency.
STEP 4 — Gestural Spatial Cohesion
Ensure motion originates from the trigger element:
- Modals scale up from the click origin (
transform-origin: var(--origin-x) var(--origin-y)). - Menus expand outward from the trigger button icon.
STEP 5 — Accessibility & Reduced Motion Gate
Mandate strict reduced-motion overrides:
@media (prefers-reduced-motion: reduce) {
*, *::before, *::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
}
}Deliverables Generated
spring-tokens.css— CSS Custom Properties with mathematical Bezier approximations.motion-choreography.js— Lightweight spring timing helper.CHOREOGRAPHY-TIMELINE.md— Visual timeline diagram of micro-interactions.
Companion Skills
| Skill | Relationship |
micro-interaction-motion-design | Sets foundation duration tokens |
touch-gesture-interaction | Connects gesture velocity to spring release |
perceived-performance-loading | Coordinates skeleton reveal transitions |
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.

