/compose-recomposition-performance

Use when investigating Jetpack Compose recomposition performance, skippable/restartable composables, composables.txt or compiler reports, Layout Inspector recomposition counts, or frame-rate State reads in composition vs layout/draw, and it is not yet clear whether the cause is

Boost this skill

vitorpamplona@vitorpamplona

GitHub

From plugin

amethyst

1.6k30 skills3 commands

Install

$ npx -y skills add vitorpamplona/amethyst --skill compose-recomposition-performance --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/compose-recomposition-performance

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when investigating Jetpack Compose recomposition performance, skippable/restartable composables, composables.txt or compiler reports, Layout Inspector recomposition counts, or frame-rate State reads in composition vs layout/draw, and it is not yet clear whether the cause is

SKILL.md

compose-recomposition-performance.SKILL.md

name: compose-recomposition-performance
description: Use when investigating Jetpack Compose recomposition performance, skippable/restartable composables, composables.txt or compiler reports, Layout Inspector recomposition counts, or frame-rate State reads in composition vs layout/draw, and it is not yet clear whether the cause is parameter stability or deferred reads. Technique-layer skill — complements the codebase-specific compose-expert.

Compose recomposition performance

Router only — deep fixes live in [`compose-stability-diagnostics`](../compose-stability-diagnostics/SKILL.md) and [`compose-state-deferred-reads`](../compose-state-deferred-reads/SKILL.md).

Two axes

1. **Parameter stability / skipping** — can Compose skip this restartable composable; are arguments stable and comparable? 2. **Where `State` is read** — is frame-rate `State` read during composition vs layout/draw?

Either axis can dominate; they combine independently.

Route here → focused skill

| Primary suspicion | Next skill | |---|---| | Skipping, unstable params, compiler/`composables.txt` churn | [`compose-stability-diagnostics`](../compose-stability-diagnostics/SKILL.md) | | Frame-rate `State` read phase (composition vs layout/draw) | [`compose-state-deferred-reads`](../compose-state-deferred-reads/SKILL.md) | | Evidence for both | Apply both skills in parallel |

Review order

1. Decide which axis fits the evidence; open the matching skill. 2. If unclear, sample both — stability churn vs composition-phase reads of fast `State`. 3. Re-measure after changes.