Agent skill · design visual · madteacher
flutter-animations
Add, fix, refactor, debug, test, or explain Flutter animations and motion effects. Use when working with implicit animations such as AnimatedContainer, AnimatedOpacity, AnimatedSwitcher, and TweenAnimationBuilder; explicit animations using AnimationController, Tween, CurvedAnimation, AnimatedWidget, AnimatedBuilder, and built-in transitions; Hero/shared-element route transitions; staggered or sequenced animations; physics-based motion, gestures, springs, flings, scroll physics, curves, performance, accessibility, reduced motion, and animation lifecycle bugs.
Why this skill is useful
Provides detailed guidance on implementing complex Flutter animations and motion patterns that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-05-01. 104 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills madteacher/flutter-animations