What problem does it solve? HarmonyOS NEXT development fails in non-obvious ways: ArkTS rejects valid TypeScript, state decorators silently stop observing, and global ArkUI APIs target the wrong UI instance. This Skill encodes the platform's compile rules, state-management generations, and API-version gates so code compiles, updates, and passes AppGallery release verification. ## Core Features & Use Cases - ArkTS language enforcement: Covers the roughly 76 arkts-* restriction rules with error codes, severities, and rewrite recipes for diagnostics like arkts-no-any-unknown and arkts-no-structural-typing. - State management V1/V2 guidance: Explains @ObservedV2/@Trace, @Param/@Event, V1 decorators, and the API 19 UIUtils interop functions, including the silent-failure modes of each. - End-to-end workflows: Provides implement, review, fix-compile-errors, migrate-from-android, and verify-on-device workflows with explicit gates using hvigorw, codelinter, hdc, and uitest. - Use Case: When porting an Android app, follow the per-concern mapping tables to translate Activities into NavDestinations, ViewModels into @ObservedV2 models, and JNI into Node-API, then verify one vertical slice on a real device. ## Quick Start Use the harmonyos skill to review my entry module's .ets files for ArkTS violations and state-management bugs against API 20.