universal-dev-standards 4.1.0 → 5.0.0-beta.10

package/src/utils/integration-generator.js

@@ -2,50 +2,33 @@ import { existsSync, readFileSync, writeFileSync, mkdirSync } from 'fs';
 import { dirname, join, basename } from 'path';
 import { getLanguageRules } from '../prompts/integrations.js';
 import { computeIntegrationBlockHash } from './hasher.js';
+import { UDS_MARKERS, SUPPORTED_AI_TOOLS, LEGACY_TOOL_MAPPINGS } from '../core/constants.js';
 
 /**
- * Marker block constants for different file formats
+ * Helper functions for tool configuration
  */
-const MARKERS = {
-  markdown: {
-    start: '<!-- UDS:STANDARDS:START -->',
-    end: '<!-- UDS:STANDARDS:END -->'
-  },
-  plaintext: {
-    start: '# === UDS:STANDARDS:START ===',
-    end: '# === UDS:STANDARDS:END ==='
-  }
-};
 
 /**
- * Tool file mappings - maps tool names to their integration file paths
+ * Get tool file name with legacy mapping support
+ * @param {string} tool - Tool name
+ * @returns {string} File name
  */
-const TOOL_FILES = {
-  cursor: '.cursorrules',
-  windsurf: '.windsurfrules',
-  cline: '.clinerules',
-  copilot: '.github/copilot-instructions.md',
-  antigravity: 'INSTRUCTIONS.md',
-  'claude-code': 'CLAUDE.md',
-  codex: 'AGENTS.md',
-  'gemini-cli': 'GEMINI.md',
-  opencode: 'AGENTS.md'  // Shares file with codex
-};
+function getToolFileName(tool) {
+  const normalizedName = LEGACY_TOOL_MAPPINGS[tool] || tool;
+  const config = SUPPORTED_AI_TOOLS[normalizedName];
+  return config ? config.file : `${tool}.md`;
+}
 
 /**
- * Tool format mappings - determines if tool uses markdown or plaintext format
+ * Get tool format with legacy mapping support
+ * @param {string} tool - Tool name
+ * @returns {string} Format ('markdown' or 'plaintext')
  */
