hmos-arkui-scenario-development

Route HarmonyOS ArkUI development tasks to scenario-based implementation references and code patterns.

2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill hmos-arkui-scenario-development-iskenkenya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hmos-arkui-scenario-development
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/harmonyos/development/application-framework/ArkUI/hmos-arkui-scenario-development
Command: npx skills add https://github.com/IsKenKenYa/skills --skill hmos-arkui-scenario-development-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? HarmonyOS ArkUI development spans dozens of APIs, decorators, and component patterns, making it hard to know which approach fits a given task. This Skill routes any ArkUI (.ets) request through a structured decision tree to the correct scenario documentation, then generates implementations grounded in verified API usage rather than guesswork. ## Core Features & Use Cases - Four-Stage Phase Routing: Classifies every request into REQ (requirements), DEV (development), FIX (bug fixing), or VAL (validation) phases with stage-specific output fields. - Four Primary Scenarios: Covers ArkUI basic syntax (declarative UI, Builder, AttributeModifier, component reuse), UI framework logic (gestures, navigation, dialogs, animations, focus, layouts, lists, text), state management (V1/V2 decorators, mixing, extensions), and compile/runtime issues (build failures, ANR, white screen, crashes, jank). - Cascading Reference Reading: Automatically reads ROUTE documents and leaf reference files containing complete code examples, API tables, and forbidden-pattern lists before writing any code. - Use Case: When a user reports "long list stutters during scrolling", the Skill routes to ARKUI-04, reads the rendering jank scenario doc, and produces a fix using @Reusable with reuseId, @ObjectLink instead of @Prop, and LazyForEach partial refresh. ## Quick Start Ask the assistant to implement or diagnose an ArkUI page, such as building a responsive app skeleton with Navigation and breakpoint adaptation for phones and tablets.

Frequently Asked Questions about hmos-arkui-scenario-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement ArkUI state management with V1 and V2 decorators?

Use V1 decorators (@State, @Prop, @Link, @Provide/@Consume) or V2 decorators (@Local, @Param, @Event, @Monitor, @Computed) depending on project needs. The Skill routes state questions to ARKUI-03, which covers basic usage, V1/V2 mixing via bridging, and extension capabilities like UIUtils and Environment.

How to fix ArkUI list scrolling jank and dropped frames?

List jank is typically fixed by enabling @Reusable with reuseId for component reuse, replacing @Prop with @ObjectLink to avoid deep copies, and using LazyForEach partial refresh instead of notifyDataReload. The Skill's ARKUI-04 scenario documents these patterns with Profiler-based diagnosis steps.

What ArkUI layout component should I use for responsive multi-device pages?

Use GridRow/GridCol for responsive column adaptation, RelativeContainer for flat anchor-based layouts, and Navigation with breakpoint systems for phone/tablet skeletons. The Skill's scenario docs include a layout selection comparison table covering Column, Row, Stack, Flex, DynamicLayout, and Tabs.

Does this Skill cover non-ArkUI HarmonyOS native development?

No. The Skill explicitly scopes itself to ArkUI/ArkTS .ets pages, components, interactions, state, routing, dialogs, animations, layouts, and compile/runtime issues. Native system capabilities, backend interfaces, databases, CI/CD, and non-HarmonyOS platforms are declared out of scope.

Why does my ArkUI animation or transition not play?

Common causes include missing state changes inside animateTo callbacks, transitions not bound to conditionally rendered components, or geometryTransition used outside animateTo without disabling default transitions. The Skill routes these to ARKUI-02-05 and checks trigger conditions and performance impact.