What problem does it solve? Writing HarmonyOS ArkUI pages requires choosing the correct layout components, state decorators, and lifecycle hooks; picking the wrong pattern causes broken UI updates, unnecessary re-renders, and ArkTS type errors. ## Core Features & Use Cases - Layout & Component Reference: Covers Column, Row, Stack, Scroll, List, Grid, Tabs, Navigation, and common attributes and events for building ArkUI pages. - State Management Guidance: Explains V1 decorators (@State, @Prop, @Link, @Provide/@Consume, @Observed/@ObjectLink, @Watch, @StorageLink) and V2 decorators (@ComponentV2, @Local, @Param, @Event, @ObservedV2/@Trace), with rules for when to use each. - Lifecycle & Performance Patterns: Documents component and page lifecycle callbacks, ForEach/LazyForEach key requirements, dialogs, animations, and a verification checklist including dcli__lsp_check validation. - Use Case: When building a new HarmonyOS settings page with a scrollable list bound to shared app state, load this Skill to select the right layout, apply @Provide/@Consume for cross-level state, and verify the ArkTS code compiles cleanly. ## Quick Start Load the arkui-state skill and help me build an ArkUI list page in ArkTS that uses @State and @Link to sync a selected item between parent and child components.
