Skip to content

Coverage Matrix

Reference doc — auto-synced from the harmony-app-dev AgentSkill. Source: references/coverage.md

Purpose

This file is the official coverage map for harmony-app-dev. It records:

  • the canonical first-level structure of the official HarmonyOS docs (Guides + References)
  • which official categories this skill currently covers
  • which categories are missing
  • recommended priority for filling the gaps

This file is the source of truth for skill completeness. All gap planning, audit work, and roadmap discussion should refer to this file.

How to use this file

When asked “is this skill complete?” or “do we have X capability covered?”:

  1. find the matching official category below
  2. check the Local file column
  3. if missing, follow the Priority column to plan the gap fill

When adding a new reference file:

  1. confirm which official category it serves
  2. add or update the row in this table
  3. include at least one official URL in the new reference file

Official documentation roots

SectionURL
Docs homehttps://developer.huawei.com/consumer/cn/doc/
Designhttps://developer.huawei.com/consumer/cn/doc/design-guides/
Guideshttps://developer.huawei.com/consumer/cn/doc/harmonyos-guides-V5
References (API)https://developer.huawei.com/consumer/cn/doc/harmonyos-references-V6
Release Noteshttps://developer.huawei.com/consumer/cn/doc/harmonyos-releases-V6
AppGallery Connecthttps://developer.huawei.com/consumer/cn/agconnect/

Version note: HarmonyOS docs are versioned. Guides are commonly seen under V5, References under V6, and newer iterations may exist (V14 etc.). Always verify the current valid version when implementing version-sensitive features.

Coverage matrix — Guides (first-level domains)

Status legend:

  • ✅ covered — has a dedicated reference file with at least one official URL
  • 🟡 partial — mentioned but lacks depth or official URL anchoring
  • ❌ missing — no dedicated reference file
  • 🟦 intentionally out of scope — currently not in skill scope (will be revisited)
#Official domain (Guides)Local fileStatusPriority
1应用模型 (Application Model / Stage 模型)app-model.md✅ coveredmaintain
2应用程序包 (HAP / HAR / HSP)packaging.md✅ coveredmaintain
3UI 开发 (ArkUI 声明式 UI)ui-implementation-rules.md, visual-effects-recipes.md, example-cookbook.md, component-library-policy.md✅ coveredmaintain
4UI 设计 (Design / HarmonyOS Design)ui-design.md✅ coveredmaintain
5资源管理 (Resource Manager)resource-management.md✅ coveredmaintain
6权限管理 (Ability Kit / Permissions)permissions.md✅ coveredmaintain
7网络 (Network Kit / @ohos.net.http)network.md✅ coveredmaintain
8数据管理 (ArkData: Preferences / RDB / KV)persistence.md✅ coveredmaintain
9文件管理 (Core File Kit)file-management.md✅ coveredmaintain
10媒体 (Camera Kit / Image Kit / Audio / Media Library)media-and-camera.md✅ coveredmaintain
11通知 (Notification Kit)notification.md✅ coveredmaintain
12后台任务 (Background Tasks Kit)background-tasks.md✅ coveredmaintain
13位置 (Location Kit)location.md✅ coveredmaintain
14安全 (Universal Keystore / 加密 / 隐私)security-and-privacy.md✅ coveredmaintain
15分布式 (Distributed Service Kit / 流转 / 分布式数据)distributed.md✅ coveredmaintain
16Widget / 服务卡片 (FormExtensionAbility)widget.md, widget-cookbook.md✅ coveredmaintain
17元服务 (Atomic Service)atomic-service.md✅ coveredmaintain
18ArkTS 语言 (Language)arkts-language.md✅ coveredmaintain
19ArkUI 状态管理 (@State / @Prop / @Link / AppStorage …)state-management.md✅ coveredmaintain
20ArkUI 动画 / 转场 / 手势animation-and-gesture.md, ui-implementation-rules.md, visual-effects-recipes.md✅ coveredmaintain
21Canvas / 2D 绘制canvas.md, visual-effects-recipes.md✅ coveredmaintain
22ArkGraphics 3Dgraphics-3d.md✅ coveredmaintain
23多媒体感知 (Multimodal Awareness Kit)official-api-examples.md🟡 partialP2
24并发 (TaskPool / Worker)concurrency.md✅ coveredmaintain
25调试与性能 (DevEco Studio / HiLog / Profiler)debugging.md✅ coveredmaintain
26测试 (HarmonyOS Test Framework)testing.md✅ coveredmaintain
27上架与发布 (AppGallery Connect)publishing.md✅ coveredmaintain
28国际化 (i18n / l10n)i18n.md✅ coveredmaintain
29无障碍 (Accessibility)accessibility.md✅ coveredmaintain
30跨设备 (手机 / 手表 / 平板 / 车机 / 电视)cross-device.md✅ coveredmaintain

Coverage matrix — Skill-internal supporting files

These are not direct mirrors of official categories but are part of the skill workflow.

FilePurposeStatus
capability-map.mdclassify a request into an official capability domainneeds expansion to list every domain in this matrix
api-watch.mdreminder that official docs are the source of truthOK
official-search-playbook.mdhow to look up exact APIs from official docsOK
official-api-examples.mdconfirmed official URLs for high-frequency APIsshould grow over time
coverage.mdthis filecurrent

Current coverage summary (audit baseline)

  • official Guides domains in scope: 30
  • domains fully covered (✅): 29
  • domains partially covered (🟡): 1 (Multimodal Awareness)
  • domains missing (❌): 0
  • coverage ratio (full only): ~97%
  • coverage ratio (full + partial): 100%

🎉 30/30 全部覆盖。

Priority guidance

P0 — must-have engineering capability files

Any real HarmonyOS app will block on these. These are the highest-ROI gaps to fill first:

  • permissions.md ✅ done
  • network.md ✅ done
  • persistence.md ✅ done
  • media-and-camera.md ✅ done
  • notification.md ✅ done
  • state-management.md ✅ done

P0 全部完成。

P1 — common but secondary

Important for full-featured apps:

  • location.md ✅ done
  • concurrency.md ✅ done
  • security-and-privacy.md ✅ done
  • background-tasks.md ✅ done
  • file-management.md ✅ done
  • testing.md ✅ done
  • debugging.md ✅ done
  • publishing.md ✅ done
  • widget-cookbook.md ✅ done
  • app-model.md ✅ done (upgraded)
  • animation-and-gesture.md ✅ done
  • canvas.md ✅ done
  • distributed.md ✅ done

P1 全部完成。

P2 — long tail

Cover when product work touches them:

  • arkts-language.md ✅ done
  • atomic-service.md ✅ done
  • resource-management.md ✅ done
  • ui-design.md ✅ done (mapped from design-guidelines)
  • i18n.md ✅ done
  • accessibility.md ✅ done
  • cross-device.md ✅ done
  • packaging.md ✅ done (mapped from hap-har-hsp)

P2 全部完成。

Audit rules

  1. Every reference file should declare which official category it maps to.
  2. Every reference file should include at least one official URL.
  3. New reference files must update this matrix.
  4. Removed reference files must update this matrix.
  5. When the official Guides structure changes, update the matrix first, then plan content changes.