Use for HarmonyOS/OpenHarmony ArkTS code work when Codex needs official documentation and samples to answer `.ets` syntax, state management, component semantics, migration, compile-error, API-usage, or legacy ArkUI maintenance questions, including ArkTS compile failures inside `ohosTest` test code. Trigger on `.ets` files, ArkTS decorators, `@kit` or `@ohos` APIs, HarmonyOS/OpenHarmony context, `@ComponentV2`, `@ObservedV2`, `@Trace`, `@Local`, `@Param`, `@Event`, `@LocalBuilder`, `@State`, `@Prop`, `@Link`, `@Provide`, `@Consume`, `@StorageLink`, `@StorageProp`, `@Watch`, or when V1/V2 state-management choices or strict ArkTS typing are relevant inside code.
Use when Codex needs to turn an empty or partial HarmonyOS/OpenHarmony project into a complete working application or demo-ready sample. Covers official Stage-model project setup, directory layout, DevEco configuration, ArkTS UI architecture, state-management choices, test expectations for complete or validation-oriented apps, ability and native integration boundaries, and staged verification. Trigger on requests to build a HarmonyOS app from scratch, scaffold a project, complete an unfinished app, create a sample app, set up DevEco or hvigor structure, add abilities or native integration, or define a project architecture and delivery plan.
Use when Codex needs official HarmonyOS/OpenHarmony SDK toolchain workflows for build output generation, packaging, install, launch, signing, logs, device-debug, or build-deploy troubleshooting based on local developer documentation. Trigger on DevEco SDK command-line tool usage, `hdc`, `bm`, `aa`, `hilog`, `packing-tool`, HAP/HSP/APP packaging, signing, device install, launch, test-package install, or troubleshooting around API compatibility, SysCap, signing, or device deployment where Codex should prefer local official docs over third-party wrappers.
Use when Codex needs official HarmonyOS/OpenHarmony Test Kit workflows for ArkTS unit tests, UI tests, performance tests, test-runner wiring, or command-line test execution, including deciding the minimum test surface for complete or validation-oriented app samples. Trigger on `@ohos/hypium`, `@kit.TestKit`, `@ohos.UiTest`, `Driver`, `ON`, `aa test`, `ohosTest`, `testRunner`, `OpenHarmonyTestRunner`, unit-test, UI-test, performance-test, test coverage, or when Codex should follow local official docs and samples for HarmonyOS testing.
Use when the user needs HarmonyOS or OpenHarmony app UI/UX design guidance, design review, page structure advice, navigation choices, responsive or adaptive layout decisions, multimodal input consistency, component semantics, editing-flow decisions, visual rules, motion rules, or a pre-implementation or post-implementation design audit against HarmonyOS app design specifications.