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. ## Phase → capability - **Research:** `android docs search` / `docs fetch` for authoritative docs. - **Plan:** `android describe` for module/APK introspection; `android info` for env. - **Symbol search:** use **ast-index** by default (standalone, fast). Only if Android Studio is open (`android studio check` reports a live instance) and you need semantic resolution (overloads, resources, type-aware) reach for `android studio find-declaration` / `find-usages`. - **Execute / build:** **gradle builds** (`./gradlew assemble*`). android CLI does NOT build — it deploys: `android run` replaces `adb install`. Pipeline: gradle build → `android describe` (find APK) → `android run`. SDK platforms via `android sd