What problem does it solve? When a Jetpack Compose UI recomposes too often, developers struggle to answer two questions: which composables get dragged in when a root composable changes, and which composables actually recompose at runtime during a scroll or animation. This Skill drives the active investigation features of the compose-stability-analyzer IntelliJ/Android Studio plugin to answer both. ## Core Features & Use Cases - Static Cascade Visualizer: Right-click inside any @Composable and run Analyze Recomposition Cascade to walk the static call graph (depth-capped at 10, cycle-safe) and see the blast radius of a state change, with per-node stability badges. - Live Recomposition Heatmap: Toggle the heatmap to stream D/Recomposition logcat events from a connected device via adb logcat -s Recomposition:D -T 1 and render recomposition counts as color-coded block inlays above each instrumented composable. - Three-Tab Tool Window: Use the Explorer tab to survey a module, the Cascade tab for static analysis, and the Heatmap tab for runtime confirmation. - Use Case: Before refactoring a shared composable like PriceTicker, run the cascade to find 12 downstream nodes, annotate the top suspects with @TraceRecomposition, toggle the heatmap during a scroll, and discover only 2 nodes are actually hot — then fix just those two. ## Quick Start Right-click inside a @Composable function, choose Analyze Recomposition Cascade to see its blast radius, then annotate targets with @TraceRecomposition and toggle the Recomposition Heatmap to confirm live recomposition counts from your device.
