@harmonyos-arkts/opencode-plugin 0.0.6-beta → 0.0.7

package/dist/index.js

@@ -14860,7 +14860,7 @@ var HM_DEVELOP = `
 ### Development Phase
 - Use the \`harmonyos-atomic-dev\` skill to implement features according to the design document for harmonyos atomic service
 - Use the \`harmonyos-atomic-dev\` skill to fix issues and modify function in current projects
-- Use the createHmTemplate tool to create empty applicaiton\u3001module\u3001atomic
+- Use the createHmTemplate tool to create empty applicaiton\u3001module\u3001atomic. After creation, use parallel Read tool calls to read the template's README.md and key files of the current project simultaneously \u2014 do NOT use glob/grep to explore the template.
 - Use the \`.harmonyos/\` file (*.md\u3001*.html) as references to generate
 - After completing development, you MUST proceed to the Build phase
 - **NO EXCEPTIONS**: Code must be built successfully before marking development as complete
@@ -14885,22 +14885,118 @@ var HM_BUILD = `
   5. If still failing after 3 attempts, report the remaining errors to the user and ask for guidance
 - Only after a successful build should the development cycle be considered complete
 `;
-var HM_ASCF = `
-### ASCF Phase
-- HM_ASCF is the default active environment. Treat all requests as ASCF-context tasks unless the user explicitly asks to switch domain.
-- Skill routing is mandatory and must be explicit before execution. Never handle ASCF tasks without selecting one of the ASCF skills first.
-- Use \`harmonyos-atomic-ascf-convert\` for mini-program to HarmonyOS Atomic Service conversion (migration, API mapping, directory and component adaptation, conversion implementation).
-- Use \`harmonyos-ascf-knowledge\` for ASCF development guidance, technical Q&A, issue localization, and troubleshooting in existing ASCF projects.
-- For mixed requests, execute in two stages: (1) conversion via \`harmonyos-atomic-ascf-convert\`, then (2) engineering verification and issue diagnosis via \`harmonyos-ascf-knowledge\`.
-- If the request is "how to", "why it fails", "where the issue is", or "how to fix", always prioritize \`harmonyos-ascf-knowledge\`.
-- If a selected skill returns insufficient context, immediately continue with the other ASCF skill as fallback, then merge results into a single ASCF-oriented answer.
-`;
 var HM_ONE2MANY = `
 ### One-to-Many Adaptation Phase
 - Use the \`harmonyos-one2many-adapt\` skill to adapt the HarmonyOS application for multiple device types (phone, tablet, foldable, 2-in-1, wearable, TV)
 - After completing adaptation, you MUST proceed to the Build phase
 - **NO EXCEPTIONS**: Code must be built successfully before marking adaptation as complete
 `;
