Prompt file imported from hrkj-18/alarm (
.github/prompts/optimize-size.prompt.md). Copyright stays with the author.
Investigate the requested app-size concern before changing code. Inspect dependencies, assets, Android build configuration, and the available build outputs. Establish a reproducible baseline and compare the same build mode and ABI after any proposed change.
Prefer removing unused resources or avoiding unnecessary dependencies over adding optimization tooling. Evaluate runtime behavior, alarm reliability, accessibility, security, platform compatibility, maintenance cost, and transitive dependency impact. Profile or measure rather than speculate.
Do not change signing credentials, production configuration, distribution settings, or shrinker/split behavior without explicit authorization and a compatibility check. Do not make unrelated product changes. Report measured before/after artifact sizes, build commands, tradeoffs, and anything that could not be verified; do not claim an optimization without measurements.
