compose-recomposition-performance

Estrellas15

Forks0

Actualizado15 de mayo de 2026 a las 17:14

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

costular

costular/Minitask

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

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.

Compose recomposition performance

Router only — deep fixes live in compose-stability-diagnostics and compose-state-deferred-reads.

Two axes

Parameter stability / skipping — can Compose skip this restartable composable; are arguments stable and comparable?
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`
Frame-rate `State` read phase (composition vs layout/draw)	`compose-state-deferred-reads`
Evidence for both	Apply both skills in parallel

Review order

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

When NOT to apply

Recomposition tracks real data changes, or the bug is correctness not cost.
No profiler / compiler signal suggests a problem.

Más de este repositorio

mismo repositorio

compose-modifier-and-layout-style

costular/Minitask

Use when writing or reviewing Jetpack Compose layout APIs, modifier parameters, modifier chain construction, hardcoded root layout decisions, or layout wrappers around a single conditional.

2026-05-1515

compose-side-effects

costular/Minitask

Use when writing or reviewing Jetpack Compose code with LaunchedEffect, DisposableEffect, SideEffect, rememberCoroutineScope, rememberUpdatedState, snapshotFlow, snackbar, navigation, focus requests, analytics, or event Flow collection.

2026-05-1515

compose-slot-api-pattern

costular/Minitask

Use when designing or reviewing a reusable Jetpack Compose component whose visual regions vary by caller, or when primitive content parameters and boolean shape flags are accumulating.

2026-05-1515

compose-stability-diagnostics

costular/Minitask

Use when writing or reviewing Jetpack Compose parameter stability, compiler reports, skippability, unstable UI state classes, collection parameters, or Kotlin 2.0+ strong skipping behavior.

2026-05-1515

compose-state-authoring

costular/Minitask

Use when writing or reviewing Jetpack Compose code with bare local var in a @Composable, remember { mutableStateOf(...) }, mutableStateListOf/mutableStateMapOf, or @ReadOnlyComposable.

2026-05-1515

compose-state-deferred-reads

costular/Minitask

Use when Jetpack Compose code reads scroll, animation, gesture, or other frame-rate State in composition, passes changing values across composable boundaries, or uses value-form layout/draw modifiers.

2026-05-1515

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.

Compose recomposition performance

Router only — deep fixes live in compose-stability-diagnostics and compose-state-deferred-reads.

Two axes

Parameter stability / skipping — can Compose skip this restartable composable; are arguments stable and comparable?
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`
Frame-rate `State` read phase (composition vs layout/draw)	`compose-state-deferred-reads`
Evidence for both	Apply both skills in parallel

Review order

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

When NOT to apply

Recomposition tracks real data changes, or the bug is correctness not cost.
No profiler / compiler signal suggests a problem.