cx-viewer 1.0.0

package/concepts/zh-TW/Tool-AskUserQuestion.md

@@ -0,0 +1,75 @@
+# AskUserQuestion
+
+## 定義
+
+在執行過程中向使用者提問，用於取得澄清、驗證假設或請求決策。
+
+## 參數
+
+| 參數 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `questions` | array | 是 | 問題列表（1-4 個問題） |
+| `answers` | object | 否 | 使用者收集的答案 |
+| `annotations` | object | 否 | 每個問題的註解（如預覽選擇的備註） |
+| `metadata` | object | 否 | 追蹤和分析用的中繼資料 |
+
+每個 `question` 物件：
+
+| 欄位 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `question` | string | 是 | 完整的問題文字，應以問號結尾 |
+| `header` | string | 是 | 短標籤（最多 12 字元），顯示為標籤晶片 |
+| `options` | array | 是 | 2-4 個選項 |
+| `multiSelect` | boolean | 是 | 是否允許多選 |
+
+每個 `option` 物件：
+
+| 欄位 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `label` | string | 是 | 選項顯示文字（1-5 個詞） |
+| `description` | string | 是 | 選項說明 |
+| `markdown` | string | 否 | 預覽內容（用於 ASCII 佈局、程式碼片段等的視覺化對比） |
+
+## 使用場景
+
+**適合使用：**
+- 收集使用者偏好或需求
+- 澄清模糊的指令
+- 在實施過程中取得決策
+- 向使用者提供方向選擇
+
+**不適合使用：**
+- 問「方案可以嗎？」——應使用 ExitPlanMode
+
+## 注意事項
+
+- 使用者始終可以選擇 "Other" 提供自訂輸入
+- 推薦選項放在第一位，並在 label 末尾加 "(Recommended)"
+- `markdown` 預覽僅支援單選問題
+- 有 `markdown` 的選項會切換為左右並排佈局
+- 在規劃模式中，用於在確定方案前澄清需求
+
+## 原文
+
+<textarea readonly>Use this tool when you need to ask the user questions during execution. This allows you to:
+1. Gather user preferences or requirements
+2. Clarify ambiguous instructions
+3. Get decisions on implementation choices as you work
+4. Offer choices to the user about what direction to take.
+
+Usage notes:
+- Users will always be able to select "Other" to provide custom text input
+- Use multiSelect: true to allow multiple answers to be selected for a question
+- If you recommend a specific option, make that the first option in the list and add "(Recommended)" at the end of the label
+
+Plan mode note: In plan mode, use this tool to clarify requirements or choose between approaches BEFORE finalizing your plan. Do NOT use this tool to ask "Is my plan ready?" or "Should I proceed?" - use ExitPlanMode for plan approval. IMPORTANT: Do not reference "the plan" in your questions (e.g., "Do you have feedback about the plan?", "Does the plan look good?") because the user cannot see the plan in the UI until you call ExitPlanMode. If you need plan approval, use ExitPlanMode instead.
+
+Preview feature:
+Use the optional `markdown` field on options when presenting concrete artifacts that users need to visually compare:
+- ASCII mockups of UI layouts or components
+- Code snippets showing different implementations
+- Diagram variations
+- Configuration examples
+
+When any option has a markdown, the UI switches to a side-by-side layout with a vertical option list on the left and preview on the right. Do not use previews for simple preference questions where labels and descriptions suffice. Note: previews are only supported for single-select questions (not multiSelect).
+</textarea>

package/concepts/zh-TW/Tool-Bash.md

