What problem does it solve? Choosing and correctly implementing the right Jetpack Compose animation API is error-prone: developers pick overly complex APIs for simple cases, animate layout properties that cause jank, or misconfigure shared element transitions that silently fail. This Skill provides an opinionated decision tree, tuned spring specs, and anti-pattern fixes for Compose animation work. ## Core Features & Use Cases - API Decision Tree: Maps each animation need (single value, visibility, crossfade, multi-property, shared elements, gestures) to the correct Compose API such as animateFloatAsState, AnimatedVisibility, updateTransition, Animatable, or SharedTransitionLayout. - Opinionated Spring Specs: Provides pre-tuned stiffness and damping values for UI snap, tactile feedback, bouncy reveals, and drag-follow interactions. - Anti-Pattern Fixes: Documents BAD/GOOD code pairs for animating layout size vs transforms, LaunchedEffect keying, LazyColumn item keys, and nested AnimatedContent in lists. - Deep-Dive References: Covers gestures and nested scroll, recomposition performance with Macrobenchmark and Baseline Profiles, and shared element transition recipes. - Use Case: When building an Android screen where tapping a card in a list should morph into a detail view, use this Skill to wire SharedTransitionLayout with matching rememberSharedContentState keys and a tuned boundsTransform spring. ## Quick Start Ask the AI to implement a card-to-detail shared element transition in Jetpack Compose using this skill's SharedTransitionLayout recipe.