What problem does it solve? After implementing a HarmonyOS feature, static checks alone cannot confirm the app actually behaves correctly on a real device. This Skill closes the acceptance loop by driving the app on a physical device or emulator, operating its UI, and visually verifying each screen against requirements. ## Core Features & Use Cases - End-to-end device workflow: Confirms devices are online, builds and installs the debug-signed HAP, and launches the app via dcli tools. - UI inspection and operation: Reads the on-screen node tree with dcli__ui_layout, then clicks, swipes, and inputs text through dcli__ui_click, dcli__ui_swipe, and dcli__ui_text. - Screenshot-based verification: Captures per-step screenshots with dcli__ui_screenshot and inspects them with read_image to compare against expected results, falling back to device logs for failures. - Use Case: After finishing a login page, build and install the app on an emulator, tap the login button, screenshot the result, and confirm the home page displays the user nickname. ## Quick Start Verify the login flow of my HarmonyOS app on a connected device by building, installing, tapping through the screens, and checking screenshots against the expected behavior.
