Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
madteacher avatar

Flutter Animations

  • 14.7k installs
  • 105 repo stars
  • Updated May 1, 2026
  • madteacher/mad-agents-skills

Flutter Animations is a skill covering five animation patterns in Flutter with code templates and performance guidance for building smooth, responsive motion.

About

Flutter Animations is a comprehensive guide to motion and transitions in Flutter apps. It covers implicit animations (AnimatedContainer, TweenAnimationBuilder) for simple cases, explicit animations (AnimationController, Tween) for full control, hero transitions for shared elements, staggered effects for sequential motion, and physics-based animations for natural movement. Developers use it to add polish and visual feedback to Flutter UIs.

  • Covers 5 animation types: Implicit, Explicit, Hero, Staggered, and Physics-based
  • Ready-to-use Dart templates for each animation pattern
  • Comprehensive reference docs on curves, spring simulations, and performance trade-offs

Flutter Animations by the numbers

  • 14,737 all-time installs (skills.sh)
  • +92 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #13 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
At a glance

flutter-animations capabilities & compatibility

Capabilities
ui animation · motion design
Use cases
frontend
npx skills add https://github.com/madteacher/mad-agents-skills --skill flutter-animations

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs14.7k
repo stars105
Security audit3 / 3 scanners passed
Last updatedMay 1, 2026
Repositorymadteacher/mad-agents-skills

What it does

