ohos-system-dev
OpenHarmony System Dev
Platform work has its own rules that normal-app development doesn't. A system/persistent
bundle (systemui, launcher, a gesture-nav service) is not reloaded by reinstalling it —
it reloads on reboot — and it's signed/installed differently. This skill captures that
loop. Everything routes through the devecocli CLI where the documented commands support it (cross-platform; stdout=results,
stderr=logs) with raw hdc / bm / param as the escape hatch.
Platform builds assume access to an OHOS source tree and a device/emulator that accepts system bundles (a dev image, or
system_appsigning). Paths likeapplications/standard/systemuibelow are illustrative.
Windows toolchain selection
Require the caller's PATH to put the DevEco Studio Node directory first, followed by
the npm global bin directory and DevEco toolchain directories. Do not hard-code, probe,
or modify installation paths in this skill. Verify the resolved tools: