What problem does it solve? Verifying Android UI changes often stops at green unit tests, which prove nothing about what a user actually sees on a device. This Skill defines a repeatable loop that builds a debug APK with Gradle, deploys it to an emulator with the android CLI, and captures layout JSON and screen PNGs as real visual evidence. ## Core Features & Use Cases - Device-driven verification: Launch an emulator this run owns, deploy the APK via android run, and drive screens with layout inspection, screen capture, and input commands. - Feature-map coverage: A features/ directory maps each user-facing area (save note, search, empty/error states, multi-surface journeys) with entry points, success/cancel/error/empty/persistence paths, and proof requirements. - Fail-closed doctor checks: Verify the android CLI, adb serial, and assemble receipts before driving, and stop instead of faking device proof when the environment is broken. - Use Case: After changing the note editor, run the save-note feature flow on an emulator, capture layout JSON and a PNG showing the saved row, and report exactly which commands ran and which checks were skipped. ## Quick Start Ask the agent to verify the Notes app save and search flows on an emulator using the android CLI and produce layout JSON and screenshot evidence.