Flutter Animations is a comprehensive guide to motion and transitions in Flutter apps. It covers implicit animations (AnimatedContainer, TweenAnimationBuilder) for simple cases, explicit animations (

Who is it for?

Adding motion effects, transitions, hero animations, and physics-based movement to Flutter apps

Skip if: Server-side or backend animation

When should I use this skill?

Implementing animations in Flutter, choosing between animation approaches, or fixing animation performance

What you get

Smooth, performant animations implemented with correct patterns for the specific use case

  • Animated widget implementations
  • Navigation transition handlers
  • Interaction feedback animations

By the numbers

  • Covers 5 animation categories: Implicit, Explicit, Hero, Staggered, Physics-based
  • Provides 4+ code templates: implicit_animation.dart, explicit_animation.dart, hero_transition.dart, staggered_animation.

Files

SKILL.mdMarkdownGitHub ↗

Flutter Animations

You are a Flutter motion implementation specialist. Build animation changes that fit the app's existing widget structure, state model, navigation, theme, and performance constraints.

Principle 0

Motion must not become hidden state or unverified demo code. Before adding or changing animation logic, inspect the target widget, lifecycle, route structure, and existing patterns. After the change, verify analyzer-clean Dart and call out any animation behavior that could not be run or visually checked.

Workflow

1. Identify the user's actual request: add a new animation, fix a broken one, refactor animation code, debug jank/lifecycle behavior, explain a pattern, or provide a standalone example. 2. Inspect the local Flutter context first when code is available: widget tree, state management, navigation approach, assets, tests, theming, accessibility helpers, and existing animation abstractions. 3. Choose the smallest animation model that satisfies the behavior:

  • Use implicit animations for simple state-driven property changes.
  • Use explicit animations for lifecycle control, repeated/reversible motion,

gestures, multiple coordinated properties, or custom transitions.

  • Use Hero for shared elements across route transitions.
  • Use staggered animation when multiple elements need sequenced or

overlapping timing.

  • Use physics when motion depends on velocity, springs, dragging, flings, or

scroll-like behavior. 4. Implement in the app's style. Preserve existing public APIs unless the user asked for a refactor. Keep controllers owned by the state object that owns the animation lifecycle, dispose them, and avoid creating animation state inside build methods. 5. Prefer production animation patterns: AnimatedBuilder, AnimatedWidget, built-in transitions, child caching, stable keys, and small rebuild regions. Use setState() in animation listeners only for minimal examples or when no narrower rebuild path is practical. 6. Respect accessibility and user settings. Check MediaQuery.disableAnimations or existing reduced-motion policy for non-essential motion, and provide a fast/static path when motion can distract or harm usability. 7. Validate with the strongest available local checks. At minimum, run analyzer on touched Dart files or the relevant Flutter project. Run widget/golden or integration tests when animation behavior, navigation, or gestures are part of the requested change.

Decision Guide

NeedDefault approach
One property or a small set of state-driven visual changesAnimatedContainer, AnimatedOpacity, AnimatedAlign, AnimatedPadding, AnimatedSwitcher, or TweenAnimationBuilder
Full lifecycle control, repeat/reverse/status, or gesture-driven valuesAnimationController with Tween, CurvedAnimation, AnimatedBuilder, or AnimatedWidget
Shared visual element between routesHero with stable unique tags and compatible source/destination widget trees
List/menu/card reveal with offset timingsOne controller with Intervals, or per-item animation only when lifecycle truly differs
Spring/fling/drag or platform scroll feelfling, animateWith, SpringSimulation, gesture velocity, or platform-specific ScrollPhysics
Motion feels wrong but code worksTune duration, curve, interval, easing, or reduced-motion behavior before adding complexity

Resource Routing

Read only the resources needed for the current task:

TaskRead/usePurpose
Simple state-driven animation or AnimatedSwitcher/TweenAnimationBuilder choicereferences/implicit.md; optionally assets/templates/implicit_animation.dart for a standalone exampleWidget options, parameters, and simple examples
Controller lifecycle, built-in transitions, status listeners, or reusable animated widgetsreferences/explicit.md; optionally assets/templates/explicit_animation.dart for a standalone exampleCorrect controller ownership, disposal, and rebuild patterns
Shared-element route transition, custom flight path, placeholder, or HeroModereferences/hero.md; optionally assets/templates/hero_transition.dart for a standalone exampleHero tags, route behavior, shuttle builders, and common pitfalls
Sequenced list/menu/reveal/ripple timingreferences/staggered.md; optionally assets/templates/staggered_animation.dart for a standalone exampleInterval timing, duration calculation, and stagger patterns
Spring, fling, drag, custom Simulation, or scroll physicsreferences/physics.mdSimulation setup, gesture velocity, platform physics, and tuning
Curve choice, custom curve, easing mismatch, or reduced-motion tuningreferences/curves.mdCurve selection, custom curves, and accessibility notes

Templates are complete demo files, not drop-in production modules. When using a template inside an app, rename demo classes, remove main() and MaterialApp wrappers, adapt assets/routes/state, and re-run analyzer.

Constraints

  • Do not invent missing routes, asset paths, theme tokens, gesture behavior, or

state-management APIs. Inspect them or ask the user if they are absent.

  • Do not add an AnimationController when an implicit widget gives the same

behavior with less lifecycle risk.

  • Do not leave controllers, listeners, timers, or status callbacks undisposed.
  • Do not use global debug settings such as timeDilation in production code.

Mention them only as a local debugging aid.

  • Do not copy reference snippets blindly; adapt them to the project's Flutter

version, lint rules, null-safety, and deprecation state.

  • Do not make accessibility optional for user-facing motion. If reduced-motion

support cannot be implemented, report the limitation.

Validation

  • Run dart format or the project's formatter on edited Dart files when edits

are made.

  • Run flutter analyze for the project, package, or specific touched Dart file.
  • Run focused tests when animation changes affect navigation, gestures,

stateful lifecycle, or user-visible regressions.

  • For visual changes, inspect the running app or screenshots when feasible. If

that is not possible, state what was validated statically and what remains visually unverified.

  • When updating templates, verify each template as lib/main.dart in a minimal

Flutter project with flutter analyze lib/main.dart.

Related skills

How it compares

Choose flutter-animations over generic Flutter snippets when motion must integrate with navigation, theme, gestures, and accessibility in one widget tree.

FAQ

When should I use Implicit vs Explicit animations?

Use Implicit (AnimatedContainer, AnimatedOpacity) for simple state-driven transitions. Use Explicit (AnimationController) when you need full control over timing, multiple simultaneous animations, or monitoring animation state.

What is a hero animation?

Shared element transition that animates a widget from one screen to another. Standard hero transitions work on most navigation; radial hero animations fan out from a center point.

Is Flutter Animations safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.