@aigne/doc-smith 0.8.11-beta.5 → 0.8.11-beta.6

package/docs/getting-started.zh-TW.md

@@ -1,17 +1,17 @@
 # 入門指南
 
-本指南將逐步引導您安裝 AIGNE DocSmith、設定專案，並從您的原始碼產生一套完整的說明文件。
+本指南將逐步引導您安裝 AIGNE DocSmith、設定專案，並從您的原始碼產生一套完整的文件。
 
 ## 步驟 1：先決條件
 
-在開始之前，請確保您的系統上已安裝 Node.js 及其套件管理器 npm。DocSmith 是一個在 Node.js 環境中執行的命令列工具。
+在開始之前，請確保您的系統上已安裝 Node.js 及其套件管理器 npm。DocSmith 是一個在 Node.js 環境中運行的命令列工具。
 
 ### 安裝 Node.js
 
 以下是在各種作業系統上安裝 Node.js 的簡要說明。
 
 **Windows**
-1.  從 [Node.js 官方網站](https://nodejs.org/) 下載安裝程式。
+1.  從官方 [Node.js 網站](https://nodejs.org/) 下載安裝程式。
 2.  執行 `.msi` 安裝程式並依照安裝精靈的步驟進行。
 
 **macOS**
@@ -38,7 +38,7 @@ curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
 sudo apt-get install -y nodejs
 ```
 
-對於基於 CentOS/RHEL/Fedora 的系統：
+對於 CentOS/RHEL/Fedora 系統：
 
 ```bash Terminal icon=lucide:laptop
 curl -fsSL https://rpm.nodesource.com/setup_lts.x | sudo bash -
@@ -62,7 +62,7 @@ DocSmith 工具包含在 AIGNE 命令列介面 (CLI) 中。請使用 npm 全域
 npm i -g @aigne/cli
 ```
 
-安裝完成後，請執行說明文件的說明指令來驗證：
+安裝完成後，請執行文件工具的說明指令來進行驗證：
 
 ```bash Terminal
 aigne doc -h
@@ -70,7 +70,7 @@ aigne doc -h
 
 此指令將顯示 DocSmith 的說明選單，確認其已準備就緒可供使用。
 
-## 步驟 3：產生您的說明文件
+## 步驟 3：產生您的文件
 
 安裝 CLI 後，您只需一個指令即可產生文件。請在終端機中導覽至您專案的根目錄並執行：
 
@@ -80,15 +80,15 @@ aigne doc generate
 
 ### 自動設定
 
-當您首次在專案中執行此指令時，DocSmith 會偵測到尚無設定，並自動啟動一個互動式設定精靈。
+當您首次在專案中執行此指令時，DocSmith 會偵測到尚無設定檔，並自動啟動互動式設定精靈。
 
 ![執行 generate 指令會啟動設定精靈](https://docsmith.aigne.io/image-bin/uploads/0c45a32667c5250e54194a61d9495965.png)
 
-系統將會提示您一系列問題，以定義說明文件的特性，包括：
+系統將會提示您回答一系列問題，以定義文件的特性，包括：
 
 - 主要目的與風格。
 - 預期的目標讀者。
-- 主要語言及任何用於翻譯的其他語言。
+- 主要語言以及任何用於翻譯的其他語言。
 - 供 AI 分析的原始碼路徑。
 - 產生文件的輸出目錄。
 
@@ -98,24 +98,24 @@ aigne doc generate
 
 ![DocSmith 正在規劃結構並產生文件](https://docsmith.aigne.io/image-bin/uploads/d0766c19380a02eb8a6f8ce86a838849.png)
 
-## 步驟 4：檢閱您的輸出
+## 步驟 4：檢視您的產出
 
 產生過程結束後，您的終端機中將會顯示一則確認訊息。
 
-![成功產生說明文件的訊息](https://docsmith.aigne.io/image-bin/uploads/0967443611408ad9d0042793d590b8fd.png)
+![文件成功產生的訊息](https://docsmith.aigne.io/image-bin/uploads/0967443611408ad9d0042793d590b8fd.png)
 
-您新的說明文件現在位於您在設定過程中指定的輸出目錄中。預設位置是 `.aigne/doc-smith/docs`。
+您的新文件現在位於您在設定過程中指定的輸出目錄中。預設位置為 `.aigne/doc-smith/docs`。
 
-## 接下來呢？
+## 下一步是什麼？
 
-現在您已經產生了第一份文件，可以探索其他功能：
+既然您已產生了第一份文件，您可以探索其他功能：
 
 <x-cards>
   <x-card data-title="核心功能" data-icon="lucide:box" data-href="/features">
-    探索主要指令與功能，從更新文件到線上發布。
+    探索主要指令與功能，從更新文件到線上發佈。
   </x-card>
   <x-card data-title="設定指南" data-icon="lucide:settings" data-href="/configuration">
-    了解如何透過編輯 config.yaml 檔案來微調您文件的風格、目標讀者和語言。
+    了解如何透過編輯 config.yaml 檔案來微調文件的風格、目標讀者和語言。
   </x-card>
   <x-card data-title="CLI 指令參考" data-icon="lucide:terminal" data-href="/cli-reference">
     取得所有可用的 `aigne doc` 指令及其選項的完整參考。

package/docs/getting-started.zh.md

@@ -1,25 +1,25 @@
-# 入门指南
+# 快速入门
 
-本指南提供了一个分步演练，指导您安装 AIGNE DocSmith、配置项目，并从源代码生成一套完整的文档。
+本指南将引导您逐步安装 AIGNE DocSmith、配置项目，并从您的源代码生成一套完整的文档。
 
-## 第 1 步：准备工作
+## 第 1 步：先决条件
 
-在开始之前，请确保您的系统上已安装 Node.js 及其包管理器 npm。DocSmith 是一个在 Node.js 环境中运行的命令行工具。
+在开始之前，请确保您的系统上已安装 Node.js 及其包管理器 npm。DocSmith 是一个在 Node.js 环境下运行的命令行工具。
 
 ### 安装 Node.js
 
 以下是在各种操作系统上安装 Node.js 的简要说明。
 
 **Windows**
-1.  从官方 [Node.js 网站](https://nodejs.org/) 下载安装程序。
+1.  从 [Node.js 官方网站](https://nodejs.org/) 下载安装程序。
 2.  运行 `.msi` 安装程序，并按照安装向导中的步骤操作。
 
 **macOS**
 
 推荐的方法是使用 [Homebrew](https://brew.sh/)：
 
-```bash Terminal icon=lucide:apple
-# 如果您没有安装 Homebrew，请先安装
+```bash 终端 icon=lucide:apple
+# 如果您还没有安装 Homebrew，请先安装
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
 
 # 安装 Node.js
@@ -32,7 +32,7 @@ brew install node
 
 对于基于 Ubuntu/Debian 的系统：
 
-```bash Terminal icon=lucide:laptop
+```bash 终端 icon=lucide:laptop
 sudo apt update
 curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
 sudo apt-get install -y nodejs
@@ -40,47 +40,47 @@ sudo apt-get install -y nodejs
 
 对于基于 CentOS/RHEL/Fedora 的系统：
 
-```bash Terminal icon=lucide:laptop
+```bash 终端 icon=lucide:laptop
 curl -fsSL https://rpm.nodesource.com/setup_lts.x | sudo bash -
 sudo yum install nodejs
 ```
 
 ### 验证
 
-安装完成后，通过在终端中运行以下命令来验证 Node.js 和 npm 是否可用：
+安装完成后，在终端中运行以下命令，验证 Node.js 和 npm 是否可用：
 
-```bash Terminal
+```bash 终端
 node --version
 npm --version
 ```
 
 ## 第 2 步：安装 AIGNE CLI
 
-DocSmith 工具包含在 AIGNE 命令行界面（CLI）中。使用 npm 全局安装最新版本的 AIGNE CLI：
+DocSmith 工具包含在 AIGNE 命令行界面 (CLI) 中。使用 npm 全局安装最新版本的 AIGNE CLI：
 
-```bash Terminal icon=logos:npm
+```bash 终端 icon=logos:npm
 npm i -g @aigne/cli
 ```
 
-安装完成后，通过运行文档工具的帮助命令来验证安装：
+安装完成后，运行文档工具的帮助命令进行验证：
 
-```bash Terminal
+```bash 终端
 aigne doc -h
 ```
 
-此命令将显示 DocSmith 的帮助菜单，确认其已准备就绪。
+该命令将显示 DocSmith 的帮助菜单，确认其已准备就绪。
 
-## 第 3 步：生成您的文档
+## 第 3 步：生成文档
 
-安装 CLI 后，您可以使用单个命令生成文档。在终端中导航到您项目的根目录并运行：
+安装 CLI 后，您只需一个命令即可生成文档。在终端中导航到您项目的根目录并运行：
 
-```bash Terminal icon=lucide:sparkles
+```bash 终端 icon=lucide:sparkles
 aigne doc generate
 ```
 
 ### 自动配置
 
-当您首次在项目中运行此命令时，DocSmith 会检测到不存在任何配置，并自动启动一个交互式设置向导。
+当您在项目中首次运行此命令时，DocSmith 会检测到尚无配置，并自动启动一个交互式设置向导。
 
 ![运行 generate 命令会启动设置向导](https://docsmith.aigne.io/image-bin/uploads/0c45a32667c5250e54194a61d9495965.png)
 
@@ -88,23 +88,23 @@ aigne doc generate
 
 - 主要目的和风格。
 - 目标受众。
-- 主要语言以及用于翻译的其他语言。
+- 主要语言及其他需要翻译的语言。
 - 供 AI 分析的源代码路径。
 - 生成文档的输出目录。
 
 ![回答提示以完成项目设置](https://docsmith.aigne.io/image-bin/uploads/fbedbfa256036ad6375a6c18047a75ad.png)
 
-配置完成后，DocSmith 将继续分析您的源代码、规划文档结构并生成内容。
+配置完成后，DocSmith 将开始分析您的源代码，规划文档结构，并生成内容。
 
 ![DocSmith 正在规划结构并生成文档](https://docsmith.aigne.io/image-bin/uploads/d0766c19380a02eb8a6f8ce86a838849.png)
 
-## 第 4 步：检查您的输出
+## 第 4 步：查看您的输出
 
-生成过程结束后，您的终端中将显示一条确认消息。
+生成过程结束后，您的终端将显示一条确认消息。
 
-![文档生成成功的消息](https://docsmith.aigne.io/image-bin/uploads/0967443611408ad9d0042793d590b8fd.png)
+![文档生成成功消息](https://docsmith.aigne.io/image-bin/uploads/0967443611408ad9d0042793d590b8fd.png)
 
-您的新文档现在位于您在设置过程中指定的输出目录中。默认位置是 `.aigne/doc-smith/docs`。
+您的新文档现已位于您在设置过程中指定的输出目录中。默认位置是 `.aigne/doc-smith/docs`。
 
 ## 接下来做什么？
 
@@ -112,10 +112,10 @@ aigne doc generate
 
 <x-cards>
   <x-card data-title="核心功能" data-icon="lucide:box" data-href="/features">
-    探索主要命令和功能，从更新文档到在线发布。
+    探索从更新文档到在线发布的主要命令和功能。
   </x-card>
   <x-card data-title="配置指南" data-icon="lucide:settings" data-href="/configuration">
-    学习如何通过编辑 config.yaml 文件来微调文档的风格、受众和语言。
+    了解如何通过编辑 config.yaml 文件来微调文档的风格、受众和语言。
   </x-card>
   <x-card data-title="CLI 命令参考" data-icon="lucide:terminal" data-href="/cli-reference">
     获取所有可用的 `aigne doc` 命令及其选项的完整参考。

package/docs/overview.md

@@ -14,11 +14,11 @@ The following diagram illustrates how DocSmith fits within the AIGNE architectur
 
 DocSmith provides a set of features to automate and simplify the documentation process:
 
-*   **Structure Planning:** Analyzes a codebase to generate a logical document structure.
-*   **Content Generation:** Populates the planned document structure with content generated from the source code.
+*   **Structure Planning:** Analyzes a codebase to generate a logical documentation structure.
+*   **Content Generation:** Populates the planned documentation structure with content generated from the source code.
 *   **Multi-Language Support:** Translates documentation into 12 languages, including English, Chinese, Japanese, and Spanish.
 *   **AIGNE Hub Integration:** Uses [AIGNE Hub](https://www.aigne.io/en/hub) as an LLM provider, allowing model switching without managing individual API keys.
-*   **Document Publishing:** Publishes documentation to the official platform at [docsmith.aigne.io](https://docsmith.aigne.io/app/) or to a user's own [Discuss Kit](https://www.arcblock.io/docs/web3-kit/en/discuss-kit) instance.
+*   **One-Click Publishing:** Makes your documentation live with shareable links for your team or users. Publish to the official platform at [docsmith.aigne.io](https://docsmith.aigne.io/app/) or to your own [Discuss Kit](https://www.arcblock.io/docs/web3-kit/en/discuss-kit) instance.
 *   **Iterative Updates:** Detects source code changes to update documentation and supports targeted regeneration of specific documents based on user feedback.
 
 ## Next Steps

package/docs-mcp/analyze-docs-relevance.yaml

@@ -1,7 +1,7 @@
 name: analyze-docs-relevance
-description: Analyze which documents in the document structure are relevant to the user query
+description: Analyze which documents in the documentation structure are relevant to the user query
 instructions: |
-  You are an AI assistant that analyzes the relevance between a user query and documents in a document structure.
+  You are an AI assistant that analyzes the relevance between a user query and documents in a documentation structure.
 
   <document_structure>
   {{ originalDocumentStructure }}
@@ -11,9 +11,9 @@ instructions: |
   {{ query }}
   </user-query>
 
-  Given a user query and a document structure containing multiple documents, your task is to:
+  Given a user query and a documentation structure containing multiple documents, your task is to:
   1. Understand the user's search intent from the query
-  2. Analyze each document in the document structure to determine relevance
+  2. Analyze each document in the documentation structure to determine relevance
   3. Return a list of relevant documents with their paths, titles, and descriptions
 
   Consider the following factors for relevance:
@@ -44,7 +44,7 @@ input_schema:
             type: string
           description:
             type: string
-      description: Document structure containing all available documents
+      description: Documentation Structure containing all available documents
 output_schema:
   type: object
   properties:
@@ -52,7 +52,7 @@ output_schema:
       type: array
       items:
         type: string
-        description: Must be selected from paths in the document structure, cannot be other paths
+        description: Must be selected from paths in the documentation structure, cannot be other paths
       description: List of relevant documents
     reasoning:
       type: string

package/docs-mcp/docs-search.yaml

@@ -38,5 +38,5 @@ output_schema:
             type: string
           description:
             type: string
-      description: List of relevant documents from document structure
+      description: List of relevant documents from documentation structure
 mode: sequential

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aigne/doc-smith",
-  "version": "0.8.11-beta.5",
+  "version": "0.8.11-beta.6",
   "description": "AI-driven documentation generation tool built on the AIGNE Framework",
   "publishConfig": {
     "access": "public"
@@ -14,7 +14,7 @@
   "dependencies": {
     "@aigne/aigne-hub": "^0.10.0",
     "@aigne/anthropic": "^0.14.0",
-    "@aigne/cli": "^1.49.0",
+    "@aigne/cli": "^1.49.1",
     "@aigne/core": "^1.61.0",
     "@aigne/gemini": "^0.14.0",
     "@aigne/openai": "^0.16.0",

package/prompts/common/document-structure/conflict-resolution-guidance.md

@@ -1,8 +1,8 @@
 <conflict_resolution_guidance>
-When users select potentially conflicting options, conflict resolution guidance will be provided in user_rules. Please carefully read these guidelines and implement the corresponding resolution strategies in the document structure.
+When users select potentially conflicting options, conflict resolution guidance will be provided in user_rules. Please carefully read these guidelines and implement the corresponding resolution strategies in the documentation structure.
 
 Core principles for conflict resolution:
-1. **Layered need satisfaction**: Simultaneously satisfy multiple purposes and audiences through reasonable document structure hierarchy
+1. **Layered need satisfaction**: Simultaneously satisfy multiple purposes and audiences through reasonable documentation structure hierarchy
 2. **Clear navigation paths**: Provide clear document usage paths for users with different needs
 3. **Avoid content duplication**: Ensure content across different sections is complementary rather than repetitive
 4. **Progressive disclosure**: From high-level overview to specific details, meeting needs at different depth levels
@@ -12,5 +12,5 @@ Common conflict resolution patterns:
 - **Audience conflicts**: Design role-oriented sections or paths
 - **Depth conflicts**: Adopt progressive structures that allow users to choose appropriate depth levels
 
-When generating document structure, prioritize conflict resolution strategies to ensure the final structure can harmoniously satisfy all user needs.
+When generating documentation structure, prioritize conflict resolution strategies to ensure the final structure can harmoniously satisfy all user needs.
 </conflict_resolution_guidance>

package/prompts/common/document-structure/document-structure-rules.md

@@ -16,8 +16,8 @@ Structural planning rules:
 5. The order of {{nodeName}} in output should follow the target audience's browsing path. It doesn't need to follow the exact order in DataSources—progress from simple to advanced, from understanding to exploration, with reasonable pathways
 6. Each {{nodeName}} should have a clear content plan and must not duplicate content from other {{nodeName}} items
 7. Information planned for each {{nodeName}} should be clearly describable within a single page. If there's too much information to display or the concepts are too broad, consider splitting into sub-{{nodeName}} items
-8. If previous document structure and user feedback are provided, make only necessary modifications based on user feedback without major changes
-9. If previous document structure is provided but no feedback is given, **directly return the previous document structure**
+8. If previous documentation structure and user feedback are provided, make only necessary modifications based on user feedback without major changes
+9. If previous documentation structure is provided but no feedback is given, **directly return the previous documentation structure**
 10. If review feedback exists, it indicates your previous generation didn't meet requirements. Optimize your output based on the review feedback
 
 {{nodeName}} planning rules:

package/prompts/detail/document-rules.md

@@ -8,7 +8,7 @@ Documentation Generation Rules:
 - Include links to related documents in the introduction using Markdown format to help users navigate to relevant content
 - Add links to further reading materials in the summary section using Markdown format
 - Use proper Markdown link syntax, for example: [Next Chapter Title](next_chapter_path)
-- **Ensure next_chapter_path references either external URLs or valid paths from the structure plan**—use absolute paths from the structure plan
+- **Ensure next_chapter_path references either external URLs or valid paths from the documentation structure**—use absolute paths from the documentation structure
 - When DataSources includes third-party links, incorporate them appropriately throughout the document
 - Structure each section with: title, introduction, code examples, response data samples, and explanatory notes. Place explanations directly after code examples without separate "Example Description" subheadings
 - Maintain content completeness and logical flow so users can follow the documentation seamlessly

package/prompts/detail/generate-document.md

@@ -40,7 +40,7 @@ Custom code block generation rules:
 Diagram generate guide:
 Evaluate for each document whether diagrams are necessary.
 - Use diagrams to clarify complex concepts and diversify the presentation of the page.
-- The document overview page must include an architecture diagram that illustrates the entire document structure.
+- The document overview page must include an architecture diagram that illustrates the entire documentation structure.
 - For the first page of each section, include a structural diagram of the current module when it adds clarity.
 - For individual article pages, consider detailed flowcharts when the content or overall architecture warrants them.
 - The number of diagrams is flexible, but aim for 0-3 diagrams as a practical range.

package/prompts/evaluate/document-structure.md

@@ -1,16 +1,16 @@
 <role_and_goal>
 
-You are a professional **documentation structure architect** responsible for conducting **high-standard quality** reviews of AI-generated document structure.
-Your task is to rigorously evaluate the **completeness and adaptability** of document structure based on the user's selected **document purpose, target audiences, and desired coverage depth**.
+You are a professional **documentation structure architect** responsible for conducting **high-standard quality** reviews of AI-generated documentation structure.
+Your task is to rigorously evaluate the **completeness and adaptability** of documentation structure based on the user's selected **document purpose, target audiences, and desired coverage depth**.
 You must **precisely map** the correspondence between each module in the structure and user requirements, and provide **compelling reasons** to support scoring in each dimension, ensuring that evaluation results can **effectively guide structure optimization**.
 
 </role_and_goal>
 
 <context>
 
-**document structure to be evaluated (documentStructure)**:
+**documentation structure to be evaluated (documentStructure)**:
 
-- **Document Structure**
+- **Documentation Structure**
   {{ documentStructureYaml }}
 
 - **User selections**
@@ -22,7 +22,7 @@ You must **precisely map** the correspondence between each module in the structu
     {{ coverageDepth }}
 
 - **Notes**
-  - The document structure can satisfy multiple purposes or multiple audiences through **different document modules**; a single document is not required to be compatible with all.
+  - The documentation structure can satisfy multiple purposes or multiple audiences through **different document modules**; a single document is not required to be compatible with all.
   - If priorities are provided, missing high-priority items is more serious than missing secondary items.
 
 </context>
@@ -66,7 +66,7 @@ Apply these levels to the following key points. Create a separate detail entry f
 
 Strictly follow these steps:
 1. **Mapping Coverage**
-   - Determine which modules in the document structure correspond to each purpose and audience (list correspondences).
+   - Determine which modules in the documentation structure correspond to each purpose and audience (list correspondences).
    - Note uncovered purposes/audiences (especially high-priority ones) and any depth or hygiene issues tied to specific modules.
 
 2. **Assign Levels**

package/prompts/structure/check-document-structure.md

@@ -1,8 +1,8 @@
 <role_and_goal>
-You are a meticulous AI Agent responsible for quality control. Your task is to compare new document structures with previous versions based on specific user feedback. You must act as a strict gatekeeper, ensuring that only intended and explicitly requested changes occur.
+You are a meticulous AI Agent responsible for quality control. Your task is to compare new documentation structures with previous versions based on specific user feedback. You must act as a strict gatekeeper, ensuring that only intended and explicitly requested changes occur.
 
 Your primary objective is to validate three critical rules:
-1.  **Feedback Implementation**: The new document structure **must** correctly implement all changes requested in the user feedback.
+1.  **Feedback Implementation**: The new documentation structure **must** correctly implement all changes requested in the user feedback.
 2.  **Unrelated Node Stability**: Nodes not mentioned in user feedback **must not have their path or sourcesIds attributes modified**
   - `path` and `sourcesIds` are critical identifiers linking existing content, and their stability is paramount.
   - For scenarios where users request adding new nodes, the new nodes may affect the order of existing nodes, which is acceptable.
@@ -10,7 +10,7 @@ Your primary objective is to validate three critical rules:
 </role_and_goal>
 
 <context>
-- **Original document structure (originalDocumentStructure)**:
+- **Original documentation structure (originalDocumentStructure)**:
 <original_document_structure>
 {{ originalDocumentStructure }}
 </original_document_structure>
@@ -22,14 +22,14 @@ Your primary objective is to validate three critical rules:
 ```
 {% endif %}
 
-- **Newly generated document structure (documentStructure)**:
+- **Newly generated documentation structure (documentStructure)**:
 <document_structure>
 {{ documentStructure }}
 </document_structure>
 </context>
 
 <quality_control_rules>
-### Scenario 1: Initial Run (No Original document Structure)
+### Scenario 1: Initial Run (No Original Documentation Structure)
 If `original_document_structure` is null, empty, or not provided, this indicates the first structure generation. There is no baseline for comparison.
 Your validation automatically passes.
 
@@ -52,7 +52,7 @@ Your output must be a valid JSON object containing `isValid` and `reason`, retur
     ```json
     {
       "isValid": true,
-      "reason": "The new document structure correctly implements user feedback while maintaining stability of all unrelated nodes."
+      "reason": "The new documentation structure correctly implements user feedback while maintaining stability of all unrelated nodes."
     }
     ```
 
@@ -61,7 +61,7 @@ Your output must be a valid JSON object containing `isValid` and `reason`, retur
     ```json
     {
       "isValid": false,
-      "reason": "The new document structure fails to correctly implement user feedback. [Please provide specific details, e.g.: 'Feedback requested renaming 'Introduction' to 'Overview', but this change was not executed.']"
+      "reason": "The new documentation structure fails to correctly implement user feedback. [Please provide specific details, e.g.: 'Feedback requested renaming 'Introduction' to 'Overview', but this change was not executed.']"
     }
     ```
 
@@ -70,7 +70,7 @@ Your output must be a valid JSON object containing `isValid` and `reason`, retur
     ```json
     {
       "isValid": false,
-      "reason": "The new document structure modified unrelated nodes, which is not allowed. [Please provide specific details, e.g.: 'The path of node 'API Reference' was changed from '/api' to '/reference/api' without any feedback requesting this change. This is a critical error.']"
+      "reason": "The new documentation structure modified unrelated nodes, which is not allowed. [Please provide specific details, e.g.: 'The path of node 'API Reference' was changed from '/api' to '/reference/api' without any feedback requesting this change. This is a critical error.']"
     }
     ```
 
@@ -78,7 +78,7 @@ Your output must be a valid JSON object containing `isValid` and `reason`, retur
     ```json
     {
       "isValid": false,
-      "reason": "The document structure contains nodes without associated data sources. Each node must have at least one source file linked through sourcesIds."
+      "reason": "The documentation structure contains nodes without associated data sources. Each node must have at least one source file linked through sourcesIds."
     }
     ```
 
@@ -87,7 +87,7 @@ Your output must be a valid JSON object containing `isValid` and `reason`, retur
     ```json
     {
       "isValid": true,
-      "reason": "Initial document structure generation with no previous version for comparison."
+      "reason": "Initial documentation structure generation with no previous version for comparison."
     }
     ```
 </output_constraints>

package/prompts/structure/document-rules.md

@@ -1,6 +1,6 @@
-Document structure planning rules:
+Documentation structure rules:
 
-- Generate a comprehensive document structure that encompasses all features in the source code and includes code examples.
+- Generate a comprehensive documentation structure that encompasses all features in the source code and includes code examples.
 - Plan the structure based on the provided source code, ensuring each planned node has enough information to be displayed.
 - Group related content in the same section to avoid scattering it across multiple sections and duplicating content.
 - Keep the structure concise, avoiding splitting the same functionality into multiple parts. If content is too complex to present together without hurting readability, create sub-levels.

package/prompts/structure/generate-structure-system.md

@@ -9,13 +9,13 @@ Key capabilities and behavioral principles:
   - Structured Thinking: Strong logical analysis capabilities to decompose complex information into clear chapters, sections, and items, establishing reasonable hierarchical relationships.
   - User-Oriented Approach: Ability to flexibly adjust the focus and level of detail in structural planning based on document objectives and audience characteristics provided by users.
   - Modular Design: Tendency to divide documents into independent, reusable modules or sections for easy content population and subsequent maintenance.
-  - Flexibility and Adaptability: Ability to handle multiple types of data sources and design the most suitable document structure based on data source characteristics (such as code function/class structures, API endpoints/parameters, text paragraphs/themes).
+  - Flexibility and Adaptability: Ability to handle multiple types of data sources and design the most suitable documentation structure based on data source characteristics (such as code function/class structures, API endpoints/parameters, text paragraphs/themes).
   - Clarity and Completeness: Ensure the final structural plan is easy to understand and can guide the LLM to generate a comprehensive and well-organized document.
 
 
 Objectives:
-  - This structural plan should be reasonable and clear, capable of comprehensively displaying information from the user-provided context while providing users with logical browsing paths.
-  - Each {{nodeName}} should include: {{nodeName}} title, a one-sentence introduction to the main information this {{nodeName}} displays, with information presentation and organization methods matching the target audience.
+  - Create a clear and logical structural plan that comprehensively presents information from the user-provided context while providing users with intuitive navigation paths.
+  - Each {{nodeName}} should include: a {{nodeName}} title, a one-sentence introduction describing its main content, with presentation and organization methods tailored to the target audience.
 
 {% include "../common/document-structure/intj-traits.md" %}
 

package/prompts/structure/structure-example.md

@@ -1,5 +1,5 @@
 <document_structure_examples>
-Below are some high-quality document structure examples for your reference:
+Below are some high-quality documentation structure examples for your reference:
 
 Example A: Open Source Frontend Framework Docs
 ```yaml

package/prompts/structure/structure-getting-started.md

@@ -1,5 +1,5 @@
 <getting_started_document_structure_rules>
-Based on the provided data sources, plan a Getting Started document structure:
+Based on the provided data sources, plan a Getting Started documentation structure:
   - The entire structure should be complete and continuous, allowing users to follow the documentation step by step to complete a working example
   - Each document section should complete a relatively complete step, avoiding overly long individual sections that create reading pressure for users
   - Provide reference command lines and code as needed to facilitate users following the documentation

package/prompts/structure/update-document-structure.md

@@ -1,7 +1,7 @@
 <role_and_goal>
 
-You are a document structure update specialist with the strategic mindset of an **INTJ** (The Architect).
-You analyze user feedback and intentions to modify existing document structures using specific operations.
+You are a documentation structure update specialist with the strategic mindset of an **INTJ** (The Architect).
+You analyze user feedback and intentions to modify existing documentation structures using specific operations.
 Your task is to understand user requirements and execute the appropriate structure modifications efficiently and accurately.
 
 {% include "../common/document-structure/intj-traits.md" %}
@@ -12,15 +12,15 @@ Processing workflow:
 - Analyze user feedback to understand the specific intent (add, delete, update, or move sections)
 - Determine which tools to use based on the user's requirements
 - Execute the appropriate operations using available tools
-- Ensure all modifications maintain document structure integrity
+- Ensure all modifications maintain documentation structure integrity
 
 Rules:
-** Never generate new document structures directly. All changes must be made using Tools. **
-** Use the document structure returned by Tools as the latest version, check if it satisfies the user's feedback, and if so, return the latest version directly. **
+** Never generate new documentation structures directly. All changes must be made using Tools. **
+** Use the documentation structure returned by Tools as the latest version, check if it satisfies the user's feedback, and if so, return the latest version directly. **
 
 Objectives:
-  - This structural plan should be reasonable and clear, capable of comprehensively displaying information from the user-provided context while providing users with logical browsing paths.
-  - Each {{nodeName}} should include: {{nodeName}} title, a one-sentence introduction to the main information this {{nodeName}} displays, with information presentation and organization methods matching the target audience.
+  - Create a clear and logical structural plan that comprehensively presents information from the user-provided context while providing users with intuitive navigation paths.
+  - Each {{nodeName}} should include: a {{nodeName}} title, a one-sentence introduction describing its main content, with presentation and organization methods tailored to the target audience.
 
 </role_and_goal>
 
@@ -28,7 +28,7 @@ Objectives:
 
 {% include "../common/document-structure/user-preferences.md" %}
 
-Initial Document Structure:
+Initial Documentation Structure:
 <initial_document_structure>
 {{documentStructure}}
 </initial_document_structure>
@@ -87,7 +87,7 @@ Operation execution rules:
 - **Use only the appropriate tools** based on the determined operation type
 - **Validate all required parameters** before calling tools
 - **Maintain data integrity** by ensuring all constraints are met
-- **Only use Tools to update data** Use provided Tools to modify document structure, use the document structure returned by Tools as the latest version
+- **Only use Tools to update data** Use provided Tools to modify documentation structure, use the documentation structure returned by Tools as the latest version
 - **Use Tool return results** When all Tool calls are complete, directly use the result from the last Tool
 
 Tool usage guidelines:

package/prompts/utils/feedback-refiner.md

@@ -33,7 +33,7 @@ Save determination rules:
 **One-time operations (do not save)**:
 - Only corrects current version/typos/individual phrasing/local factual errors with no stable reusable value → `save=false`
 - Fixes that are highly specific to a single line or data point and unlikely to recur (e.g., "change the year from 2020 to 2021") → `save=false`
-- Document structure adjustments, adding new documents, and moving document positions are always one-time operations → `save=false`
+- Documentation Structure adjustments, adding new documents, and moving document positions are always one-time operations → `save=false`
 
 **Reusable policies (save)**:
 - Writing styles, structural conventions, inclusion/exclusion items, translation conventions that are broadly applicable and should be consistently executed in the future → `save=true`

package/tests/agents/clear/choose-contents.test.mjs

@@ -15,7 +15,7 @@ describe("choose-contents", () => {
         path: "/test/docs",
       })),
       clearDocumentStructure: mock(async () => ({
-        message: "Document structure cleared",
+        message: "Documentation Structure cleared",
         cleared: true,
         path: "/test/structure.json",
       })),