
Presentations
- 421 installs
- 68 repo stars
- Updated December 30, 2025
- dylantarre/animation-principles
presentations is a Claude Code skill that applies Disney's 12 animation principles to Keynote, PowerPoint, and Google Slides decks so motion guides attention, reinforces story beats, and keeps audiences oriented.
About
presentations is a motion design skill for Claude Code that adapts Disney's 12 animation principles to slide decks built in Keynote, PowerPoint, and Google Slides. The skill maps each principle to presentation techniques such as elastic scaling for emphasis, pre-reveal anticipation builds, staggered element entrances, and slow-in/slow-out easing for readable transitions. It helps developers and technical presenters structure pitch flows and narrative screens where motion reinforces story beats instead of distracting from content. Use presentations when creating or refining deck animations for product launches, investor pitches, or conference talks that need purposeful, audience-oriented motion.
- Story-driven entrance and exit timing
- Attention hierarchy via motion staging
- Smooth transitions between narrative beats
- Brand-consistent animation vocabulary
- Reduced cognitive load during dense slides
Presentations by the numbers
- 421 all-time installs (skills.sh)
- Ranked #666 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dylantarre/animation-principles --skill presentationsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 421 |
|---|---|
| repo stars | ★ 68 |
| Last updated | December 30, 2025 |
| Repository | dylantarre/animation-principles ↗ |
How do you animate presentation slides with purpose?
Design slide decks, pitch flows, and narrative screens with purposeful motion that guides attention, reinforces story beats, and keeps audiences oriented.
Who is it for?
Developers and technical presenters building Keynote, PowerPoint, or Google Slides decks who want principled motion that supports narrative flow.
Skip if: In-game engine animation, web app UI component libraries, or teams that need data analytics rather than slide motion design.
When should I use this skill?
The user creates or refines Keynote, PowerPoint, or Google Slides animations, pitch flows, or presentation motion design.
What you get
Slide transition patterns, staggered build sequences, focal-point staging rules, and story-beat motion cues for pitch decks
- Transition patterns
- Staggered build sequences
- Story-beat motion guide
By the numbers
- Covers Disney's 12 animation principles with presentation-specific implementation tables
Files
Presentation Animation
Apply Disney's 12 animation principles to Keynote, PowerPoint, Google Slides, and presentation software.
Quick Reference
| Principle | Presentation Implementation |
|---|---|
| Squash & Stretch | Bounce emphasis, elastic scaling |
| Anticipation | Build sequences, pre-reveal fades |
| Staging | Focal point management, dimming |
| Straight Ahead / Pose to Pose | Morph vs discrete transitions |
| Follow Through / Overlapping | Staggered builds, delayed elements |
| Slow In / Slow Out | Ease animations, avoid linear |
| Arc | Motion paths, curved entrances |
| Secondary Action | Supporting graphics follow primary |
| Timing | Builds 0.3-0.5s, transitions 0.5-0.8s |
| Exaggeration | Emphasis effects, attention draws |
| Solid Drawing | Consistent alignment, visual balance |
| Appeal | Professional polish, purposeful motion |
Principle Applications
Squash & Stretch: Use bounce effect sparingly for playful emphasis. Scale animations should feel elastic not mechanical. Key numbers can "pop" with slight overshoot.
Anticipation: Fade out previous content before new appears. Slight pause after slide transition before builds begin. Dim existing elements before highlighting new ones.
Staging: One focal point per moment. Dim completed content to 30-50% opacity. Use motion to direct eye path. Build complex diagrams piece by piece.
Straight Ahead vs Pose to Pose: Morph transitions (Keynote Magic Move, PowerPoint Morph) create fluid straight-ahead motion. Standard builds are pose to pose. Use morph for transformation stories.
Follow Through & Overlapping: Build related items with 0.1-0.2s delays. Supporting text follows primary graphic. Bullet points stagger naturally. Don't animate everything simultaneously.
Slow In / Slow Out: Always use ease-in-out or ease-out. Never linear—looks robotic. Keynote: "Ease In & Out". PowerPoint: use custom motion paths with curve handles.
Arc: Motion paths should curve naturally. Elements entering from sides arc inward. Exit animations arc toward edges. Straight lines feel mechanical.
Secondary Action: Icons animate alongside text reveals. Arrows appear as relationships are explained. Background subtle shifts support primary content.
Timing: Text builds: 0.3-0.5s. Graphic reveals: 0.4-0.6s. Slide transitions: 0.5-0.8s. Complex sequences: 0.2-0.3s between elements. Match pacing to speaking rhythm.
Exaggeration: Use scale emphasis for key points. Pulse effect for critical numbers. Shake for contrast/disagreement. Reserve exaggeration for truly important moments.
Solid Drawing: Maintain grid alignment during motion. Consistent transform origins. Elements should feel anchored to the slide structure.
Appeal: Purposeful animation builds credibility. Excessive motion distracts and annoys. Every animation should serve communication.
Software Patterns
Keynote
Best builds: Dissolve, Move In, Scale
Magic Move: Most powerful transition—objects morph between slides
Timing: Use "Build Order" panel for precise sequencing
Tip: Group objects that should animate togetherPowerPoint
Best entrances: Fade, Fly In (with custom path)
Morph transition: Objects with same name transform
Timing: Animation Pane for sequencing
Tip: Use "With Previous" + delay for staggerGoogle Slides
Limited but functional: Fade, Fly in
No morphing: Use Fade for cleanest transitions
Timing: Less control—keep animations simple
Tip: Fewer, better animations beat many poor onesBuild Sequences
| Content Type | Animation | Duration | Delay |
|---|---|---|---|
| Title | Fade + Scale | 0.5s | 0s |
| Subtitle | Fade | 0.4s | 0.2s |
| Bullet 1 | Fade + Move | 0.3s | 0.3s |
| Bullet 2+ | Fade + Move | 0.3s | +0.15s each |
| Image | Scale from center | 0.5s | varies |
| Chart | Custom/Wipe | 0.6s | varies |
Presenter Tips
1. Animate on click, not automatically—control your pacing 2. Practice with animations—know what comes next 3. Less is more—animation should clarify, not decorate 4. Test on presentation display—timing feels different at scale 5. Have a backup with no animations for technical issues
Related skills
FAQ
Which presentation tools does presentations support?
presentations targets Keynote, PowerPoint, Google Slides, and similar deck software, applying Disney's 12 animation principles to transitions, builds, and focal-point staging.
How is presentations different from game-development animation?
presentations focuses on slide deck and pitch flow motion in presentation software, while the sibling game-development skill applies the same principles to interactive engine animations and player feedback.