What problem does it solve? HarmonyOS ArkUI developers often struggle with tangled state management, unclear layer responsibilities, and mixing V1/V2 state decorators, leading to unmaintainable code and runtime crashes. This Skill provides a structured decision framework and strict workflows to build new features or refactor existing projects into a clean Model/ViewModel/View architecture. ## Core Features & Use Cases - MVVM Layering Guidance: Decision trees for state variable placement (state hoisting), code file ownership (model/ vs viewmodel/ vs util/), and recommended directory structures. - V1/V2 State Management Support: Separate development scenarios for V1 (@Observed + @Track + @ObjectLink) and V2 (@ObservedV2 + @Trace + @Param/@Event + PersistenceV2), with anti-mixing rules and decorator mapping tables. - New-Build and Refactor Workflows: Step-by-step workflows for creating new MVVM features and migrating existing pages, including anti-pattern scanning and per-page verification with devecocli builds. - Use Case: You inherit a single-file ArkUI page with business logic embedded in the Page component. Use this Skill to scan for anti-patterns, extract a ViewModel, separate the Model layer, and verify the refactored page compiles and behaves identically. ## Quick Start Ask the AI to refactor my existing ArkUI todo list page into MVVM architecture using V2 state management with proper Model, ViewModel, and View separation.