What problem does it solve? Choosing and correctly implementing the right Compose Multiplatform animation API is error-prone: developers pick overly complex APIs, forget reduced-motion accessibility, or hit crashes with shared element transitions missing a SharedTransitionLayout. This Skill provides decision guidance and working code patterns for every common animation scenario. ## Core Features & Use Cases - API Selection Guidance: A preference-ordered recommendation ladder (AnimatedVisibility → animateContentSize → Crossfade/AnimatedContent → animateXAsState → shared elements) so you always pick the simplest API for the job. - Ready-to-Use Patterns: Complete composable examples for enter/exit transitions, size animations, state crossfades, property animations, multi-property Transitions, and Compose 1.7+ shared element transitions between list and detail screens. - Accessibility & Testing: Reduced-motion fallbacks via LocalAccessibilityManager, plus Compose UI test and Roborazzi screenshot test patterns for animated content. - Use Case: When building a product list that expands cards on tap and transitions to a detail screen, use this Skill to implement AnimatedVisibility with expandVertically, animateContentSize for height changes, and a shared element transition for the product image. ## Quick Start Ask the agent to add an animated expand/collapse transition with reduced-motion support to a Compose Multiplatform card composable.