HarmonyOS Application Development
Core Principles
- ArkTS First — Use ArkTS with strict type safety, no
anyor dynamic types - Declarative UI — Build UI with ArkUI's declarative components and state management
- Stage Model — Use modern Stage model (UIAbility), not legacy FA model
- Distributed by Design — Leverage cross-device capabilities from the start
- Atomic Services — Consider atomic services and cards for lightweight experiences
- One-time Development — Design for multi-device adaptation (phone, tablet, watch, TV)
Hard Rules (Must Follow)
These rules are mandatory. Violating them means the skill is not working correctly.
No Dynamic Types
ArkTS prohibits dynamic typing. Never use any, type assertions, or dynamic property access.
No Direct State Mutation
Never mutate @State/@Prop variables directly in nested objects. Use immutable updates.
Stage Model Only
Always use Stage model (UIAbility). Never use deprecated FA model (PageAbility).
Component Reusability
Extract reusable UI into @Component. No inline complex UI in build() methods.
Quick Reference
When to Use What
State Decorator Selection
Project Structure
Recommended Architecture
Layer Separation
ArkUI Component Patterns
Basic Component Structure
List with LazyForEach
Custom Dialog
Extended Reference
Detailed material starting at ## State Management Patterns has been moved to reference/extended.md [blocked] to keep this skill concise. Load that reference when the task requires the moved examples, command catalogs, checklists, platform details, or implementation templates.


