wnb-compose-animationlisted

# Jetpack Compose — decision-aware animation Most animation bugs in Compose are not "wrong API" bugs — they are **"did not need to animate in the first place"** bugs. This skill's job is to make the first decision explicit before any code is written. Only after the "should we animate?" gate passes does API selection matter. For deep API selection (which primitive to reach for), this skill is intentionally thin — see `[[compose-animations]]` (chrisbanes/skills) linked at the end. This skill focuses on the **gate**. ## Non-negotiables 1. **Every animation earns its frame budget.** If a reviewer cannot answer "what does this animation communicate?" in one sentence, remove it. 2. **The gate runs first, always.** Before typing `AnimatedVisibility` or `animate*AsState`, answer the three "should we animate?" questions below. If any answer is no, no motion. 3. **Every animation gets a `label`.** `animate*AsState(label = "fabWidth")`, `rememberTransition(label = "phase")`, `AnimatedContent(label = "profile-content")`. Enables the Compose Animation preview and tooling — no exceptions. 4. **Respect reduce-motion.** On Android, wrap animation opt-in on `LocalAccessibilityManager.current?.getRecommendedTimeoutMillis(...)` or the platform's `Settings.Global.TRANSITION_ANIMATION_SCALE`. If motion is disabled, jump to the end state directly. 5. **No animated value on the recomposition-hot path.** Reading a frame-updating `State` in a composable body causes recomposition every frame. For