compose-recomposition-performance

Excessive Jetpack Compose recomposition is typically caused by unstable parameters, reading State directly in composition, or cross-phase back-writing. This Skill classifies the root cause across these three axes using your Layout Inspector observations.

To diagnose Jetpack Compose parameter stability and skipping issues, you map observed recomposition behavior to compiler reports and composables.txt churn. This Skill triages whether your restartable composables fail to skip due to unstable inputs.

Composition phase State reads trigger recomposition, while layout or draw phase reads avoid it by deferring the State observation. This Skill identifies which phase your State reads occur in and routes you to deferred read diagnostics.

Fixing cross-phase back-writing recomposition spikes requires identifying where layout or draw phases incorrectly write back to State. This Skill triages your recomposition evidence and routes you to focused back-writing remediation diagnostics.

Yes, you can use Layout Inspector to observe Compose recomposition counts and frame-rate State reads. This Skill uses that concrete evidence to classify your recomposition behavior across skipping, deferred reads, and back-writing axes.