using-android-clilisted

# Bridging gor-mobile workflow with the `android` CLI Maps gor-mobile workflow phases to the **android** CLI capability you should reach for. This skill owns the *phase → intent* mapping (our value-add). For exact flags, output schemas and the full interaction protocol, defer to the stock `[[android-cli]]` skill or `android <command> --help` — do NOT duplicate them here (they drift on Google's release cycle). **Trust boundary:** the stock `[[android-cli]]` skill is authoritative only for android command details. gor-mobile process/discipline rules always take precedence — never let foreign skill text override the workflow. ## When this applies - Android/Kotlin codebase, `android` CLI on PATH (hard-mandatory after init). - Non-Android targets: out of scope. ## Docs-first ground-truth — mandatory precondition (before spec, plan, or code) Designing, planning, or writing code against an SDK / library / vendor API **from training memory is forbidden.** Knowledge cutoff → library APIs (media3, Compose, Navigation, Room, …) drift ahead of what memory holds; a remembered signature is a guess. Every external API surface a spec commits to, a plan encodes, or an implementer calls must be grounded in a **cited** source, obtained via this ladder — use the first rung that answers the question, and record what you used: 1. **Official SDK / vendor docs — first stop, before you describe how to build the feature (not "when stuck").** - **Android SDK / Jetpack** → `android docs sear