What problem does it solve? HarmonyOS developers often guess at system APIs, permission flows, and Kit imports, producing code that fails against the actual SDK. This Skill provides a structured framework for using HarmonyOS system capabilities correctly, with a strict rule to verify every interface against official documentation before writing code. ## Core Features & Use Cases - Ability and Page Routing Guidance: Covers the Stage model, UIAbility lifecycle callbacks, router-based navigation, and multi-module (HAR/HSP) routing considerations. - Permission Model Reference: Explains permission declaration in module.json5, normal versus system_basic levels, and dynamic user authorization via abilityAccessCtrl with denial handling. - Capability Framework Map: Maps common needs (notifications, background tasks, ArkData storage, files, networking, media, distributed services, security) to the correct HarmonyOS Kits. - Use Case: When adding a local notification feature to a HarmonyOS app, follow the Skill to declare the right permission, use Notification Kit, verify the exact module import with dcli__api_lookup, and release resources in the correct lifecycle callback. ## Quick Start Ask the agent to implement a HarmonyOS feature such as requesting camera permission dynamically and showing a local notification, following the system capabilities guidelines.
