What problem does it solve? Debug builds misrepresent Jetpack Compose performance: the interpreted runtime, JIT warmup, Live Literals constant-getters, and approximate Layout Inspector counts inflate startup times, frame timings, and recomposition counts. This Skill ensures every performance number is measured against a release variant with R8 enabled so conclusions reflect what users actually experience. ## Core Features & Use Cases - Release-mode measurement setup: Configures a release (or release-derived) build with R8 minification, resource shrinking, debug signing for measurement, and NDK debug symbols for profiling. - Correct tooling wiring: Targets Macrobenchmark with CompilationMode.Partial(BaselineProfileMode.Require), reads Compose Compiler reports from the release output directory, and confirms recomposition counts with @TraceRecomposition instead of Layout Inspector. - Anti-pattern detection: Flags perf claims sourced from assembleDebug, CompilationMode.None, debug Layout Inspector counts, or numbers quoted without variant, device, and iteration provenance. - Use Case: A developer reports "startup is 1.4s" from a debug build. This Skill rebuilds the measurement against the release variant on a physical device and produces a reviewable number like "TimeToInitialDisplay p50 = 460 ms (release, R8 on, Pixel 6, cold start, 10 iterations)". ## Quick Start Ask the assistant to verify whether your Compose performance numbers were measured in release mode and to set up a release-with-R8 Macrobenchmark run for your app.
