Flutter motion

Skill musabekisakov-imj/flutter-design-engineer/skills/flutter-motion

Agent skills for product-aware, adaptive, accessible, and visually verified Flutter UI design engineering

Install

npx -y skills add musabekisakov-imj/flutter-design-engineer --skill flutter-motion

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design and implement purposeful, performant, and accessible motion in Flutter. Use for transitions, micro-interactions, gesture feedback, animated state changes, shared elements, list choreography, reduced-motion behavior, or diagnosing animation quality and performance.

SKILL.md

1.8 KB, as published. Nobody here has run it

Flutter Motion

Use motion to explain change, causality, continuity, hierarchy, or feedback. Remove motion that communicates none of these.

Specify

Name the event, property change, user value, trigger, interruption behavior, and completion state.
Select the least complex Flutter mechanism that satisfies it: implicit animation, AnimatedSwitcher, explicit controller, hero transition, custom painter, or physics simulation.
Define duration ranges, curve character, sequencing, gesture relationship, and reduced-motion equivalent. Read references/motion.md. For multi-domain state changes, read references/connected-product-workflows.md and animate only the region whose state changed.
Check how the motion behaves during rapid taps, navigation interruption, rebuilds, route disposal, low frame budgets, and changed accessibility settings.

Implement

Animate transform and opacity before layout-heavy properties when visually equivalent.
Dispose controllers and avoid duplicated tickers.
Preserve semantic state throughout transitions.
Avoid delayed access to core actions.
Keep list stagger subtle and bounded; never scale delay linearly across large collections.
Provide immediate or cross-fade alternatives when reduced motion is requested.

Verify

Test at normal and reduced motion, under interruption, and on the lowest relevant performance tier. Inspect frame behavior when tooling permits. Report unmeasured performance instead of assuming smoothness.