Skip to content
Skills Library
Design & UX · Building & coding

flutter-motion

/flutter-motion

Add or review purposeful animation in Flutter apps — card entrances, list insert/remove/reorder, page and tab transitions, hero/container transforms, button progress and success, counters, progress bars and charts that move from old to new values, sheets, skeleton shimmer, micro-interactions, scroll effects, desktop hover. Use when the user asks for animations, transitions, "make it feel alive/smooth", or when motion feels janky, missing or overdone.

Author
m3n99 ↗
Licence
MIT
Last repository change
09.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Add or review purposeful animation in Flutter apps — card entrances, list insert/remove/reorder, page and tab transitions, hero/container transforms, button progress and success, counters, progress bars and charts that move from old to new values, sheets, skeleton shimmer, micro-interactions, scroll effects, desktop hover. Use when the user asks for animations, transitions, "make it feel alive/smooth", or when motion feels janky, missing or overdone.

Triggers from the description

make it feel alive/smooth
Original author description

Add or review purposeful animation in Flutter apps — card entrances, list insert/remove/reorder, page and tab transitions, hero/container transforms, button progress and success, counters, progress bars and charts that move from old to new values, sheets, skeleton shimmer, micro-interactions, scroll effects, desktop hover. Use when the user asks for animations, transitions, "make it feel alive/smooth", or when motion feels janky, missing or overdone.

How it works

  1. Workflow
  2. Rules
  3. References
Original SKILL.md headings · 52 lines, 543 words
SKILL.md preview
---
name: flutter-motion
description: Add or review purposeful animation in Flutter apps — card entrances, list insert/remove/reorder, page and tab transitions, hero/container transforms, button progress and success, counters, progress bars and charts that move from old to new values, sheets, skeleton shimmer, micro-interactions, scroll effects, desktop hover. Use when the user asks for animations, transitions, "make it feel alive/smooth", or when motion feels janky, missing or overdone.
---

# Flutter Motion

Motion explains change: where something came from, what just happened, what is now in focus. Good motion is fast, consistent and comes from a few shared pieces; bad motion is a different `AnimationController` in every widget.

Shared pieces live in the design system (`../flutter-modern-ui/assets/design_system/motion/` and `widgets/`). In a project with its own motion helpers, use and extend those.

## Workflow

1. **Know where to animate.** Use the intake answer (`../flutter-modern-ui/references/intake.md` › Motion). If nobody answered: press feedback, skeleton shimmer, state cross-fades, list insert/remove, button progress. Ask before adding decorative motion.
2. **Inventory what exists**: `rg -n "AnimationController|Animated[A-Z]\w+\(|Hero\(|PageRouteBuilder|TweenAnimationBuilder|flutter_animate|Lottie|Rive" lib`. Reuse existing helpers; remove one-off duplicates when touching them.
3. **Pick one recipe per surface** from `references/recipes.md` and route every screen through it:

   | Surface | Shared piece |
   |---|---|
   | Press feedback | ink + `PressScale` (built into `AppCard`) |
   | Desktop hover | `AppCard` hover border / raised hover shadow |
   | Card entrance | `Entrance` (staggered, first frame only) |
   | Lists insert / remove / reorder | `AnimatedItems` |
   | Loading → content → empty → error | `StateSwitcher` + `ShowAfter` + `Shimmer` |
   | Buttons: busy, success | `SubmitButton` |
   | Counters | `AnimatedNumber` |
   | Progress | `AppProgressBar` |
   | Charts | `MiniBarChart` rules / chart `duration` + `TickerMode` hold |
   | Errors, toggles | `ShakeOnChange`, `PopOnChange` |
   | Pages | theme `pageTransitionsTheme`; `animations` package for shared axis / container transform |

4. **Tokens only**: durations from `AppDurations`, curves from `AppCurves`, every duration through `context.motion(d)` so reduced motion turns it off. `references/principles.md`.
5. **Check performance**: animate transforms and opacity, not layout, where possible; `RepaintBoundary` around continuously animating regions; at most 2–3 blurs on screen; dispose every controller.
6. **Test it** (`references/testing.md`): behaviour tests with `pump(duration)`, a reduced-motion test, and filmstrip screenshots for anything non-trivial; look at the frames.
7. **Record** the motion table (what animates, duration, curve) in DESIGN.md.

## Rules

1. 150–350 ms for UI responses (routes 450 ms). Nothing functional over 500 ms.
2. Enter with deceleration (`AppCurves.enter`), exit with acceleration (`AppCurves.exit`), move on screen with `standard` / `emphasized`. `AppCurves.pop` (overshoot) only for celebrations.
3. Animate **from the current value**: lists keep item state, counters and bars tween from what's on screen, never restart from zero.
4. Entrances play once, on first data or a new sort, for the first ~8 items only; never on scroll or on every rebuild.
5. Nothing animates while hidden: charts in background tabs hold their values until shown (`TickerMode`).
6. Reduced motion (`MediaQuery.disableAnimationsOf`) → zero durations, no shimmer, no entrance, no parallax.
7. Motion never carries meaning alone: a shake comes with an error message, a check with a label change.
8. No infinite animations except loading indicators. No bounce on functional UI.
9. Platform conventions win for routes and sheets (predictive back on Android, Cupertino on iOS).
10. One shared piece per surface; no ad-hoc controllers in screens.

## References

- `references/principles.md`: purpose, easing and duration tables, choreography, accessibility, performance.
- `references/recipes.md`: code for every surface above, plus hero, container transform, shared axis, tabs, sheets, scroll effects, drag physics, celebrations.
- `references/testing.md`: testing animations, filmstrip screenshots, reduced motion, profiling.
- `references/packages.md`: when to reach for `animations`, `flutter_animate`, Lottie, Rive, confetti, and how to keep them on tokens.
Files in this package (5)
  • SKILL.md 4 KB
  • references/packages.md 2 KB
  • references/principles.md 5 KB
  • references/recipes.md 11 KB
  • references/testing.md 3 KB

Versions

The database has no other skills named flutter-motion.

Database snapshot: 13.11.2026 · package version 7417ac048087 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100animate
    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
  • 100animate
    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
  • 90motion-design
    Design and build UI motion with intent — micro-interactions, transitions, entrances, scroll and hover behavior — applying the twelve principles of animation to a brand's settled system, in custom code. Use when the user mentions 'animation,' 'motion,' 'micro-interactions,'…
  • 100animate
    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
  • 100animate
    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
  • 90css-animation-creator
    Create professional CSS animations, transitions, micro-interactions, and complex motion design. Use when adding animations, hover effects, loading states, page transitions, scroll animations, or any motion design work.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.