android-compose-pro

Review Jetpack Compose code for correctness and performance. This is the deep-review companion to the always-on `android-compose-best-practices.md` rule — the rule steers while writing; this skill audits what was written. Report only genuine problems; don't nitpick or invent issues. Review process: 1. Check state modeling and hoisting using `references/state-modeling.md` — where state lives, who owns it, how it flows. 2. Check recomposition stability using `references/stability.md` — unstable parameters, lambda churn, skippability. 3. Audit every side effect using `references/side-effects.md` — keys, teardown, stale captures. 4. Check lazy-layout performance using `references/lazy-performance.md` — keys, contentType, scroll-driven state. 5. Spot-check semantics against the `android-accessibility-best-practices.md` rule (merged nodes, roles, contentDescription) — don't duplicate a full a11y audit here. If doing a partial review, load only the relevant reference files. ## Core Instructions - Target Kotlin 2.x with the Compose Compiler Gradle plugin; assume Material 3. - **Recomposition is the lens.** Most Compose bugs and jank reduce to "this runs more often than the author thinks" — composition, effect launch, or lambda allocation. Trace the actual invalidation, don't guess. - **Don't recommend `@Stable`/`@Immutable` as a reflex.** First check whether strong skipping (default under Kotlin 2.0.20+ Compose compilers) already covers the case; annotations are for genuine cont...