mobile-compaction

Context compaction strategically summarizes less critical code while preserving essential context, reducing token consumption without losing task-critical information. Use scoped commands like /compact --module=feature:auth to focus on specific areas of your Android project.

Yes, context compaction supports module-level isolation and layer-based targeting. Narrow your scope to UI, Data, or Domain layers, or focus on a single module to retain only relevant files while summarizing the rest.

Define clear compaction scopes and preservation rules before starting. Use layer-based or module-focused workflows to keep essential architecture visible while reducing noise from unrelated code, enabling sustained work across complex refactors.

Build variant and test isolation narrows context around specific test failures. Apply variant-focused compaction to exclude unrelated build configurations and test code, keeping your debugging context lean and focused.

Compaction is essential when token limits threaten your workflow—particularly during deep refactors, cross-cutting changes, or extended debugging. Use it to preserve focus when exploring large codebases where full context exhausts available tokens.

Yes, the skill supports build variant and test-focused workflows, allowing you to isolate context around specific variants or failing tests while summarizing configuration and test code outside your scope.