
slow-in-out-mastery
Use when designing easing curves, controlling motion pacing, creating natural acceleration/deceleration, or making movements feel physically grounded.
- Installs
- 521
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/dylantarre/animation-principles --skill slow-in-out-mastery- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads slow-in-out-mastery automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Slow In / Slow Out Mastery
The Physics Principle
Objects in the real world don't move at constant speeds—they accelerate from rest and decelerate to stops. Slow in/slow out (also called ease in/ease out) captures this fundamental truth. Without it, animation looks mechanical. With it, motion feels alive.
Core Theory
Slow Out (Ease Out): More drawings clustered at the start of a movement. The object accelerates away from its starting position gradually.
Slow In (Ease In): More drawings clustered at the end of a movement. The object decelerates into its final position gradually.
Linear motion: Equal spacing between positions. Rare in nature, useful for mechanical elements or stylistic choice.
The Spacing Principle
Traditional animators controlled this through drawing spacing:
- Tight spacing = slow movement (drawings close together)
- Wide spacing = fast movement (drawings far apart)
Digital animators control this through easing curves—mathematical functions that describe how values change over time.
Common Easing Functions
- Ease Out: Fast start, slow end (70% of UI animations)
- Ease In: Slow start, fast end (exits, departures)
- Ease In Out: Slow start and end (elegant, deliberate)
- Linear: Constant rate (mechanical, looping)
- Custom bezier: Precise control for specific feels
Interaction with Other Principles
Timing is modified by easing: The same duration feels different with different easing. Ease out feels faster than ease in at identical durations.
Anticipation often uses ease in: The wind-up accelerates before the fast action.
Follow through uses ease out: Settling motion decelerates to rest.
Squash/stretch intensity follows easing: More deformation during fast phases, less during slow phases.
Domain Applications
UI/Motion Design
- Page transitions: Ease out for entrances (fast appearance, settle), ease in for exits
- Modals: Ease out scale-up for friendly, non-jarring appearance
- Buttons: Ease out on press feedback (immediate response, smooth settle)
- Loading: Linear for progress bars (predictable), ease for spinners (organic)
- Hover states: Quick ease out to start, ease in out for smooth feel
Character Animation
- Jumps: Slow out from ground (acceleration), slow in to peak (deceleration), fast middle
- Head turns: Slow out from rest, slow in to new direction
- Blinks: Fast down (almost linear), slow out up (lids dragging)
- Weight shifts: Heavy easing reflects mass
Motion Graphics
- Text reveals: Staggered ease outs create cascading arrivals
- Logo animations: Carefully crafted curves define brand personality
- Data visualization: Ease out for growth, ease in for decrease
Game Feel
- Camera movement: Ease in out for cinematic, quick ease out for responsive
- Character control: Ease curves define how "tight" or "floaty" movement feels
- Impact effects: Sharp ease in creates punch
Common Mistakes
- Linear everything: Motion feels robotic and sterile
- Too much easing: Overly soft motion feels sluggish, unresponsive
- Wrong easing direction: Ease in on entrances feels reluctant; ease out on exits feels like the element doesn't want to leave
- Ignoring context: Playful UIs need bouncier curves; professional UIs need subtler easing
The Bounce and Elastic Extensions
Beyond basic easing:
- Bounce: Overshoot with diminishing oscillation (playful, energetic)
- Elastic: Overshoot with wobble (stretchy, cartoony)
- Back: Slight pullback before motion (adds anticipation)
The 80/20 Rule
For most UI work: use ease out for 80% of animations (elements responding to user action). Ease out communicates responsiveness—"I heard you and I'm moving." Reserve ease in for departures and de-emphasis.
Implementation Heuristic
Default to ease out (fast start, slow end) for element appearances and responses. Use ease in for exits. Use ease in out for autonomous animations (not triggered by user). Adjust curve intensity based on brand personality—aggressive curves for dynamic brands, subtle curves for calm brands.
FAQ
What does the slow-in-out-mastery skill do?
Use when designing easing curves, controlling motion pacing, creating natural acceleration/deceleration, or making movements feel physically grounded.
How do I install slow-in-out-mastery?
Run npx skills add https://github.com/dylantarre/animation-principles --skill slow-in-out-mastery in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/slow-in-out-mastery/ (personal) or .claude/skills/slow-in-out-mastery/ (project).
Which AI agents can use slow-in-out-mastery?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is slow-in-out-mastery safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains slow-in-out-mastery?
It is published by dylantarre in dylantarre/animation-principles. It has 521 recorded installs.
More from dylantarre/animation-principles
video-motion-graphics
dylantarre/animation-principles
Use when creating After Effects compositions, Premiere Pro motion, video titles, explainer videos, or broadcast motion graphics.
mobile-touch
dylantarre/animation-principles
Use when designing iOS/Android gestures, haptic feedback, touch interactions, or native mobile animations.
framer-motion
dylantarre/animation-principles
Use when implementing Disney's 12 animation principles with Framer Motion in React applications
motion-designer
dylantarre/animation-principles
Use when designing visual motion systems, creating animation specifications, or when a designer needs guidance on crafting beautiful, meaningful movement.
micro-interactions
dylantarre/animation-principles
Use when designing small UI feedback moments like button states, toggles, form validation, loading indicators, or notification badges.
web-motion-design
dylantarre/animation-principles
Use when building CSS animations, JavaScript transitions, React/Vue motion, or any browser-based animation work.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.