compose-stability-diagnostics

Excessive Jetpack Compose recomposition typically happens when composable parameters lack stability, causing instance churn that breaks skippability. This Skill diagnoses parameter stability issues using compiler reports to identify unstable inputs and non-skippable restartable composables.

Generate Jetpack Compose compiler reports by running a release build with reports enabled for the suspected module. Read the generated module, class, and composable metrics files to interpret stability indicators and identify parameters churning identity across recompositions.

Kotlin 2.0.20+ strong skipping changes when unstable parameters break skippability by altering how Compose compares stable versus unstable inputs. This Skill helps interpret these comparison semantics to determine why composables fail to skip.

Fix unstable parameters in Compose lazy lists by stabilizing item inputs using hoisting and remember, converting interface collections to kotlinx.collections.immutable, and correctly applying @Immutable or @Stable annotations.

Use @Immutable versus @Stable in Jetpack Compose based on compiler report stability indicators showing non-skippable restartable composables. This Skill guides correct annotation usage to resolve parameter instability and restore predictable skipping behavior.

Diagnosing Compose recomposition without compiler reports is limited because you need generated class and composable metrics files to read stability and skippability indicators directly. This Skill workflow requires running a release build with reports enabled to identify unstable parameters.