ArkUI Scenario Development

Skill Definition

Field	Content
`skill_id`	`arkui-scenario-development`
`skill_name`	`ArkUI Scenario Development`
`one_line_purpose`	Covers ArkUI basic syntax, UI framework logic, state management, compilation and runtime. Uses route documents for interaction, focus, navigation, page construction, V1/V2 state management, component synchronization, dialogs, menus, animation, custom components, layouts, images, lists, and text.
`not_in_scope`	Native development unrelated to ArkUI, non-HarmonyOS development, and CI/CD configuration.
`primary_outputs`	`primary_scene`, `implementation_notes`, `code_touchpoints`, `verification_matrix`

Handle only ArkUI / ArkTS .ets pages, components, interactions, state, navigation, dialogs, animation, layout, images, lists, text, compilation, and runtime tasks.
Do not handle unrelated native system capabilities, back-end APIs, databases, CI/CD, release workflows, or non-HarmonyOS development. Classify requests limited to those areas as not_in_scope.
When ARKUI-02 or ARKUI-03 is matched, read its route document and complete the secondary routing. If several secondary scenes match, record and read all of them.
Before presenting a solution or code, provide the routing result, phase, matched scenes, and resource paths to be read. Do not skip routing and go directly to implementation.
Base the solution or code on the matched resource documents, including their APIs, component structure, callbacks, lifecycle rules, and verification points. Explicitly state any uncovered boundary.