You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The skill teaches the AI everything needed to read, write, review, and debug HarmonyOS NEXT native apps (**4,440 lines of dense, actionable knowledge, 242 sections, 105+ code examples**):
120
+
The skill teaches the AI everything needed to read, write, review, and debug HarmonyOS NEXT native apps (**4,450 lines of dense, actionable knowledge, 242 sections, 105+ code examples**):
- UX testing supports multi-device layout comparison across straight-screen and foldable devices.
145
145
- Test-service matrix includes local app listing precheck, performance baseline/monitoring, stability baseline, memory-leak testing, UX baseline and multi-device layout comparison, security baseline, power baseline, functional-experience baseline, exploratory testing, regression testing, device projection, UIViewer, app graph management, performance report auto-analysis, and report comparison.
146
146
147
+
**HarmonyOS AI development tools and capability highlights (officially surfaced 2026/06):**
148
+
-**DevEco Code** — a HarmonyOS-focused AI coding Agent for planning, code generation, build/run, device logs, UI verification, ArkTS checking, knowledge lookup, debugging, and iterative repair. It complements DevEco Studio rather than replacing the SDK/toolchain.
149
+
-**DevEco CLI** — Agent-friendly command-line access to project creation, syntax checks, build, device run/debug, and other HarmonyOS engineering actions; use it for third-party coding Agents, automation, and CI/CD integration.
150
+
-**Agent Framework Kit** — launches a combination of system Agents from an app through UI controls. Keep it distinct from Intents Kit (declaring app intents), ArkTS script-based app Skills (exposing app capabilities), and device-side A2A (Agent-to-Agent communication).
151
+
-**HarmonyOS 7 experience areas** — spatial-audio processing nodes, app/game quick start, cold-start network preconnection, QUIC and weak-network live-stream optimization, and LTPO variable frame rate are highlighted platform capabilities; confirm the installed API 26 SDK and device support before presenting them as generally available APIs.
152
+
-**API 26 cloud debugging** — AGC remote-device cloud debugging can filter devices by API 26 or system version `7.0.0.23` for early compatibility validation.
153
+
154
+
For tool selection, capability boundaries, and answer rules, read `references/ai-development-tools.md`.
155
+
147
156
### Official documentation updates (2026/06/12)
148
157
149
158
Huawei's release docs did not add a newer SDK after 26.0.0 Beta1, but the documentation change log added several developer-facing guides worth surfacing in answers:
@@ -4448,6 +4457,7 @@ The root `SKILL.md` remains the discovery entry. These files are loaded only whe
4448
4457
| User intent | Read first | Then read |
4449
4458
|---|---|---|
4450
4459
| Version, SDK, DevEco Studio, API baseline |`platform-baseline.md`|`api26-preview.md` only for preview requests |
| Scriptable project, build, check, device, and debugging actions for Agents or CI/CD | DevEco CLI |
4489
+
| General-purpose third-party coding Agent | Its native workflow plus DevEco CLI/Hvigor/HDC and this skill |
4490
+
4491
+
DevEco Code is a HarmonyOS-focused coding Agent, while DevEco CLI is the execution layer designed for command-line automation and Agent invocation. Neither changes the production SDK baseline: use API 24 Release by default and API 26 Beta1 only for preview/adaptation work.
4492
+
4493
+
## Agent capability boundaries
4494
+
4495
+
| Capability | Purpose |
4496
+
|---|---|
4497
+
| Agent Framework Kit | Let an app actively launch system Agent combinations through UI controls |
4498
+
| Intents Kit | Declare app or atomic-service functions as system-recognizable intents |
4499
+
| ArkTS script-based app Skill | Expose app business capabilities to system intelligent entry points through a declared contract |
4500
+
| Device-side A2A | Connect an app-side Agent with system Agents using registered components, authenticated bidirectional communication, and interactive UI |
4501
+
| AgentCard | Present Agent-related content or interaction through supported card capabilities |
4502
+
4503
+
Do not use these names interchangeably. First identify whether the user needs UI-triggered Agent invocation, intent exposure, an app Skill, Agent-to-Agent communication, or card presentation.
- Treat marketing-level capability descriptions as discovery signals, not stable API signatures. Verify the API 26 SDK reference, device category, permissions, and feature availability before generating production code.
4510
+
- For AGC cloud debugging, filter remote devices by API 26 or system version `7.0.0.23` when validating HarmonyOS 7 compatibility.
4511
+
4512
+
## Answer rules
4513
+
4514
+
1. State whether the request is about DevEco Studio, DevEco Code, DevEco CLI, or a third-party Agent.
4515
+
2. Keep API 24 production guidance separate from API 26 Beta preview guidance.
4516
+
3. Name the exact Agent capability layer instead of using generic terms such as "HarmonyOS Agent API."
4517
+
4. Do not invent DevEco CLI command names. Use installed-tool help or official documentation for exact commands and flags.
4518
+
5. For device-dependent capabilities such as LTPO or spatial audio, require SDK and hardware support verification.
- UX testing supports multi-device layout comparison across straight-screen and foldable devices.
157
158
- Test-service matrix includes local app listing precheck, performance baseline/monitoring, stability baseline, memory-leak testing, UX baseline and multi-device layout comparison, security baseline, power baseline, functional-experience baseline, exploratory testing, regression testing, device projection, UIViewer, app graph management, performance report auto-analysis, and report comparison.
158
159
160
+
**HarmonyOS AI development tools and capability highlights (officially surfaced 2026/06):**
161
+
-**DevEco Code** — a HarmonyOS-focused AI coding Agent for planning, code generation, build/run, device logs, UI verification, ArkTS checking, knowledge lookup, debugging, and iterative repair. It complements DevEco Studio rather than replacing the SDK/toolchain.
162
+
-**DevEco CLI** — Agent-friendly command-line access to project creation, syntax checks, build, device run/debug, and other HarmonyOS engineering actions; use it for third-party coding Agents, automation, and CI/CD integration.
163
+
-**Agent Framework Kit** — launches a combination of system Agents from an app through UI controls. Keep it distinct from Intents Kit (declaring app intents), ArkTS script-based app Skills (exposing app capabilities), and device-side A2A (Agent-to-Agent communication).
164
+
-**HarmonyOS 7 experience areas** — spatial-audio processing nodes, app/game quick start, cold-start network preconnection, QUIC and weak-network live-stream optimization, and LTPO variable frame rate are highlighted platform capabilities; confirm the installed API 26 SDK and device support before presenting them as generally available APIs.
165
+
-**API 26 cloud debugging** — AGC remote-device cloud debugging can filter devices by API 26 or system version `7.0.0.23` for early compatibility validation.
166
+
167
+
For tool selection, capability boundaries, and answer rules, read `references/ai-development-tools.md`.
168
+
159
169
### Official documentation updates (2026/06/12)
160
170
161
171
Huawei's release docs did not add a newer SDK after 26.0.0 Beta1, but the documentation change log added several developer-facing guides worth surfacing in answers:
| Scriptable project, build, check, device, and debugging actions for Agents or CI/CD | DevEco CLI |
12
+
| General-purpose third-party coding Agent | Its native workflow plus DevEco CLI/Hvigor/HDC and this skill |
13
+
14
+
DevEco Code is a HarmonyOS-focused coding Agent, while DevEco CLI is the execution layer designed for command-line automation and Agent invocation. Neither changes the production SDK baseline: use API 24 Release by default and API 26 Beta1 only for preview/adaptation work.
15
+
16
+
## Agent capability boundaries
17
+
18
+
| Capability | Purpose |
19
+
|---|---|
20
+
| Agent Framework Kit | Let an app actively launch system Agent combinations through UI controls |
21
+
| Intents Kit | Declare app or atomic-service functions as system-recognizable intents |
22
+
| ArkTS script-based app Skill | Expose app business capabilities to system intelligent entry points through a declared contract |
23
+
| Device-side A2A | Connect an app-side Agent with system Agents using registered components, authenticated bidirectional communication, and interactive UI |
24
+
| AgentCard | Present Agent-related content or interaction through supported card capabilities |
25
+
26
+
Do not use these names interchangeably. First identify whether the user needs UI-triggered Agent invocation, intent exposure, an app Skill, Agent-to-Agent communication, or card presentation.
- Treat marketing-level capability descriptions as discovery signals, not stable API signatures. Verify the API 26 SDK reference, device category, permissions, and feature availability before generating production code.
33
+
- For AGC cloud debugging, filter remote devices by API 26 or system version `7.0.0.23` when validating HarmonyOS 7 compatibility.
34
+
35
+
## Answer rules
36
+
37
+
1. State whether the request is about DevEco Studio, DevEco Code, DevEco CLI, or a third-party Agent.
38
+
2. Keep API 24 production guidance separate from API 26 Beta preview guidance.
39
+
3. Name the exact Agent capability layer instead of using generic terms such as "HarmonyOS Agent API."
40
+
4. Do not invent DevEco CLI command names. Use installed-tool help or official documentation for exact commands and flags.
41
+
5. For device-dependent capabilities such as LTPO or spatial audio, require SDK and hardware support verification.
0 commit comments