-const TOOL_FORMATS = {
-  cursor: 'plaintext',
-  windsurf: 'plaintext',
-  cline: 'plaintext',
-  copilot: 'markdown',
-  antigravity: 'markdown',
-  'claude-code': 'markdown',
-  codex: 'markdown',
-  'gemini-cli': 'markdown',
-  opencode: 'markdown'
-};
+function getToolFormat(tool) {
+  const normalizedName = LEGACY_TOOL_MAPPINGS[tool] || tool;
+  const config = SUPPORTED_AI_TOOLS[normalizedName];
+  return config ? config.format : 'markdown';
+}
 
 /**
  * Mapping from standard filename to task description
@@ -62,7 +45,9 @@ const STANDARD_TASK_MAPPING = {
   'code-review-checklist.md': { task: 'Code review', when: 'During PR review', priority: 'SHOULD' },
   'spec-driven-development.md': { task: 'Feature development', when: 'When SDD tool present', priority: 'SHOULD' },
   'test-completeness-dimensions.md': { task: 'Test coverage', when: 'When evaluating tests', priority: 'SHOULD' },
-  'git-workflow.ai.yaml': { task: 'Git workflow', when: 'Branch/merge decisions', priority: 'SHOULD' }
+  'git-workflow.ai.yaml': { task: 'Git workflow', when: 'Branch/merge decisions', priority: 'SHOULD' },
+  'developer-memory.ai.yaml': { task: 'Developer memory', when: 'Always (protocol)', priority: 'SHOULD' },
+  'project-context-memory.ai.yaml': { task: 'Project context', when: 'Planning & Coding', priority: 'MUST' }
 };
 
 /**
@@ -81,6 +66,8 @@ const STANDARD_DESCRIPTIONS = {
   'spec-driven-development.md': '規格驅動開發',
   'test-completeness-dimensions.md': '測試完整性維度',
   'git-workflow.ai.yaml': 'Git 工作流程',
+  'developer-memory.ai.yaml': '開發者持久記憶',
+  'project-context-memory.ai.yaml': '專案情境記憶',
   'zh-tw.md': '繁體中文本地化'
 };
 
@@ -133,12 +120,29 @@ const COMMIT_TYPE_TEMPLATES = {
     ],
     format: '<type>(<scope>): <English subject>. <Chinese subject>.',
     formatNote: 'English types for tool compatibility, bilingual subjects for clarity'
+  },
+
+  // Bilingual with Simplified Chinese (used when displayLanguage is zh-cn)
+  'bilingual-zhcn': {
+    types: [
+      { type: 'feat', description_en: 'New feature', description_zh: '新功能', example: 'feat(auth): Add login form. 新增登录表单.' },
+      { type: 'fix', description_en: 'Bug fix', description_zh: '错误修正', example: 'fix(api): Fix null pointer. 修正空指针.' },
+      { type: 'docs', description_en: 'Documentation', description_zh: '文档更新', example: 'docs(readme): Update guide. 更新指南.' },
+      { type: 'style', description_en: 'Formatting', description_zh: '格式调整', example: 'style(lint): Fix indent. 修正缩排.' },
+      { type: 'refactor', description_en: 'Code restructure', description_zh: '代码重构', example: 'refactor(user): Extract logic. 抽取逻辑.' },
+      { type: 'test', description_en: 'Tests', description_zh: '测试相关', example: 'test(cart): Add tests. 新增测试.' },
+      { type: 'chore', description_en: 'Maintenance', description_zh: '维护任务', example: 'chore(deps): Update deps. 更新套件.' },
+      { type: 'perf', description_en: 'Performance', description_zh: '性能改善', example: 'perf(query): Optimize DB. 优化数据库.' },
+      { type: 'ci', description_en: 'CI/CD changes', description_zh: '持续集成', example: 'ci(github): Add deploy. 新增部署.' }
+    ],
+    format: '<type>(<scope>): <English subject>. <Chinese subject>.',
+    formatNote: 'English types for tool compatibility, bilingual subjects for clarity'
   }
 };
 
 /**
  * Generate commit types table based on commit_language
- * @param {string} commitLanguage - The commit language: 'english', 'traditional-chinese', or 'bilingual'
+ * @param {string} commitLanguage - The commit language: 'english', 'traditional-chinese', 'bilingual', or 'bilingual-zhcn'
  * @param {string} format - Output format: 'markdown' or 'plaintext'
  * @returns {string} Formatted commit types section
  */
