harmonyos-dev-suite

Use devecocli commands such as devecocli build, devecocli run, and devecocli device list, which this Skill prefers over direct hvigor or hdc calls. Identify the project root via build-profile.json5 or oh-package.json5 before running any build command.

Classify the artifact first as a JS crash, C++ crash, app freeze, API fault, or memory leak, then route to the matching DFX atomic Skill such as hmos-jscrash-analysis or hmos-appfreeze-analysis. Preserve raw faultlog files and stack traces before proposing fixes.

Atomic Skills are 83 optional specialist Skills indexed in the catalog, covering areas like ArkUI development, Push Kit, multi-device adaptation, and testing. Install one only when a task requires repeated deep specialization, using the install_atomic_skill.py script with a local source checkout.

Yes, it routes multi-device tasks through hmos-multidevice-scenario-entry and classifies issues into screen/window size, fold state, avoid areas, natural orientation, interaction methods, or hardware access. Specialist atomic Skills handle each adaptation category.

Yes, it prefers the official HarmonyOS Developer Knowledge MCP using searchDocuments followed by getDocumentsById for full content, limited to 10 documents per call. When the MCP is unavailable, it falls back to devecocli docs search and devecocli docs read.

Avoid running builds, emulators, or log following without a confirmed project path and clear user intent, as the Skill's safety rules require project detection first. For pure conceptual questions, it answers as guidance rather than executing device commands.