Loading...
Loading...
Found 6 Skills
Debug HarmonyOS ArkWeb applications using Chrome DevTools Protocol. Use when Claude needs to: (1) Start ArkWeb debugging sessions, (2) Connect Chrome DevTools to HarmonyOS apps via hdc, (3) Inspect webview elements, console, and network, (4) Test ArkWeb applications with Chrome DevTools MCP, (5) Troubleshoot webview debugging issues, or (6) Manage port forwarding and debugging sessions. Automatically detects project configuration, device connection, and debugging sockets. Works with ohos-app-build-debug skill for complete workflow.
Vision-driven HarmonyOS NEXT device automation using Midscene. Operates entirely from screenshots — no DOM or accessibility labels required. Can interact with all visible elements on screen regardless of technology stack. Control HarmonyOS devices with natural language commands via HDC. Perform taps, swipes, text input, app launches, screenshots, and more. Trigger keywords: harmony, harmonyos, 鸿蒙, hdc, huawei device, harmony app, harmony automation, harmony phone, harmony tablet Powered by Midscene.js (https://midscenejs.com)
HarmonyOS application build, clean, package and device installation. Use when building HarmonyOS projects with hvigorw, cleaning build artifacts, managing ohpm dependencies, packaging HAP/HSP/APP bundles, installing to devices via hdc, or troubleshooting installation errors like "version code not same".
Use when the user wants to download OpenHarmony daily build images or flash them to a real device (DAYU200/RK3568 or others). Triggers on daily build, DAYU200, RK3568, flashing, burning, hdc reboot, upgrading firmware.
Provides UT-based code coverage report generation for OpenHarmony C/C++, supporting both full and incremental coverage analysis, and requires a test device to be connected through hdc. Use when: (1) the user requests full code coverage for a subsystem, part, module, test suite, or test case; if a report path is provided, parse it as the --output path; (2) the user requests incremental code coverage for a part, module, test suite, or test case, requiring git diff files; if a report path is provided, parse it as the --output path. Note: incremental coverage does not support the subsystem level. Activate when an OpenHarmony device must be connected to execute tests.
Develop, sign, deploy, and verify standalone OpenHarmony apps whose APIs or permissions may require `hos_system_app`, an elevated APL, ACL/provisioning, or a Full SDK system API. Use for privileged inspection or control of other apps or protected device state and for `Not System App` failures, then verify requirements against the exact SDK metadata. For public ordinary-app capabilities use `ohos-app-dev`; for OHOS source-tree components use `ohos-system-dev`.