Use this skill to ensure Jetpack Compose performance numbers reflect production reality by measuring against a release variant with R8 enabled, Live Literals disabled, and Compose Compiler reports read from the release output directory. Covers why debug builds lie (interpreted Compose runtime, JIT warmup, Live Literals constant-getters), how to set up a release-with-symbols measurement build, and how to wire Macrobenchmark, Compose Compiler reports, Layout Inspector, simpleperf, and Android Studio Profiler against it. Cited result is roughly 75 percent startup gain and 60 percent frame-render gain debug to release. Use when the developer reports "slow startup", "jank", "dropped frames", "high recomposition count", or quotes timings from assembleDebug, Layout Inspector, or CompilationMode.None. Use when reviewing a perf bug, setting up a CI perf gate, or before filing a perf regression.
How to install testing-compose-in-release-mode?
skydoves/compose-performance-skills/testing-compose-in-release-mode
$npx -y skills add skydoves/compose-performance-skills --skill testing-compose-in-release-modeInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/skydoves/compose-performance-skills" --skill "skydoves/compose-performance-skills/testing-compose-in-release-mode"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/skydoves/compose-performance-skills" that are relevant to the current task. Run `npx skills add "https://github.com/skydoves/compose-performance-skills"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- gpt-image-2Create or edit images with Pilio GPT Image 2 through the unified Pilio developer API.Jul 2026
- spec-driven-implementationDrive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs…Jul 2026
- review-prReview a pull request diff and write structured feedback to review.json for the workflow to publish.Jul 2026
- write-product-specWrite a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation.Jul 2026
- write-tech-specWrite a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints.Jul 2026
- fix-errorsFix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests.Jul 2026