@@ -159,6 +163,13 @@ function generateCommitTypesTable(commitLanguage, format = 'markdown') {
       for (const t of template.types) {
         lines.push(`| \`${t.type}\` | ${t.description_en} | ${t.description_zh} | ${t.example} |`);
       }
+    } else if (commitLanguage === 'bilingual-zhcn') {
+      // Simplified Chinese bilingual - header uses Simplified Chinese
+      lines.push('| Type | EN Description | 中文说明 | Example |');
+      lines.push('|------|----------------|----------|---------|');
+      for (const t of template.types) {
+        lines.push(`| \`${t.type}\` | ${t.description_en} | ${t.description_zh} | ${t.example} |`);
+      }
     } else {
       // English (default)
       lines.push('| Type | Description | Example |');
@@ -173,7 +184,7 @@ function generateCommitTypesTable(commitLanguage, format = 'markdown') {
       for (const t of template.types) {
         lines.push(`- ${t.type} (${t.english}): ${t.description}`);
       }
-    } else if (commitLanguage === 'bilingual') {
+    } else if (commitLanguage === 'bilingual' || commitLanguage === 'bilingual-zhcn') {
       for (const t of template.types) {
         lines.push(`- ${t.type}: ${t.description_en} / ${t.description_zh}`);
       }
@@ -207,6 +218,11 @@ function generateCommitStandardsContent(commitLanguage, detailLevel = 'standard'
 - Format: \`${template.format}\`
 - ${template.formatNote}
 - Keep subject under 72 characters | 主題保持在 72 字元內`;
+    } else if (commitLanguage === 'bilingual-zhcn') {
+      return `## Commit Standards | 提交标准
+- Format: \`${template.format}\`
+- ${template.formatNote}
+- Keep subject under 72 characters | 主题保持在 72 字符内`;
     } else {
       return `## Commit Standards
 - Format: \`${template.format}\`
@@ -260,6 +276,28 @@ ${typesTable}
 - Subject line: max 72 characters | 主題行: 最多 72 字元
 - Use imperative mood | 使用祈使語氣
 - Body: explain WHAT and WHY | 本文: 說明做了什麼及為什麼`;
+    } else if (commitLanguage === 'bilingual-zhcn') {
+      return `## Commit Message Standards | 提交消息标准
+Reference: .standards/commit-message-guide.md, .standards/options/bilingual.ai.yaml
+
+### Format | 格式
+\`\`\`
+${template.format}
+
+<English body>
+
+<Chinese body>
+
+<footer>
+\`\`\`
+
+### Types | 类型
+${typesTable}
+
+### Rules | 规则
+- Subject line: max 72 characters | 主题行: 最多 72 字符
+- Use imperative mood | 使用祈使语气
+- Body: explain WHAT and WHY | 本文: 说明做了什么及为什么`;
     } else {
       return `## Commit Message Standards
 Reference: .standards/commit-message-guide.md
@@ -353,6 +391,41 @@ ${typesTable}
 ### Footer Format | 頁腳格式
 - Breaking changes: \`BREAKING CHANGE: description\`
 - Issue references: \`Fixes #123\`, \`Closes #456\`
+- Co-authors: \`Co-authored-by: Name <email>\``;
+  } else if (commitLanguage === 'bilingual-zhcn') {
+    return `## Commit Message Standards | 提交消息标准
+Reference: .standards/commit-message-guide.md, .standards/options/bilingual.ai.yaml
+
+### Format Structure | 格式结构
+\`\`\`
+${template.format}
+
+<English body>
+
+<Chinese body / 中文本文>
+
+<footer>
+\`\`\`
+
+**Note**: ${template.formatNote}
+
+### Commit Types | 提交类型
+${typesTable}
+
+### Subject Line Rules | 主题行规则
+- Maximum 72 characters | 最多 72 字符
+- Use imperative mood | 使用祈使语气
+- No period at the end | 结尾不加句点
+- Include both EN and ZH subjects | 包含英文和中文主旨
+
+### Body Guidelines | 本文指引
+- Wrap at 72 characters | 每行 72 字符换行
+- Explain WHAT and WHY | 说明做了什么及为什么
+- Write English first, then Chinese | 先英文后中文
+
+### Footer Format | 页脚格式
+- Breaking changes: \`BREAKING CHANGE: description\`
+- Issue references: \`Fixes #123\`, \`Closes #456\`
 - Co-authors: \`Co-authored-by: Name <email>\``;
   } else {
     return `## Commit Message Standards
@@ -1820,7 +1893,12 @@ const TOOL_HEADERS = {
 You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# Cursor 規則
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -1828,7 +1906,12 @@ All responses should be in **English**.`,
 您是專業的軟體工程助手。請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# Cursor Rules | Cursor 規則
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -1839,7 +1922,15 @@ You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   windsurf: {
     en: `# Windsurf Rules
@@ -1849,7 +1940,12 @@ All responses should be in **Traditional Chinese (繁體中文)**, with technica
 You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# Windsurf 規則
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -1857,7 +1953,12 @@ All responses should be in **English**.`,
 您是專業的軟體工程助手。請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# Windsurf Rules | Windsurf 規則
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -1868,7 +1969,15 @@ You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   cline: {
     en: `# Cline Rules
@@ -1878,7 +1987,12 @@ All responses should be in **Traditional Chinese (繁體中文)**, with technica
 You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# Cline 規則
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -1886,7 +2000,12 @@ All responses should be in **English**.`,
 您是專業的軟體工程助手。請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# Cline Rules | Cline 規則
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -1897,7 +2016,15 @@ You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   copilot: {
     en: `# GitHub Copilot Instructions
@@ -1907,7 +2034,12 @@ All responses should be in **Traditional Chinese (繁體中文)**, with technica
 You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# GitHub Copilot 說明
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -1915,7 +2047,12 @@ All responses should be in **English**.`,
 您是專業的軟體工程助手。請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# GitHub Copilot Instructions | GitHub Copilot 說明
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -1926,7 +2063,15 @@ You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   antigravity: {
     en: `# Antigravity System Instructions
@@ -1937,7 +2082,12 @@ Recommended system instructions for Google Antigravity (Gemini Advanced Agent).
 Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# Antigravity 系統指令
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -1946,7 +2096,12 @@ Google Antigravity (Gemini Advanced Agent) 的推薦系統指令。
 請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# Antigravity System Instructions | Antigravity 系統指令
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -1957,7 +2112,15 @@ Google Antigravity (Gemini Advanced Agent) 的推薦系統指令。
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   'claude-code': {
     en: `# Project Guidelines for Claude Code
@@ -1965,14 +2128,24 @@ All responses should be in **Traditional Chinese (繁體中文)**, with technica
 # https://github.com/AsiaOstrich/universal-dev-standards
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# Claude Code 專案指南
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
 
 ## 對話語言 / Conversation Language
 所有回覆必須使用**繁體中文 (Traditional Chinese)**。
-AI 助手應以繁體中文回覆使用者的問題與請求。`,
+AI 助手應以繁體中文回覆使用者的問題與請求。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# Project Guidelines for Claude Code | Claude Code 專案指南
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -1981,7 +2154,15 @@ AI 助手應以繁體中文回覆使用者的問題與請求。`,
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
 所有回覆必須使用**繁體中文**，技術術語可保留英文。
-AI 助手應以繁體中文回覆使用者的問題與請求。`
+AI 助手應以繁體中文回覆使用者的問題與請求。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   codex: {
     en: `# AGENTS.md - OpenAI Codex CLI Rules
@@ -1991,7 +2172,12 @@ AI 助手應以繁體中文回覆使用者的問題與請求。`
 You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# AGENTS.md - OpenAI Codex CLI 規則
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -1999,7 +2185,12 @@ All responses should be in **English**.`,
 您是專業的軟體工程助手。請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# AGENTS.md - OpenAI Codex CLI Rules | OpenAI Codex CLI 規則
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -2010,7 +2201,15 @@ You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   'gemini-cli': {
     en: `# GEMINI.md - Gemini CLI Rules
@@ -2020,7 +2219,12 @@ All responses should be in **Traditional Chinese (繁體中文)**, with technica
 You are an expert software engineer assistant powered by Gemini. Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# GEMINI.md - Gemini CLI 規則
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -2028,7 +2232,12 @@ All responses should be in **English**.`,
 您是由 Gemini 驅動的專業軟體工程助手。請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# GEMINI.md - Gemini CLI Rules | Gemini CLI 規則
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -2039,7 +2248,15 @@ You are an expert software engineer assistant powered by Gemini. Follow these pr
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   },
   opencode: {
     en: `# AGENTS.md - OpenCode Rules
@@ -2049,7 +2266,12 @@ All responses should be in **Traditional Chinese (繁體中文)**, with technica
 You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language
-All responses should be in **English**.`,
+All responses should be in **English**.
+
+## Core Standards Usage Rule
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> This ensures token efficiency and focused context.`,
     'zh-tw': `# AGENTS.md - OpenCode 規則
 # 由 Universal Dev Standards CLI 生成
 # https://github.com/AsiaOstrich/universal-dev-standards
@@ -2057,7 +2279,12 @@ All responses should be in **English**.`,
 您是專業的軟體工程助手。請遵循以下專案標準。
 
 ## 對話語言 / Conversation Language
-所有回覆必須使用**繁體中文 (Traditional Chinese)**。`,
+所有回覆必須使用**繁體中文 (Traditional Chinese)**。
+
+## 核心標準使用規則 / Core Standards Usage Rule
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> 這確保了 Token 效率和上下文聚焦。`,
     bilingual: `# AGENTS.md - OpenCode Rules | OpenCode 規則
 # Generated by Universal Dev Standards CLI
 # 由 Universal Dev Standards CLI 生成
@@ -2068,7 +2295,15 @@ You are an expert software engineer assistant. Follow these project standards.
 
 ## Conversation Language / 對話語言
 All responses should be in **Traditional Chinese (繁體中文)**, with technical terms in English where appropriate.
-所有回覆必須使用**繁體中文**，技術術語可保留英文。`
+所有回覆必須使用**繁體中文**，技術術語可保留英文。
+
+## Core Standards Usage Rule / 核心標準使用規則
+> When verifying standards, checking code, or performing tasks, **PRIORITIZE** reading the concise rules in \`core/\` (e.g., \`core/testing-standards.md\`).
+> 當驗證標準、檢查程式碼或執行任務時，**優先**讀取 \`core/\` 中的精簡規則（例如 \`core/testing-standards.md\`）。
+> **ONLY** read \`core/guides/\` or \`methodologies/guides/\` when explicitly asked for educational content, detailed explanations, or tutorials.
+> 只有在被明確要求提供教育內容、詳細解釋或教學時，才讀取 \`core/guides/\` 或 \`methodologies/guides/\`。
+> This ensures token efficiency and focused context.
+> 這確保了 Token 效率和上下文聚焦。`
   }
 };
 
@@ -2154,6 +2389,60 @@ export function generateMinimalStandardsReference(installedStandards, format, la
   return sections.join('\n');
 }
 
+/**
+ * Generate commit message language directive for integration files
+ * Ensures AI tools always know the expected commit language, even when
+ * commit-message.ai.yaml is not installed as a standard.
+ * @param {string} commitLanguage - 'english', 'traditional-chinese', 'simplified-chinese', 'bilingual', or 'bilingual-zhcn'
+ * @param {string} language - Display language: 'en', 'zh-tw', 'zh-cn', or 'bilingual'
+ * @returns {string|null} The directive section, or null if not needed
+ */
+function generateCommitLanguageDirective(commitLanguage, language) {
+  if (!commitLanguage || commitLanguage === 'english') {
+    // For zh-tw/zh-cn display language with english commits, still add a note
+    if (language === 'zh-tw') {
+      return '## 提交訊息語言\n所有提交訊息使用**英文**撰寫。';
+    }
+    if (language === 'zh-cn') {
+      return '## 提交消息语言\n所有提交消息使用**英文**撰写。';
+    }
+    return null; // English display + English commits = no directive needed
+  }
+
+  if (commitLanguage === 'traditional-chinese') {
+    if (language === 'zh-tw') {
+      return '## 提交訊息語言\n所有提交訊息必須使用**繁體中文**撰寫。\n格式：`<類型>(<範圍>): <主旨>`';
+    }
+    if (language === 'zh-cn') {
+      return '## 提交消息语言\n所有提交消息必须使用**繁体中文**撰写。\n格式：`<类型>(<范围>): <主旨>`';
+    }
+    return '## Commit Message Language\nWrite all commit messages in **Traditional Chinese (繁體中文)**.\nFormat: `<類型>(<範圍>): <主旨>`';
+  }
+
+  if (commitLanguage === 'simplified-chinese') {
+    if (language === 'zh-tw') {
+      return '## 提交訊息語言\n所有提交訊息必須使用**簡體中文**撰寫。\n格式：`<类型>(<范围>): <主旨>`';
+    }
+    if (language === 'zh-cn') {
+      return '## 提交消息语言\n所有提交消息必须使用**简体中文**撰写。\n格式：`<类型>(<范围>): <主旨>`';
+    }
+    return '## Commit Message Language\nWrite all commit messages in **Simplified Chinese (简体中文)**.\nFormat: `<类型>(<范围>): <主旨>`';
+  }
+
+  if (commitLanguage === 'bilingual' || commitLanguage === 'bilingual-zhcn') {
+    const secondary = commitLanguage === 'bilingual-zhcn' ? '简体中文' : '繁體中文';
+    if (language === 'zh-tw') {
+      return `## 提交訊息語言\n使用**雙語**格式撰寫提交訊息（英文 + ${secondary}）。\n格式：\`<type>(<scope>): <English>. <中文>.\``;
+    }
+    if (language === 'zh-cn') {
+      return `## 提交消息语言\n使用**双语**格式撰写提交消息（英文 + ${secondary}）。\n格式：\`<type>(<scope>): <English>. <中文>.\``;
+    }
+    return `## Commit Message Language\nWrite commit messages in **bilingual** format (English + ${secondary}).\nFormat: \`<type>(<scope>): <English>. <中文>.\``;
+  }
+
+  return null;
+}
+
 /**
  * Generate integration file content
  * @param {Object} config - Integration configuration
@@ -2177,7 +2466,7 @@ export function generateIntegrationContent(config) {
   } = config;
 
   const sections = [];
-  const format = TOOL_FORMATS[tool] || 'markdown';
+  const format = getToolFormat(tool) || 'markdown';
 
   // Add header
   const header = TOOL_HEADERS[tool]?.[language] || TOOL_HEADERS[tool]?.en || '';
@@ -2188,7 +2477,13 @@ export function generateIntegrationContent(config) {
   for (const categoryId of categories) {
     // Special handling for commit-standards: use dynamic generation based on commitLanguage
     if (categoryId === 'commit-standards') {
-      const commitContent = generateCommitStandardsContent(commitLanguage, detailLevel);
+      // When bilingual is selected with zh-cn display language, use bilingual-zhcn template
+      // This provides Simplified Chinese content instead of Traditional Chinese
+      let effectiveCommitLanguage = commitLanguage;
+      if (commitLanguage === 'bilingual' && language === 'zh-cn') {
+        effectiveCommitLanguage = 'bilingual-zhcn';
+      }
+      const commitContent = generateCommitStandardsContent(effectiveCommitLanguage, detailLevel);
       sections.push(commitContent);
       sections.push('\n---\n');
       continue;
@@ -2209,33 +2504,43 @@ export function generateIntegrationContent(config) {
 
   // Add standards reference/compliance instructions (based on contentMode)
   // ALL modes should reference installed standards, just with different detail levels
-  if (installedStandards.length > 0) {
+  if (installedStandards.length > 0 || commitLanguage) {
     let standardsContent = '';
 
-    if (contentMode === 'minimal') {
-      // Minimal mode: simple reference list
-      standardsContent = generateMinimalStandardsReference(
-        installedStandards,
-        format,
-        language
-      );
-    } else {
-      // Index/Full mode: detailed compliance instructions + index
-      const complianceInstructions = generateComplianceInstructions(
-        installedStandards,
-        contentMode,
-        format,
-        language
-      );
-
-      const standardsIndex = generateStandardsIndex(
-        installedStandards,
-        format,
-        language,
-        level
-      );
-
-      standardsContent = complianceInstructions + '\n\n' + standardsIndex;
+    // Include commit message language directive inside markers so it updates with marker-based updates
+    if (commitLanguage) {
+      const commitLangSection = generateCommitLanguageDirective(commitLanguage, language);
+      if (commitLangSection) {
+        standardsContent += commitLangSection + '\n\n';
+      }
+    }
+
+    if (installedStandards.length > 0) {
+      if (contentMode === 'minimal') {
+        // Minimal mode: simple reference list
+        standardsContent += generateMinimalStandardsReference(
+          installedStandards,
+          format,
+          language
+        );
+      } else {
+        // Index/Full mode: detailed compliance instructions + index
+        const complianceInstructions = generateComplianceInstructions(
+          installedStandards,
+          contentMode,
+          format,
+          language
+        );
+
+        const standardsIndex = generateStandardsIndex(
+          installedStandards,
+          format,
+          language,
+          level
+        );
+
+        standardsContent += complianceInstructions + '\n\n' + standardsIndex;
+      }
     }
 
     // Wrap with markers for future updates
@@ -2318,7 +2623,7 @@ export function mergeRules(existingContent, newContent, strategy) {
  * @returns {Object} Result with success status
  */
 export function writeIntegrationFile(tool, config, projectPath) {
-  const fileName = TOOL_FILES[tool];
+  const fileName = getToolFileName(tool);
   if (!fileName) {
     return { success: false, error: `Unknown tool: ${tool}` };
   }
@@ -2335,9 +2640,21 @@ export function writeIntegrationFile(tool, config, projectPath) {
     let content = generateIntegrationContent({ ...config, tool });
 
     // Handle merge if file exists
-    if (existsSync(filePath) && config.mergeStrategy) {
+    if (existsSync(filePath)) {
       const existingContent = readFileSync(filePath, 'utf-8');
-      content = mergeRules(existingContent, content, config.mergeStrategy);
+
+      if (config.mergeStrategy) {
+        // Explicit merge strategy takes precedence
+        content = mergeRules(existingContent, content, config.mergeStrategy);
+      } else {
+        // Default: marker-based update preserves user content outside markers
+        const format = getToolFormat(tool);
+        const newParts = extractMarkedContent(content, format);
+        if (newParts.content) {
+          content = updateMarkedSection(existingContent, newParts.content, format);
+        }
+        // If new content has no markers, overwrite entirely (backward compat)
+      }
     }
 
     writeFileSync(filePath, content);
@@ -2363,7 +2680,7 @@ export function writeIntegrationFile(tool, config, projectPath) {
  * @returns {boolean} True if file exists
  */
 export function integrationFileExists(tool, projectPath) {
-  const fileName = TOOL_FILES[tool];
+  const fileName = getToolFileName(tool);
   return fileName && existsSync(join(projectPath, fileName));
 }
 
@@ -2547,7 +2864,7 @@ export function generateStandardsIndex(installedStandards, format, language = 'z
  * @returns {string} Content wrapped with markers
  */
 export function wrapWithMarkers(content, format) {
-  const markers = MARKERS[format] || MARKERS.markdown;
+  const markers = UDS_MARKERS[format] || UDS_MARKERS.markdown;
   return `${markers.start}\n${content}\n${markers.end}`;
 }
 
@@ -2558,7 +2875,7 @@ export function wrapWithMarkers(content, format) {
  * @returns {Object} Object with before, content, and after parts
  */
 export function extractMarkedContent(fileContent, format) {
-  const markers = MARKERS[format] || MARKERS.markdown;
+  const markers = UDS_MARKERS[format] || UDS_MARKERS.markdown;
   const startIdx = fileContent.indexOf(markers.start);
   const endIdx = fileContent.indexOf(markers.end);
 
@@ -2581,7 +2898,7 @@ export function extractMarkedContent(fileContent, format) {
  * @returns {string} Updated file content
  */
 export function updateMarkedSection(existingContent, newMarkedContent, format) {
-  const markers = MARKERS[format] || MARKERS.markdown;
+  const markers = UDS_MARKERS[format] || UDS_MARKERS.markdown;
   const startIdx = existingContent.indexOf(markers.start);
   const endIdx = existingContent.indexOf(markers.end);
 
@@ -2603,24 +2920,17 @@ export function updateMarkedSection(existingContent, newMarkedContent, format) {
  * @returns {string|null} File path or null if unknown tool
  */
 export function getToolFilePath(tool) {
-  return TOOL_FILES[tool] || null;
+  return getToolFileName(tool) || null;
 }
 
-/**
- * Get tool format type
- * @param {string} tool - Tool name
- * @returns {string} Format type: 'markdown' or 'plaintext'
- */
-export function getToolFormat(tool) {
-  return TOOL_FORMATS[tool] || 'markdown';
-}
+
 
 /**
  * Get all supported tools
  * @returns {string[]} Array of tool names
  */
 export function getSupportedTools() {
-  return Object.keys(TOOL_FILES);
+  return Object.keys(SUPPORTED_AI_TOOLS).concat(Object.keys(LEGACY_TOOL_MAPPINGS)).filter((v, i, a) => a.indexOf(v) === i);
 }
 
 /**
@@ -2630,5 +2940,5 @@ export function getSupportedTools() {
  * @returns {boolean} True if tools share the same file
  */
 export function toolsShareFile(tool1, tool2) {
-  return TOOL_FILES[tool1] && TOOL_FILES[tool1] === TOOL_FILES[tool2];
+  return getToolFileName(tool1) && getToolFileName(tool1) === getToolFileName(tool2);
 }