What problem does it solve? Shipping Android UI changes without runtime proof leads to undetected visual and behavioral defects. This Skill enforces a disciplined verification loop that builds with Gradle and drives a real device or emulator through the android CLI, producing concrete evidence instead of unverified claims. ## Core Features & Use Cases - Device verification loop: Runs a doctor check, starts an emulator, assembles via Gradle, deploys APKs with android run, and drives the UI through layout, screen capture, preview rendering, and journeys. - Fail-closed guardrails: Stops immediately if the android binary or official android-cli skill is missing, refuses to double-drive shared emulators, and forbids claiming coverage that was not executed. - Evidence-based done criteria: Requires layout JSON, screen or preview PNGs, journey JSON, and Gradle test reports on disk, with the reply listing commands actually run. - Use Case: After fixing a Compose layout bug, use this Skill to assemble the app, launch it on an emulator, capture layout diffs and screenshots, and report exactly which checks passed. ## Quick Start Verify my Android app's UI changes by building with Gradle and running it on an emulator with screenshot evidence.
