compose-recomposition-performance

Classify Jetpack Compose recomposition causes across stability, state reads, and back-writing.

Updated Aug 27, 2026

Search Tags:#state management #performance profiling #jetpack compose #recomposition #compiler reports #layout inspector #stability diagnostics

Ready to run

npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill compose-recomposition-performance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compose-recomposition-performance
Source: https://github.com/soygabimoreno/Los-ANDROIDES/tree/main/.agents/skills/compose-recomposition-performance
Command: npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill compose-recomposition-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you pinpoint why Jetpack Compose is recomposing more than expected so you can reduce wasted work and improve UI responsiveness.

Core Features & Use Cases

Recomposition root-cause triage across three axes: parameter stability/skipping, where State is read (composition vs layout/draw), and back-writing across phases.
Performance debugging pathways using concrete evidence like recomposition counts, compiler/composables.txt churn, and Layout Inspector observations.
Targeted next-skill routing so you can move from broad suspicion to focused diagnostics without guessing.

Quick Start

Use this Skill to identify which axis (skipping, deferred reads, or cross-phase back-writing) best matches your recomposition evidence, then follow its suggested next skill.

Frequently Asked Questions about compose-recomposition-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does my Jetpack Compose screen recompose excessively during scrolling or animations?▼

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.

How do I diagnose parameter stability and skipping issues in Jetpack Compose?▼

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.

What is the difference between composition phase and layout phase State reads in Compose?▼

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.

How do I fix cross-phase back-writing issues causing recomposition spikes?▼

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.

Can I use Layout Inspector to investigate Compose recomposition counts?▼

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.