@@ -0,0 +1,167 @@
+# Bash
+
+## 定義
+
+執行 shell 命令，支援可選的逾時設定。工作目錄在命令間持久化，但 shell 狀態（環境變數等）不持久化。
+
+## 參數
+
+| 參數 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `command` | string | 是 | 要執行的 bash 命令 |
+| `description` | string | 否 | 命令的簡短描述 |
+| `timeout` | number | 否 | 逾時時間（毫秒），最大 600000，預設 120000 |
+| `run_in_background` | boolean | 否 | 是否背景執行 |
+
+## 使用場景
+
+**適合使用：**
+- git 操作（commit、push、branch 等）
+- npm/yarn 等套件管理命令
+- docker 操作
+- 編譯、建置命令
+- 列出目錄內容（`ls`）
+- 其他需要 shell 執行的系統命令
+
+**不適合使用：**
+- 讀取檔案——應使用 Read
+- 搜尋檔案名稱——應使用 Glob
+- 搜尋檔案內容——應使用 Grep
+- 編輯檔案——應使用 Edit
+- 寫入檔案——應使用 Write
+- 向使用者輸出資訊——直接在回應文字中輸出
+- 長時間執行的程序（dev server、watch 模式）——建議使用者手動執行
+
+## 注意事項
+
+- 包含空格的路徑必須用雙引號包裹
+- 輸出超過 30000 字元會被截斷
+- 背景執行的命令透過 TaskOutput 取得結果
+- 盡量使用絕對路徑，避免 `cd`
+- 獨立命令可以並行呼叫多個 Bash
+- 有依賴關係的命令用 `&&` 鏈接
+- Shell 環境從使用者的 profile（bash 或 zsh）初始化
+
+## 原文
+
+<textarea readonly>Executes a given bash command and returns its output.
+
+The working directory persists between commands, but shell state does not. The shell environment is initialized from the user's profile (bash or zsh).
+
+IMPORTANT: Avoid using this tool to run `find`, `grep`, `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:
+
+ - File search: Use Glob (NOT find or ls)
+ - Content search: Use Grep (NOT grep or rg)
+ - Read files: Use Read (NOT cat/head/tail)
+ - Edit files: Use Edit (NOT sed/awk)
+ - Write files: Use Write (NOT echo >/cat <<EOF)
+ - Communication: Output text directly (NOT echo/printf)
+While the Bash tool can do similar things, it’s better to use the built-in tools as they provide a better user experience and make it easier to review tool calls and give permission.
+
+# Instructions
+ - If your command will create new directories or files, first use this tool to run `ls` to verify the parent directory exists and is the correct location.
+ - Always quote file paths that contain spaces with double quotes in your command (e.g., cd "path with spaces/file.txt")
+ - Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it.
+ - You may specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). By default, your command will timeout after 120000ms (2 minutes).
+ - You can use the `run_in_background` parameter to run the command in the background. Only use this if you don't need the result immediately and are OK being notified when the command completes later. You do not need to check the output right away - you'll be notified when it finishes. You do not need to use '&' at the end of the command when using this parameter.
+ - Write a clear, concise description of what your command does. For simple commands, keep it brief (5-10 words). For complex commands (piped commands, obscure flags, or anything hard to understand at a glance), include enough context so that the user can understand what your command will do.
+ - When issuing multiple commands:
+  - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message. Example: if you need to run "git status" and "git diff", send a single message with two Bash tool calls in parallel.
+  - If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together.
+  - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail.
+  - DO NOT use newlines to separate commands (newlines are ok in quoted strings).
+ - For git commands:
+  - Prefer to create a new commit rather than amending an existing commit.
+  - Before running destructive operations (e.g., git reset --hard, git push --force, git checkout --), consider whether there is a safer alternative that achieves the same goal. Only use destructive operations when they are truly the best approach.
+  - Never skip hooks (--no-verify) or bypass signing (--no-gpg-sign, -c commit.gpgsign=false) unless the user has explicitly asked for it. If a hook fails, investigate and fix the underlying issue.
+ - Avoid unnecessary `sleep` commands:
+  - Do not sleep between commands that can run immediately — just run them.
+  - If your command is long running and you would like to be notified when it finishes – simply run your command using `run_in_background`. There is no need to sleep in this case.
+  - Do not retry failing commands in a sleep loop — diagnose the root cause or consider an alternative approach.
+  - If waiting for a background task you started with `run_in_background`, you will be notified when it completes — do not poll.
+  - If you must poll an external process, use a check command (e.g. `gh run view`) rather than sleeping first.
+  - If you must sleep, keep the duration short (1-5 seconds) to avoid blocking the user.
+
+# Committing changes with git
+
+Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:
+
+Git Safety Protocol:
+- NEVER update the git config
+- NEVER run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests these actions. Taking unauthorized destructive actions is unhelpful and can result in lost work, so it's best to ONLY run these commands when given direct instructions 
+- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
+- NEVER run force push to main/master, warn the user if they request it
+- CRITICAL: Always create NEW commits rather than amending, unless the user explicitly requests a git amend. When a pre-commit hook fails, the commit did NOT happen — so --amend would modify the PREVIOUS commit, which may result in destroying work or losing previous changes. Instead, after hook failure, fix the issue, re-stage, and create a NEW commit
+- When staging files, prefer adding specific files by name rather than using "git add -A" or "git add .", which can accidentally include sensitive files (.env, credentials) or large binaries
+- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive
+
+1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:
+  - Run a git status command to see all untracked files. IMPORTANT: Never use the -uall flag as it can cause memory issues on large repos.
+  - Run a git diff command to see both staged and unstaged changes that will be committed.
+  - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.
+2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:
+  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).
+  - Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
+  - Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
+  - Ensure it accurately reflects the changes and their purpose
+3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands:
+   - Add relevant untracked files to the staging area.
+   - Create the commit with a message ending with:
+   Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
+   - Run git status after the commit completes to verify success.
+   Note: git status depends on the commit completing, so run it sequentially after the commit.
+4. If the commit fails due to pre-commit hook: fix the issue and create a NEW commit
+
+Important notes:
+- NEVER run additional commands to read or explore code, besides git bash commands
+- NEVER use the TodoWrite or Agent tools
+- DO NOT push to the remote repository unless the user explicitly asks you to do so
+- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.
+- IMPORTANT: Do not use --no-edit with git rebase commands, as the --no-edit flag is not a valid option for git rebase.
+- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
+- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:
+<example>
+git commit -m "$(cat <<'EOF'
+   Commit message here.
+
+   Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
+   EOF
+   )"
+</example>
+
+# Creating pull requests
+Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.
+
+IMPORTANT: When the user asks you to create a pull request, follow these steps carefully:
+
+1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:
+   - Run a git status command to see all untracked files (never use -uall flag)
+   - Run a git diff command to see both staged and unstaged changes that will be committed
+   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote
+   - Run a git log command and `git diff [base-branch]...HEAD` to understand the full commit history for the current branch (from the time it diverged from the base branch)
+2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request title and summary:
+   - Keep the PR title short (under 70 characters)
+   - Use the description/body for details, not the title
+3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel:
+   - Create new branch if needed
+   - Push to remote with -u flag if needed
+   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.
+<example>
+gh pr create --title "the pr title" --body "$(cat <<'EOF'
+## Summary
+<1-3 bullet points>
+
+## Test plan
+[Bulleted markdown checklist of TODOs for testing the pull request...]
+
+🤖 Generated with [Codex](https://claude.com/claude-code)
+EOF
+)"
+</example>
+
+Important:
+- DO NOT use the TodoWrite or Agent tools
+- Return the PR URL when you're done, so the user can see it
+
+# Other common operations
+- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments</textarea>

package/concepts/zh-TW/Tool-Edit.md

@@ -0,0 +1,46 @@
+# Edit
+
+## 定義
+
+透過精確的字串替換來編輯檔案。將檔案中的 `old_string` 替換為 `new_string`。
+
+## 參數
+
+| 參數 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `file_path` | string | 是 | 要修改的檔案的絕對路徑 |
+| `old_string` | string | 是 | 要替換的原始文字 |
+| `new_string` | string | 是 | 替換後的新文字（必須與 old_string 不同） |
+| `replace_all` | boolean | 否 | 是否替換所有匹配項，預設 `false` |
+
+## 使用場景
+
+**適合使用：**
+- 修改現有檔案中的特定程式碼段
+- 修復 bug、更新邏輯
+- 重新命名變數（配合 `replace_all: true`）
+- 任何需要精確修改檔案內容的場景
+
+**不適合使用：**
+- 建立新檔案——應使用 Write
+- 大規模重寫——可能需要 Write 覆寫整個檔案
+
+## 注意事項
+
+- 使用前必須先透過 Read 讀取過該檔案，否則會報錯
+- `old_string` 在檔案中必須是唯一的，否則編輯失敗。如果不唯一，需要提供更多上下文使其唯一，或使用 `replace_all`
+- 編輯文字時必須保持原始縮排（tab/空格），不要包含 Read 輸出中的行號前綴
+- 優先編輯現有檔案，而非建立新檔案
+- `new_string` 必須與 `old_string` 不同
+
+## 原文
+
+<textarea readonly>Performs exact string replacements in files.
+
+Usage:
+- You must use your `Read` tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file. 
+- When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: spaces + line number + tab. Everything after that tab is the actual file content to match. Never include any part of the line number prefix in the old_string or new_string.
+- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
+- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
+- The edit will FAIL if `old_string` is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use `replace_all` to change every instance of `old_string`.
+- Use `replace_all` for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.</textarea>

package/concepts/zh-TW/Tool-EnterPlanMode.md

@@ -0,0 +1,128 @@
+# EnterPlanMode
+
+## 定義
+
+將 Codex 切換到規劃模式，用於在實施前探索程式碼庫並設計方案。
+
+## 參數
+
+無參數。
+
+## 使用場景
+
+**適合使用：**
+- 新功能實作——需要架構決策
+- 存在多種可行方案——需要使用者選擇
+- 程式碼修改影響現有行為或結構
+- 多檔案變更——可能涉及 2-3 個以上檔案
+- 需求不明確——需要先探索再理解範圍
+- 使用者偏好很重要——實作可以有多種合理方向
+
+**不適合使用：**
+- 單行或少量行的修復（拼寫錯誤、明顯 bug）
+- 使用者已給出非常具體的指令
+- 純研究/探索任務——應使用 Task（Explore 類型）
+
+## 規劃模式中的行為
+
+進入規劃模式後，Codex 會：
+1. 使用 Glob、Grep、Read 工具深入探索程式碼庫
+2. 理解現有模式和架構
+3. 設計實施方案
+4. 將方案提交給使用者審批
+5. 如需澄清可使用 AskUserQuestion
+6. 方案就緒後透過 ExitPlanMode 退出
+
+## 注意事項
+
+- 此工具需要使用者同意才能進入規劃模式
+- 如果不確定是否需要規劃，傾向於規劃——提前對齊比返工好
+
+## 原文
+
+<textarea readonly>Use this tool proactively when you're about to start a non-trivial implementation task. Getting user sign-off on your approach before writing code prevents wasted effort and ensures alignment. This tool transitions you into plan mode where you can explore the codebase and design an implementation approach for user approval.
+
+## When to Use This Tool
+
+**Prefer using EnterPlanMode** for implementation tasks unless they're simple. Use it when ANY of these conditions apply:
+
+1. **New Feature Implementation**: Adding meaningful new functionality
+   - Example: "Add a logout button" - where should it go? What should happen on click?
+   - Example: "Add form validation" - what rules? What error messages?
+
+2. **Multiple Valid Approaches**: The task can be solved in several different ways
+   - Example: "Add caching to the API" - could use Redis, in-memory, file-based, etc.
+   - Example: "Improve performance" - many optimization strategies possible
+
+3. **Code Modifications**: Changes that affect existing behavior or structure
+   - Example: "Update the login flow" - what exactly should change?
+   - Example: "Refactor this component" - what's the target architecture?
+
+4. **Architectural Decisions**: The task requires choosing between patterns or technologies
+   - Example: "Add real-time updates" - WebSockets vs SSE vs polling
+   - Example: "Implement state management" - Redux vs Context vs custom solution
+
+5. **Multi-File Changes**: The task will likely touch more than 2-3 files
+   - Example: "Refactor the authentication system"
+   - Example: "Add a new API endpoint with tests"
+
+6. **Unclear Requirements**: You need to explore before understanding the full scope
+   - Example: "Make the app faster" - need to profile and identify bottlenecks
+   - Example: "Fix the bug in checkout" - need to investigate root cause
+
+7. **User Preferences Matter**: The implementation could reasonably go multiple ways
+   - If you would use AskUserQuestion to clarify the approach, use EnterPlanMode instead
+   - Plan mode lets you explore first, then present options with context
+
+## When NOT to Use This Tool
+
+Only skip EnterPlanMode for simple tasks:
+- Single-line or few-line fixes (typos, obvious bugs, small tweaks)
+- Adding a single function with clear requirements
+- Tasks where the user has given very specific, detailed instructions
+- Pure research/exploration tasks (use the Agent tool with explore agent instead)
+
+## What Happens in Plan Mode
+
+In plan mode, you'll:
+1. Thoroughly explore the codebase using Glob, Grep, and Read tools
+2. Understand existing patterns and architecture
+3. Design an implementation approach
+4. Present your plan to the user for approval
+5. Use AskUserQuestion if you need to clarify approaches
+6. Exit plan mode with ExitPlanMode when ready to implement
+
+## Examples
+
+### GOOD - Use EnterPlanMode:
+User: "Add user authentication to the app"
+- Requires architectural decisions (session vs JWT, where to store tokens, middleware structure)
+
+User: "Optimize the database queries"
+- Multiple approaches possible, need to profile first, significant impact
+
+User: "Implement dark mode"
+- Architectural decision on theme system, affects many components
+
+User: "Add a delete button to the user profile"
+- Seems simple but involves: where to place it, confirmation dialog, API call, error handling, state updates
+
+User: "Update the error handling in the API"
+- Affects multiple files, user should approve the approach
+
+### BAD - Don't use EnterPlanMode:
+User: "Fix the typo in the README"
+- Straightforward, no planning needed
+
+User: "Add a console.log to debug this function"
+- Simple, obvious implementation
+
+User: "What files handle routing?"
+- Research task, not implementation planning
+
+## Important Notes
+
+- This tool REQUIRES user approval - they must consent to entering plan mode
+- If unsure whether to use it, err on the side of planning - it's better to get alignment upfront than to redo work
+- Users appreciate being consulted before significant changes are made to their codebase
+</textarea>

package/concepts/zh-TW/Tool-EnterWorktree.md

@@ -0,0 +1,56 @@
+# EnterWorktree
+
+## 定義
+
+Creates an isolated git worktree and switches the current session into it. Only used when the user explicitly asks to work in a worktree.
+
+## 參數
+
+| Name | Type | Required | Description |
+|---|---|---|---|
+| name | string | No | A name for the worktree. If not provided, a random name is generated. |
+
+## 使用場景
+
+**適合使用：**
+- The user explicitly says "worktree" (e.g., "start a worktree", "work in a worktree", "create a worktree")
+
+**不適合使用：**
+- The user asks to create/switch branches — use git commands instead
+- The user asks to fix a bug or work on a feature — use normal git workflow unless they specifically mention worktrees
+
+## 注意事項
+
+- Must be in a git repository, or have WorktreeCreate/WorktreeRemove hooks configured
+- Must not already be in a worktree
+
+## 原文
+
+<textarea readonly>Use this tool ONLY when the user explicitly asks to work in a worktree. This tool creates an isolated git worktree and switches the current session into it.
+
+## When to Use
+
+- The user explicitly says "worktree" (e.g., "start a worktree", "work in a worktree", "create a worktree", "use a worktree")
+
+## When NOT to Use
+
+- The user asks to create a branch, switch branches, or work on a different branch — use git commands instead
+- The user asks to fix a bug or work on a feature — use normal git workflow unless they specifically mention worktrees
+- Never use this tool unless the user explicitly mentions "worktree"
+
+## Requirements
+
+- Must be in a git repository, OR have WorktreeCreate/WorktreeRemove hooks configured in settings.json
+- Must not already be in a worktree
+
+## Behavior
+
+- In a git repository: creates a new git worktree inside `.claude/worktrees/` with a new branch based on HEAD
+- Outside a git repository: delegates to WorktreeCreate/WorktreeRemove hooks for VCS-agnostic isolation
+- Switches the session's working directory to the new worktree
+- On session exit, the user will be prompted to keep or remove the worktree
+
+## Parameters
+
+- `name` (optional): A name for the worktree. If not provided, a random name is generated.
+</textarea>

package/concepts/zh-TW/Tool-ExitPlanMode.md

@@ -0,0 +1,62 @@
+# ExitPlanMode
+
+## 定義
+
+退出規劃模式並將方案提交給使用者審批。方案內容從之前寫入的計畫檔案中讀取。
+
+## 參數
+
+| 參數 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `allowedPrompts` | array | 否 | 實施方案所需的權限描述列表 |
+
+`allowedPrompts` 陣列中每個元素：
+
+| 欄位 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `tool` | enum | 是 | 適用的工具，目前僅支援 `Bash` |
+| `prompt` | string | 是 | 操作的語義描述（如 "run tests"、"install dependencies"） |
+
+## 使用場景
+
+**適合使用：**
+- 規劃模式中方案已完成，準備提交使用者審批
+- 僅用於需要撰寫程式碼的實施任務
+
+**不適合使用：**
+- 純研究/探索任務——不需要退出規劃模式
+- 想問使用者「方案可以嗎？」——這正是此工具的功能，不要用 AskUserQuestion 來問
+
+## 注意事項
+
+- 此工具不接受方案內容作為參數——它從之前寫入的計畫檔案中讀取
+- 使用者會看到計畫檔案的內容來審批
+- 不要在呼叫此工具前用 AskUserQuestion 問「方案是否可以」，這是重複的
+- 不要在問題中提及「計畫」，因為使用者在 ExitPlanMode 之前看不到計畫內容
+
+## 原文
+
+<textarea readonly>Use this tool when you are in plan mode and have finished writing your plan to the plan file and are ready for user approval.
+
+## How This Tool Works
+- You should have already written your plan to the plan file specified in the plan mode system message
+- This tool does NOT take the plan content as a parameter - it will read the plan from the file you wrote
+- This tool simply signals that you're done planning and ready for the user to review and approve
+- The user will see the contents of your plan file when they review it
+
+## When to Use This Tool
+IMPORTANT: Only use this tool when the task requires planning the implementation steps of a task that requires writing code. For research tasks where you're gathering information, searching files, reading files or in general trying to understand the codebase - do NOT use this tool.
+
+## Before Using This Tool
+Ensure your plan is complete and unambiguous:
+- If you have unresolved questions about requirements or approach, use AskUserQuestion first (in earlier phases)
+- Once your plan is finalized, use THIS tool to request approval
+
+**Important:** Do NOT use AskUserQuestion to ask "Is this plan okay?" or "Should I proceed?" - that's exactly what THIS tool does. ExitPlanMode inherently requests user approval of your plan.
+
+## Examples
+
+1. Initial task: "Search for and understand the implementation of vim mode in the codebase" - Do not use the exit plan mode tool because you are not planning the implementation steps of a task.
+2. Initial task: "Help me implement yank mode for vim" - Use the exit plan mode tool after you have finished planning the implementation steps of the task.
+3. Initial task: "Add a new feature to handle user authentication" - If unsure about auth method (OAuth, JWT, etc.), use AskUserQuestion first, then use exit plan mode tool after clarifying the approach.
+</textarea>

package/concepts/zh-TW/Tool-Glob.md

@@ -0,0 +1,39 @@
+# Glob
+
+## 定義
+
+快速的檔案名稱模式匹配工具，支援任意規模的程式碼庫。回傳按修改時間排序的匹配檔案路徑。
+
+## 參數
+
+| 參數 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `pattern` | string | 是 | glob 模式（如 `**/*.js`、`src/**/*.ts`） |
+| `path` | string | 否 | 搜尋目錄，預設為當前工作目錄。不要傳 "undefined" 或 "null" |
+
+## 使用場景
+
+**適合使用：**
+- 按檔案名稱模式查找檔案
+- 查找特定類型的所有檔案（如所有 `.tsx` 檔案）
+- 查找特定類別定義（如 `class Foo`）時先定位檔案
+- 可以在單條訊息中並行發起多個 Glob 呼叫
+
+**不適合使用：**
+- 搜尋檔案內容——應使用 Grep
+- 需要多輪搜尋的開放式探索——應使用 Task（Explore 類型）
+
+## 注意事項
+
+- 支援標準 glob 語法：`*` 匹配單層，`**` 匹配多層，`{}` 匹配多選
+- 結果按修改時間排序
+- 比 Bash 的 `find` 命令更推薦使用
+
+## 原文
+
+<textarea readonly>- Fast file pattern matching tool that works with any codebase size
+- Supports glob patterns like "**/*.js" or "src/**/*.ts"
+- Returns matching file paths sorted by modification time
+- Use this tool when you need to find files by name patterns
+- When you are doing an open ended search that may require multiple rounds of globbing and grepping, use the Agent tool instead
+- You can call multiple tools in a single response. It is always better to speculatively perform multiple searches in parallel if they are potentially useful.</textarea>

package/concepts/zh-TW/Tool-Grep.md

@@ -0,0 +1,57 @@
+# Grep
+
+## 定義
+
+基於 ripgrep 的強大內容搜尋工具。支援正規表示式、檔案類型過濾和多種輸出模式。
+
+## 參數
+
+| 參數 | 類型 | 必填 | 說明 |
+|------|------|------|------|
+| `pattern` | string | 是 | 正規表示式搜尋模式 |
+| `path` | string | 否 | 搜尋路徑（檔案或目錄），預設當前工作目錄 |
+| `glob` | string | 否 | 檔案名稱過濾（如 `*.js`、`*.{ts,tsx}`） |
+| `type` | string | 否 | 檔案類型過濾（如 `js`、`py`、`rust`），比 glob 更高效 |
+| `output_mode` | enum | 否 | 輸出模式：`files_with_matches`（預設）、`content`、`count` |
+| `-i` | boolean | 否 | 大小寫不敏感搜尋 |
+| `-n` | boolean | 否 | 顯示行號（僅 content 模式），預設 true |
+| `-A` | number | 否 | 匹配後顯示的行數 |
+| `-B` | number | 否 | 匹配前顯示的行數 |
+| `-C` / `context` | number | 否 | 匹配前後顯示的行數 |
+| `head_limit` | number | 否 | 限制輸出條目數，預設 0（無限） |
+| `offset` | number | 否 | 跳過前 N 條結果 |
+| `multiline` | boolean | 否 | 啟用多行匹配模式，預設 false |
+
+## 使用場景
+
+**適合使用：**
+- 在程式碼庫中搜尋特定字串或模式
+- 查找函式/變數的使用位置
+- 按檔案類型過濾搜尋結果
+- 統計匹配數量
+
+**不適合使用：**
+- 按檔案名稱查找檔案——應使用 Glob
+- 需要多輪搜尋的開放式探索——應使用 Task（Explore 類型）
+
+## 注意事項
+
+- 使用 ripgrep 語法（非 grep），花括號等特殊字元需要跳脫
+- `files_with_matches` 模式只回傳檔案路徑，最高效
+- `content` 模式回傳匹配行內容，支援上下文行
+- 多行匹配需要設定 `multiline: true`
+- 始終優先使用 Grep 工具而非 Bash 中的 `grep` 或 `rg` 命令
+
+## 原文
+
+<textarea readonly>A powerful search tool built on ripgrep
+
+  Usage:
+  - ALWAYS use Grep for search tasks. NEVER invoke `grep` or `rg` as a Bash command. The Grep tool has been optimized for correct permissions and access.
+  - Supports full regex syntax (e.g., "log.*Error", "function\s+\w+")
+  - Filter files with glob parameter (e.g., "*.js", "**/*.tsx") or type parameter (e.g., "js", "py", "rust")
+  - Output modes: "content" shows matching lines, "files_with_matches" shows only file paths (default), "count" shows match counts
+  - Use Agent tool for open-ended searches requiring multiple rounds
+  - Pattern syntax: Uses ripgrep (not grep) - literal braces need escaping (use `interface\{\}` to find `interface{}` in Go code)
+  - Multiline matching: By default patterns match within single lines only. For cross-line patterns like `struct \{[\s\S]*?field`, use `multiline: true`
+</textarea>