Configuring R8 For Compose
Minimal R8/ProGuard setup for Compose release builds; rejects over-broad keep rules
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · d1e2f78
Fetched SKILL.md at build/configuring-r8-for-compose/SKILL.md via raw GitHub; frontmatter parses with name+description, no scripts referenced in the body (self-contained), and its one repo-relative crosslink (measurement/testing-compose-in-release-mode/SKILL.md) returns HTTP 200. No security smells; retrace commands use $ANDROID_HOME env, not hardcoded paths. For output I wrote a broken config (proguard-android.txt, -keep androidx.compose.**, -keep kotlin.Metadata, -dontobfuscate) and reviewed it twice: my baseline left proguard-android.txt in its final recommendation and hedged on the keeps ("probably remove unless you hit a crash"), while the skill-guided review switched to proguard-android-optimize.txt, deleted all three lines with per-line rationale plus a narrow kotlinx.serialization replacement, and added the missing_rules.txt/retrace/APK-analyze workflow the baseline omitted. Docs lose a point: the "proguard-android.txt skips R8 optimizations" claim and the 75%/60% figures are stated more firmly than a single cited Medium post supports.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 7/10
- Docs & honesty 4/5
What Configuring R8 For Compose does
Guides configuring R8 minification for a Jetpack Compose release variant: enable full mode with proguard-android-optimize.txt, turn on minification and resource shrinking, and rely on Compose's bundled consumer rules instead of adding Compose-wide keeps. Triggers when first enabling minification, when a PR adds a broad keep like `-keep class androidx.compose.** { *; }`, or when a release build crashes after shrinking. Covers the AGP missing_rules.txt reporter and R8 retrace for diagnosing release crashes.
How to install Configuring R8 For Compose
git clone --depth 1 https://github.com/skydoves/compose-performance-skills.git /tmp/configuring-r8-for-compose-src
mkdir -p ~/.claude/skills
cp -R /tmp/configuring-r8-for-compose-src/build/configuring-r8-for-compose ~/.claude/skills/configuring-r8-for-compose
# Pure-knowledge skill (single SKILL.md, no scripts/deps). No external tool needed to use it.
# Repo also ships scripts/install-skills.sh that symlinks all 26 skills into ~/.claude/skills/ if you want the whole set.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Configuring R8 For Compose
-
/configuring-r8-for-composeMinimal R8/ProGuard setup for Compose release builds; rejects over-broad keep rules
It also activates on plain-language prompts like these:
-
Set up R8 full mode for our Compose app -
Fix our ProGuard keep rules for Compose -
Enable resource shrinking without breaking Compose
Frequently asked questions
- Is the Configuring R8 For Compose skill free?
- Yes. The skill itself is free from skydoves/compose-performance-skills. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Configuring R8 For Compose work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Tested · Works. Fetched SKILL.md at build/configuring-r8-for-compose/SKILL.md via raw GitHub; frontmatter parses with name+description, no scripts referenced in the body (self-contained), and its one repo-relative crosslink (measurement/testing-compose-in-release-mode/SKILL.md) returns HTTP 200. No security smells; retrace commands use $ANDROID_HOME env, not hardcoded paths. For output I wrote a broken config (proguard-android.txt, -keep androidx.compose.**, -keep kotlin.Metadata, -dontobfuscate) and reviewed it twice: my baseline left proguard-android.txt in its final recommendation and hedged on the keeps ("probably remove unless you hit a crash"), while the skill-guided review switched to proguard-android-optimize.txt, deleted all three lines with per-line rationale plus a narrow kotlinx.serialization replacement, and added the missing_rules.txt/retrace/APK-analyze workflow the baseline omitted. Docs lose a point: the "proguard-android.txt skips R8 optimizations" claim and the 75%/60% figures are stated more firmly than a single cited Medium post supports.
- What is the Configuring R8 For Compose SkillProof Score?
- 8.4/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 4/5.
- How do I install Configuring R8 For Compose?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Configuring R8 For Compose with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.