Loading...
Loading...
Found 19 Skills
HarmonyOS application development assistant based on ArkTS and ArkUI frameworks. Confirm API version (default API 20+) and target device type (default PC) before starting. Supports UI component development, data management, network communication, and system capability integration. Applicable for greenfield development, iterating existing projects, and architecture design. References official Huawei documentation including release notes, development guides, API references, best practices, and FAQ.
HarmonyOS code review skill for auditing ArkTS projects against official Huawei development guidelines and security best practices. Use when reviewing HarmonyOS applications for: (1) Security compliance (hardcoded credentials, encryption, input validation), (2) ArkTS language standards (hilog usage, type safety, magic numbers), (3) Component lifecycle management (resource cleanup, event subscription handling), (4) State management (V1/V2 decorator consistency), (5) Database operations (ResultSet handling, transaction management, encryption), (6) Permission management (official permission patterns), (7) Performance issues (async forEach, resource leaks), (8) API version compatibility, (9) Kit usage best practices. Generates comprehensive markdown reports with prioritized fix recommendations.
Professional HarmonyOS project scaffolding and environment verification. Initialize Standard ArkTS or Native C++ templates.
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".
HarmonyOS application development expert. Use when building HarmonyOS apps with ArkTS, ArkUI, Stage model, and distributed capabilities. Covers HarmonyOS NEXT (API 12+) best practices.
For HarmonyOS NEXT and ArkTS development, especially when handling .ets files, implementing @ComponentV2 components, or debugging errors. Provides development guidance based on official standards and maintains categorized error logs for efficient troubleshooting.
HarmonyOS ArkTS application development with ArkUI declarative UI framework. Use when building HarmonyOS/OpenHarmony apps, creating ArkUI components, implementing state management with decorators (@State, @Prop, @Link), migrating from TypeScript to ArkTS, or working with HarmonyOS-specific APIs (router, http, preferences). Covers component lifecycle, layout patterns, and ArkTS language constraints.
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.
HarmonyOS NEXT (mainly for API 12+; includes a large number of version labels for API 12-23, and a small number of references to earlier versions for comparison) offline reference library navigation: progressively locate documents (ArkTS/ArkUI/NDK) by Kit/task/index.
HarmonyOS/ArkUI scenario-based development skill for implementing, troubleshooting, and validating ArkUI (.ets) features. It routes requests through four phases (REQ, DEV, FIX, VAL) and four primary scenes: ARKUI-01 ArkUI basic syntax; ARKUI-02 UI framework and page logic; ARKUI-03 state management; and ARKUI-04 compilation and runtime. It does not cover native development unrelated to ArkUI, non-HarmonyOS platforms, or CI/CD.
HarmonyOS ArkUI MVVM architecture skill. Use for Model/ViewModel/View layering, directory planning, component responsibilities, data flow, and MVVM refactoring. Trigger for V1 or V2 state-management MVVM development, ViewModel extraction, state-ownership fixes, and testability improvements.