OpenParable
Skip to content
← Back to skills

Compose Recomposition Performance

Testing & Quality
compose-recomposition-performance

Compose Recomposition Performance is an Agent Skill for testing & quality published in the vitorpamplona/amethyst repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vitorpamplona/amethyst/blob/HEAD/.claude/skills/compose-recomposition-performance/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/compose-recomposition-performance, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Compose recomposition performance

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

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 suspicionNext skill
Skipping, unstable params, compiler/composables.txt churncompose-stability-diagnostics
Frame-rate State read phase (composition vs layout/draw)compose-state-deferred-reads
Evidence for bothApply 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.

When NOT to apply

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