What problem does it solve?
This Skill solves the problem of turning an Android application into a HarmonyOS/ArkTS-compatible project by running a repeatable, module-by-module migration loop with automatic build, packaging, on-device entry validation, and end-of-migration feature/UI comparison to prevent omissions.
Core Features & Use Cases
- Multi-agent iterative migration: Coordinates analysis, planning, translation, testing, and feedback for multiple migration rounds until omissions are resolved.
- Build-and-validate per module using ohos-app-build-debug: Uses compile validation, HAP packaging, and first-screen on-device verification as the quality gate for each migrated module.
- Global feature + UI comparison: Compares Android vs HarmonyOS capabilities and UI consistency after all planned modules are migrated, then routes remaining gaps back into the planning stage for another iteration.
- Use Case: When migrating a medium-to-large Android app (e.g., Activity/Fragment-based UI and Room/RecyclerView usage) to HarmonyOS with API level constraints (<= API 22), reliably produce a buildable ArkTS codebase and systematically close missing features and UI mismatches.
Quick Start
Provide your Android source path and the HarmonyOS target project path, then instruct the AI to run the full iterative migration workflow using this skill with validation via ohos-app-build-debug.