+var HM_PLAN = `
+### Plan Phase
+You are a **planning specialist** for HarmonyOS projects. Your sole responsibility is to ANALYZE, PLAN, and DOCUMENT.
+
+**CRITICAL RULES (you MUST follow these):**
+1. You MUST follow ALL steps below in strict order. Do not skip any step.
+2. You MUST NOT write any implementation code or create/edit source files (except the plan document).
+3. You MUST write the final plan to \`.harmonyos/plan.md\`.
+4. After outputting the plan, STOP and wait for user/approver feedback. Do NOT proceed to development yourself.
+
+---
+
+**Step 1: Explore the Codebase**
+
+Thoroughly explore the existing project to understand:
+- Directory structure and file organization (use Glob)
+- Architecture patterns \u2014 look for @ComponentV2/@ObservedV2, MVVM, state management singletons
+- Page routing setup (main_pages.json, route_map.json)
+- Existing models, stores, and data flow
+- Any existing features similar to what's being requested
+- module.json5 for permissions and ability configuration
+- Entry point (EntryAbility) and initial page loading
+
+If \`.harmonyos/codebase.md\` exists, read it first for cached analysis.
+
+**Step 2: Analyze Requirements**
+
+Break down the user's request into:
+- Core features and sub-features
+- Dependencies between tasks (what must be done before what \u2014 use explicit "depends on Step N" markers)
+- Technical constraints (HarmonyOS NEXT API availability, Kit compatibility, permission requirements)
+- Impact analysis: which existing files need modification vs which are new files
+
+Output a dependency-ordered task list.
+
+**Step 3: Create the Development Plan**
+
+Write a structured plan to \`.harmonyos/plan.md\` using this template:
+
+\`\`\`markdown
+# Development Plan: [Feature Name]
+
+## Overview
+[1-2 sentence summary of what will be implemented]
+
+## Current Architecture Summary
+[Brief description of the relevant existing code that will be affected]
+
+## Implementation Steps
+
+### Step 1: [Clear Action Title]
+- **Objective**: [What this step accomplishes]
+- **Files to create**: [Full paths of new files, or "None"]
+- **Files to modify**: [Full paths of existing files to change, or "None"]
+- **Key changes**:
+  - [Specific code changes: new classes, methods, UI components]
+  - [APIs or Kits to use]
+  - [State management approach]
+  - [Configuration or permission updates]
+- **Acceptance criteria**: [How to verify this step is correctly completed]
+
+### Step 2: [Clear Action Title]
+[Same structure, with "depends on Step 1" if applicable]
+...
+
+## Risk & Considerations
+- [Potential issues, edge cases, or breaking changes to existing functionality]
+\`\`\`
+
+**Step 4: Present and Review**
+
+Output the plan content to the user in your response. Then conclude with:
+
+> Plan saved to \`.harmonyos/plan.md\`. Please review and confirm, or suggest adjustments before implementation begins.
+
+**STOP HERE. Do NOT proceed to implementation. The main agent or user will handle the next phase.**
+
+---
+
+**Granularity Guidelines:**
+- Simple tasks (1-2 files changed): 2-3 high-level steps
+- Medium tasks (3-5 files): 4-6 steps, one major file change per step
+- Complex tasks (6+ files or architectural changes): Fine-grained steps with explicit dependency chains
+- Each step MUST be independently verifiable
+- Group related changes that must be deployed together into the same step
+
+**Plan Output Example (for reference):**
+
+### Step 1: Add UserStore Model
+- **Objective**: Create shared user authentication state management
+- **Files to create**: entry/src/main/ets/model/UserStore.ets
+- **Files to modify**: None
+- **Key changes**:
+  - Create UserInfo interface and UserStore singleton with @ObservedV2/@Trace
+  - Add loginWithHuaweiID() method using @kit.AccountKit authentication
+  - Add logout() method
+- **Acceptance criteria**: UserStore exports getInstance(), isLoggedIn is reactive
+
+### Step 2: Create Splash Page with Countdown
+- **Objective**: Add splash screen that navigates based on login state
+- **Files to create**: entry/src/main/ets/pages/SplashPage.ets
+- **Files to modify**: entry/src/main/resources/base/profile/main_pages.json, entry/src/main/ets/entryability/EntryAbility.ets
+- **Key changes**:
+  - ... (depends on Step 1)
+- **Acceptance criteria**: App starts on SplashPage, countdown works, routes correctly
+`;
 function buildPlanPrompt(type) {
   switch (type) {
     case "dev":
@@ -14909,10 +15005,10 @@ function buildPlanPrompt(type) {
       return HM_DESIGN;
     case "build":
       return HM_BUILD;
-    case "ascf":
-      return HM_ASCF;
     case "one2many":
       return HM_ONE2MANY;
+    case "plan":
+      return HM_PLAN;
     case "all":
       return buildAllAgentPrompt();
     default:
@@ -14920,40 +15016,16 @@ function buildPlanPrompt(type) {
   }
 }
 function buildAllAgentPrompt() {
-  return `All HarmonyOS development tasks can be broadly categorized into three main phases: Design, Development, Build, and ASCF conversion. Each phase has its own set of best practices and workflows to ensure efficient and successful project completion.
+  return `All HarmonyOS development tasks can be broadly categorized into three main phases: Design, Development, Build. Each phase has its own set of best practices and workflows to ensure efficient and successful project completion.
 ${HM_DESIGN}
 ${HM_DEVELOP}
 ${HM_BUILD}
-${HM_ASCF}
 
 Follow these workflows:
 - **New project (greenfield)**: PRD Design \u2192 Development \u2192 Build.
-- **Incremental development (complex)**: Explore the project first \u2192 Use Plan Agent to list a plan \u2192 Discuss plan details with the user \u2192 Development \u2192 Build.
+- **Incremental development (complex)**: Use Plan Agent to list a plan \u2192 Discuss plan details with the user \u2192 Development \u2192 Build.
 - **Incremental development (simple)**: Development \u2192 Build directly.
-- **WeChat mini-program conversion**: ASCF Phase \u2192 Development \u2192 Build.`;
-}
-function buildHmExploreSubAgentPrompt() {
-  return `
-    You are a HarmonyOS project file search specialist. You excel at thoroughly navigating and exploring codebases.
-
-    Your strengths:
-    - Rapidly finding files using glob patterns
-    - Searching code and text with powerful regex patterns
-    - Reading and analyzing file contents
-
-    Guidelines:
-    - Use Glob for broad file pattern matching
-    - Use Grep for searching file contents with regex
-    - Use Read when you know the specific file path you need to read
-    - Use Bash for file operations like copying, moving, or listing directory contents
-    - Adapt your search approach based on the thoroughness level specified by the caller
-    - Return file paths as absolute paths in your final response
-    - For clear communication, avoid using emojis
-    - Create '\`.harmonyos/codebase.md\`' to write your findings, and you can also read '\`.harmonyos/codebase.md\`' if this existed
-    - Do not create any files except '\`.harmonyos/codebase.md\`', or run bash commands that modify the user's system state in any way
-
-    Complete the user's search request efficiently and report your findings clearly.
-  `;
+`;
 }
 function buildHmAgentPrompt(type) {
   return `You are HarmonyOS Dev Assistant(HDACode), an expert coding agent specialized in HarmonyOS development.
@@ -15097,9 +15169,6 @@ function createHmAgent() {
     prompt: buildHmAgentPrompt("all"),
     temperature: 0.3,
     permission: {
-      "task": {
-        "explore": "deny"
-      },
       "skillSearch": "deny"
     },
     metadata: void 0
@@ -15134,13 +15203,6 @@ function createDesignAgent() {
 }
 
 // src/agents/dev-agent.ts
-function getHmExploreSubAgentDescription() {
-  return `
-    Fast agent specialized for exploring codebases. 
-    Use this when you need to quickly find files by patterns (eg. "src/components/**/*.tsx"), search code for keywords (eg. "API endpoints"), or answer questions about the codebase (eg. "how do API endpoints work?"). 
-    When calling this agent, specify the desired thoroughness level: "quick" for basic searches, "medium" for moderate exploration, or "very thorough" for comprehensive analysis across multiple locations and naming conventions.
-  `;
-}
 function getHmDevDescription() {
   return `
     HarmonyOS Development
@@ -15155,72 +15217,12 @@ function createHmDevelopmentAgent() {
     prompt: buildHmAgentPrompt("dev"),
     temperature: 0.3,
     permission: {
-      "task": {
-        "explore": "deny"
-      },
       "skillSearch": "allow"
     },
     metadata: void 0
   };
   return agent;
 }
-function createHmExploreSubAgent() {
-  const agent = {
-    id: "harmonyos-explore",
-    name: "harmonyos-explore",
-    description: getHmExploreSubAgentDescription(),
-    mode: "subagent",
-    prompt: buildHmExploreSubAgentPrompt(),
-    temperature: 0.1,
-    permission: {
-      "*": "deny",
-      "grep": "allow",
-      "glob": "allow",
-      "list": "allow",
-      "bash": "allow",
-      "read": "allow",
-      "edit": {
-        "*.harmonyos/codebase.md": "allow"
-      },
-      "write": {
-        "*.harmonyos/codebase.md": "allow"
-      }
-    },
-    metadata: void 0
-  };
-  return agent;
-}
-
-// src/agents/ascf-agent.ts
-function getHmAscfDescription() {
-  return `
-      HarmonyOS ASCF assistant for mini-program conversion, ASCF development Q&A, and issue troubleshooting
-    `;
-}
-function createAscfAgent() {
-  const agent = {
-    id: "harmonyos-ascf",
-    name: "harmonyos-ascf",
-    description: getHmAscfDescription(),
-    mode: "primary",
-    prompt: buildHmAgentPrompt("ascf"),
-    temperature: 0.6,
-    permission: {
-      "skill": {
-        "*": "deny",
-        "harmonyos-atomic-ascf-convert": "allow",
-        "harmonyos-ascf-knowledge": "allow",
-        "huawei-payment-integration": "allow",
-        "harmonyos-atomic-service-filing": "allow",
-        "harmony-emulator-debugging": "allow",
-        "harmonyos-atomic-ascf-release": "allow"
-      },
-      "skillSearch": "deny"
-    },
-    metadata: void 0
-  };
-  return agent;
-}
 
 // src/agents/one2many-agent.ts
 function getHmOne2ManyDescription() {
@@ -15251,9 +15253,7 @@ var AgentRegistry = class {
     this.register(createHmAgent());
     this.register(createDesignAgent());
     this.register(createHmDevelopmentAgent());
-    this.register(createAscfAgent());
     this.register(createOne2ManyAgent());
-    this.register(createHmExploreSubAgent());
   }
   register(agent) {
     this.agents.set(agent.id, agent);
@@ -15385,22 +15385,7 @@ var AgentManager = class {
   }
 };
 
-// src/shared/ets-counter.ts
-import { readdir, readFile as readFile2, stat } from "fs/promises";
-import { join as join2, extname } from "path";
-async function countEtsLines(projectDir) {
-  const files = [];
-  const totalLines = files.reduce((sum, f) => sum + f.lines, 0);
-  return {
-    fileCount: files.length,
-    totalLines,
-    files,
-    timestamp: Date.now()
-  };
-}
-
 // src/managers/config-handler.ts
-var EXPLORE_ETS_THRESHOLD = 2e3;
 function mergePermission(target, source) {
   if (!target) return source;
   const result = { ...target };
@@ -15415,27 +15400,11 @@ function mergePermission(target, source) {
   }
   return result;
 }
-function createConfigHandler(_pluginConfig, agent, projectDir) {
+function createConfigHandler(_pluginConfig, agent, _projectDir) {
   return async (config3) => {
-    let exploreEnabled = true;
-    try {
-      const stats = await countEtsLines(projectDir);
-      exploreEnabled = stats.totalLines >= EXPLORE_ETS_THRESHOLD;
-      log("ETS count for explore agent", {
-        totalLines: stats.totalLines,
-        fileCount: stats.fileCount,
-        enabled: exploreEnabled
-      });
-    } catch (err) {
-      log("Failed to count ETS lines, enabling explore by default", { error: String(err) });
-    }
     const pluginAgents = agent.record();
     if (config3.agent) {
       for (const [id, pluginAgentConfig] of Object.entries(pluginAgents)) {
-        if (id === "harmonyos-explore" && !exploreEnabled) {
-          log("Skipping harmonyos-explore agent (insufficient .ets files)");
-          continue;
-        }
         if (config3.agent[id]) {
           const merged = { ...config3.agent[id], ...pluginAgentConfig };
           if (config3.agent[id].permission && pluginAgentConfig.permission) {
@@ -28038,6 +28007,86 @@ async function downloadTemplate(mode, filePath) {
   }
 }
 
+// src/shared/ets-counter.ts
+import { readdir, readFile as readFile2, stat } from "fs/promises";
+import { join as join2, extname } from "path";
+var SKIP_DIRS = /* @__PURE__ */ new Set([
+  "node_modules",
+  ".preview",
+  "build",
+  ".cxx",
+  ".gradle",
+  "oh_modules",
+  ".hvigor",
+  "entry/build"
+]);
+var HM_PROJECT_INDICATORS = ["build-profile.json5", "oh-package.json5"];
+var MAX_CONTENT_READ_FILES = 500;
+var ESTIMATED_LINES_PER_FILE = 100;
+async function isHarmonyOSProject(dir) {
+  for (const indicator of HM_PROJECT_INDICATORS) {
+    try {
+      await stat(join2(dir, indicator));
+      return true;
+    } catch {
+    }
+  }
+  return false;
+}
+async function collectEtsFilePaths(dir, results) {
+  let entries;
+  try {
+    entries = await readdir(dir, { withFileTypes: true });
+  } catch {
+    return;
+  }
+  for (const entry of entries) {
+    if (entry.isDirectory()) {
+      if (SKIP_DIRS.has(entry.name)) continue;
+      if (entry.name.startsWith(".") && entry.name !== ".ets") continue;
+      await collectEtsFilePaths(join2(dir, entry.name), results);
+    } else if (extname(entry.name) === ".ets") {
+      results.push(join2(dir, entry.name));
+    }
+  }
+}
+async function countEtsLines(projectDir) {
+  const startTime = Date.now();
+  if (!await isHarmonyOSProject(projectDir)) {
+    log("ets.count.skipped", { projectDir, elapsed: Date.now() - startTime });
+    return { fileCount: 0, totalLines: 0, files: [], timestamp: Date.now() };
+  }
+  const filePaths = [];
+  await collectEtsFilePaths(projectDir, filePaths);
+  const fileCount = filePaths.length;
+  if (fileCount > MAX_CONTENT_READ_FILES) {
+    const elapsed2 = Date.now() - startTime;
+    log("ets.count.estimated", { fileCount, estimatedLines: fileCount * ESTIMATED_LINES_PER_FILE, elapsed: elapsed2 });
+    return {
+      fileCount,
+      totalLines: fileCount * ESTIMATED_LINES_PER_FILE,
+      files: [],
+      timestamp: Date.now()
+    };
+  }
+  const files = [];
+  for (const filePath of filePaths) {
+    try {
+      const content = await readFile2(filePath, "utf-8");
+      files.push({ path: filePath, lines: content.split("\n").length });
+    } catch {
+    }
+  }
+  const elapsed = Date.now() - startTime;
+  log("ets.count.precise", { fileCount, totalLines: files.reduce((sum, f) => sum + f.lines, 0), elapsed });
+  return {
+    fileCount,
+    totalLines: files.reduce((sum, f) => sum + f.lines, 0),
+    files,
+    timestamp: Date.now()
+  };
+}
+
 // src/tools/create-template/ets-check.ts
 async function checkEtsExists(directory) {
   try {
@@ -28090,12 +28139,11 @@ function createHmTemplateTool(managers) {
 }
 
 // src/tools/skill-search/skill-search-tool.ts
-import { homedir as homedir3 } from "node:os";
+import { homedir as homedir2 } from "node:os";
 import { join as join4 } from "node:path";
 
 // src/tools/skill-search/search-skill.ts
 import { readFileSync } from "node:fs";
-import { homedir as homedir2 } from "node:os";
 import { join as join3 } from "node:path";
 
 // src/tools/skill-search/tokenizer.ts
@@ -28278,7 +28326,6 @@ var filter_default = [
 ];
 
 // src/tools/skill-search/search-skill.ts
-var DEFAULT_SKILL_PATH = join3(homedir2(), ".config", "opencode", "skills", "harmonyos-atomic-dev");
 var cachedEntries = null;
 var cachedIndexableEntries = null;
 var cachedFilters = null;
@@ -28300,10 +28347,9 @@ function loadAndCache(resolvedPath) {
   return true;
 }
 function searchSkill(skill_path, query, topK = 5) {
-  const resolvedPath = skill_path?.trim() || DEFAULT_SKILL_PATH;
   if (!cachedEntries) {
     try {
-      if (!loadAndCache(resolvedPath)) return [];
+      if (!loadAndCache(skill_path?.trim())) return [];
     } catch {
       return [];
     }
@@ -28314,9 +28360,7 @@ function searchSkill(skill_path, query, topK = 5) {
     if (idx !== -1) {
       preFiltered.push({
         ets_file_path: "",
-        experience_file_path: entry.path,
-        summary: entry.summary,
-        range: 0
+        experience_file_path: entry.path
       });
       query = (query.slice(0, idx) + query.slice(idx + category.length)).trim();
     }
@@ -28338,9 +28382,7 @@ function convert_search_result(searchResults) {
     );
     return {
       ets_file_path: entry.path,
-      experience_file_path: experience?.path ?? "",
-      summary: entry.summary,
-      range: rank + 1
+      experience_file_path: experience?.path ?? ""
     };
   });
 }
@@ -28348,9 +28390,9 @@ function convert_search_result(searchResults) {
 // src/tools/skill-search/skill-search-tool.ts
 function skillSearchTool(managers) {
   return tool({
-    description: "Search for relevant documents within the harmonyos-atomic-dev skill directory by keywords. Returns the top K most relevant document snippets from the skill directory, ranked by keyword match frequency. Use this tool instead of Glob/Grep when you need to find specific knowledge or documentation within harmonyos-atomic-dev skill. It scans all files under the given skill_path and returns the most relevant matches based on your query keywords. The results include ets_file_path (path to the ETS code examples), experience_file_path (path to the matching experience document best practices), summary (document summary), and range (relevance rank 1 = most relevant)\u3002",
+    description: "Search for relevant documents within the harmonyos-atomic-dev skill directory by keywords. Returns the top K most relevant document snippets from the skill directory, ranked by keyword match frequency. Use this tool instead of Glob/Grep when you need to find specific knowledge or documentation within harmonyos-atomic-dev skill. It scans all files under the given skill_path and returns the most relevant matches based on your query keywords. The results include ets_file_path (path to the ETS code examples), experience_file_path (path to the matching experience document best practices), summary (document summary), and range (relevance rank 1 = most relevant). QUERY TIPS: For best results, decompose your intent into short space-separated keywords instead of long sentences. Include: 1) Kit or component name (e.g. ScanKit, AdsKit, ShareKit), 2) specific API or method names (e.g. scanBarcode, loadAd, ShareController), 3) feature keywords (e.g. \u626B\u7801, \u5E7F\u544A\u52A0\u8F7D, \u5206\u4EAB). Example: 'ScanKit \u626B\u7801 scanBarcode startScanForResult' instead of '\u5E2E\u6211\u5B9E\u73B0\u4E00\u4E2A\u626B\u7801\u529F\u80FD'.",
     args: {
-      skill_path: tool.schema.string("Absolute path to the skill directory to search within. Default path may not contains harmonyos-atomic-dev skill").default(join4(homedir3(), ".config", "opencode", "skills", "harmonyos-atomic-dev")),
+      skill_path: tool.schema.string("Absolute path to the skill directory to search within. Default path may not contains harmonyos-atomic-dev skill").default(join4(homedir2(), ".config", "opencode", "skills", "harmonyos-atomic-dev")),
       query: tool.schema.string("A decomposed requirement or intent describing what you want to find, broken down into searchable keywords separated by spaces."),
       topK: tool.schema.number("Maximum number of top-ranked documents to return. Actual results may be fewer depending on query relevance.").min(1).max(5).default(5)
     },
@@ -28360,7 +28402,13 @@ function skillSearchTool(managers) {
         if (results.length === 0) {
           return "No relative items found in the skill directory.";
         }
-        return JSON.stringify(results, null, 2);
+        return results.map((r) => {
+          if (r.ets_file_path) {
+            return `${r.experience_file_path}
+\u793A\u4F8B\u6587\u4EF6\uFF1A${r.ets_file_path}`;
+          }
+          return r.experience_file_path;
+        }).join("\n\n");
       } catch (e) {
         return `Error: ${e instanceof Error ? e.message : String(e)}`;
       }

package/dist/templates/application/README.md

@@ -0,0 +1,52 @@
+# HarmonyOS Application Template
+
+HarmonyOS 标准应用工程模板，基于 Stage 模型，适用于开发完整的 HarmonyOS 应用程序。
+
+## 目录结构
+
+```
+application/
+├── AppScope/                          # 应用全局配置
+│   ├── app.json5                      # 应用包名、版本号、图标等全局信息
+│   └── resources/                     # 应用级资源（图标、字符串）
+├── entry/                             # 主模块（Entry Module）
+│   ├── src/
+│   │   ├── main/
+│   │   │   ├── ets/
+│   │   │   │   ├── entryability/      # UIAbility 入口
+│   │   │   │   ├── entrybackupability/# 备份恢复 ExtensionAbility
+│   │   │   │   └── pages/             # 页面（Index.ets）
+│   │   │   ├── resources/             # 模块资源（字符串、颜色、图片、配置）
+│   │   │   └── module.json5           # 模块配置（Ability、页面路由）
+│   │   ├── ohosTest/                  # 仪器化测试
+│   │   └── test/                      # 本地单元测试
+│   ├── build-profile.json5            # 模块级构建配置
+│   ├── oh-package.json5               # 模块依赖声明
+│   └── hvigorfile.ts                  # Hvigor 构建脚本
+├── hvigor/                            # Hvigor 构建引擎配置
+├── build-profile.json5                # 工程级构建配置（签名、SDK 版本、模块列表）
+├── oh-package.json5                   # 工程级依赖声明
+├── hvigorfile.ts                      # 工程级 Hvigor 脚本
+└── code-linter.json5                  # 代码检查配置
+```
+
+## 关键配置
+
+| 配置项 | 值 |
+|--------|-----|
+| bundleName | `com.example.app` |
+| module type | `entry` |
+| targetSdkVersion | `6.0.1(21)` |
+| runtimeOS | `HarmonyOS` |
+| installationFree | `false` |
+
+## 使用场景
+
+- 创建一个新的 HarmonyOS 标准应用工程
+- 包含完整的 UIAbility 生命周期管理
+- 内置备份恢复能力（EntryBackupAbility）
+- 适合需要独立安装和分发的应用
+
+## 使用方式
+
+此模板由 `createHmTemplate` 工具自动下载和解压，作为 HarmonyOS 应用开发的初始工程骨架。

package/dist/templates/atomic/README.md

@@ -0,0 +1,62 @@
+# HarmonyOS Atomic Service Template
+
+HarmonyOS 元服务（Atomic Service）工程模板，基于 Stage 模型，适用于开发免安装的轻量化服务。
+
+## 目录结构
+
+```
+atomic/
+├── AppScope/                          # 应用全局配置
+│   ├── app.json5                      # 应用包名、版本号（bundleType: "atomicService"）
+│   └── resources/                     # 应用级资源（图标、字符串）
+├── entry/                             # 主模块（Entry Module）
+│   ├── src/
+│   │   ├── main/
+│   │   │   ├── ets/
+│   │   │   │   ├── entryability/      # UIAbility 入口
+│   │   │   │   └── pages/             # 页面（Index.ets）
+│   │   │   ├── resources/             # 模块资源（字符串、颜色、图片、配置）
+│   │   │   └── module.json5           # 模块配置（Ability、页面路由）
+│   │   ├── ohosTest/                  # 仪器化测试
+│   │   ├── test/                      # 本地单元测试
+│   │   └── mock/                      # Mock 配置
+│   ├── build-profile.json5            # 模块级构建配置
+│   ├── oh-package.json5               # 模块依赖声明
+│   └── hvigorfile.ts                  # Hvigor 构建脚本
+├── hvigor/                            # Hvigor 构建引擎配置
+├── build-profile.json5                # 工程级构建配置（签名、SDK 版本、模块列表）
+├── oh-package.json5                   # 工程级依赖声明
+├── hvigorfile.ts                      # 工程级 Hvigor 脚本
+└── code-linter.json5                  # 代码检查配置
+```
+
+## 关键配置
+
+| 配置项 | 值 |
+|--------|-----|
+| bundleName | `com.atomicservice.example` |
+| bundleType | `atomicService` |
+| module type | `entry` |
+| targetSdkVersion | `6.0.1(21)` |
+| runtimeOS | `HarmonyOS` |
+| installationFree | `true` |
+
+## 与 Application 模板的区别
+
+| 特性 | Application | Atomic Service |
+|------|-------------|----------------|
+| bundleType | 默认（app） | `atomicService` |
+| installationFree | `false` | `true` |
+| 备份能力 | 包含 EntryBackupAbility | 不包含 |
+| 图标资源 | layered_image | app_icon |
+| 免安装 | 不支持 | 支持 |
+
+## 使用场景
+
+- 开发免安装的元服务（Atomic Service）
+- 适用于服务卡片、快捷服务、轻量级功能入口
+- 通过 HarmonyOS 服务分发平台进行分发
+
+## 使用方式
+
+此模板由 `createHmTemplate` 工具自动下载和解压，作为 HarmonyOS 元服务开发的初始工程骨架。

package/dist/templates/module/README.md

@@ -0,0 +1,42 @@
+# HarmonyOS Module Template
+
+HarmonyOS HAR（HarmonyOS Archive）库模块模板，用于开发可复用的共享库模块。
+
+## 目录结构
+
+```
+module/
+├── src/
+│   ├── main/
+│   │   ├── ets/
+│   │   │   └── components/            # 导出的组件（MainPage.ets）
+│   │   ├── resources/                 # 模块资源（字符串、浮点数）
+│   │   └── module.json5              # 模块配置（type: "har"）
+│   ├── ohosTest/                      # 仪器化测试
+│   └── test/                          # 本地单元测试
+├── Index.ets                          # 库模块导出入口
+├── build-profile.json5                # 模块级构建配置
+├── oh-package.json5                   # 模块依赖声明
+├── hvigorfile.ts                      # Hvigor 构建脚本
+├── consumer-rules.txt                 # 混淆消费者规则
+└── obfuscation-rules.txt              # 混淆规则
+```
+
+## 关键配置
+
+| 配置项 | 值 |
+|--------|-----|
+| module name | `library` |
+| module type | `har` |
+| deviceTypes | `["phone"]` |
+| apiType | `stageMode` |
+
+## 使用场景
+
+- 创建一个可复用的 HAR 共享库
+- 封装通用组件、工具类或业务逻辑供多个模块引用
+- 通过 `oh-package.json5` 管理依赖，支持混淆配置
+
+## 使用方式
+
+此模板由 `createHmTemplate` 工具自动下载和解压，用于在现有 HarmonyOS 工程中添加新的 HAR 库模块。将模板内容复制到工程目录下并在 `build-profile.json5` 的 `modules` 中注册即可。

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@harmonyos-arkts/opencode-plugin",
-  "version": "0.0.6-beta",
+  "version": "0.0.7",
   "description": "HarmonyOS Full-Lifecycle Development Assistant. Specialized in the complete development lifecycle of HarmonyOS applications, including project creation, UI development, state management, network requests, data storage, permission requests, performance optimization, testing, and release.",
   "type": "module",
   "license": "MIT",
@@ -48,4 +48,4 @@
   "engines": {
     "node": ">=18.0.0"
   }
-}
+}