skills/common/common-mobile-animation/SKILL.md
Apply motion design principles for mobile apps covering timing curves, transitions, gestures, and performance-conscious animations. Use when implementing screen transitions, gesture-driven interactions, shared-element animations, or optimizing animation frame rates on iOS, Android, or Flutter.
npx skillsauth add hoangnguyen0403/agent-skills-standard common-mobile-animationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Duration | Range | Use Case | |----------|-------|----------| | Short | 100-150ms | Toggles, cell press | | Medium | 250-350ms | Navigation, modals | | Long | 400-600ms | Shared element, complex state |
Hard limit: Never exceed 600ms for any animation.
400-600ms shared-element or complex-state pattern; do not substitute the Medium range.Curves.fastOutSlowIn (Material) or easeInOut (iOS). Never use linear.transform, opacity). Avoid width/height which trigger layout.onPan / interactivePopGesture for fluid, interruptible UX.See implementation examples for Flutter and iOS animation patterns.
dispose() AnimationControllers in Flutter; invalidate timers in iOS.When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.