presentations
Use when creating Keynote, PowerPoint, Google Slides animations, or any presentation motion design work.
What this skill does
# 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 together ``` ### PowerPoint ``` 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 stagger ``` ### Google 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 ones ``` ## Build 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 in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.