cx-viewer 1.0.0

package/concepts/ko/Tool-Agent.md

@@ -0,0 +1,125 @@
+# Agent
+
+## 정의
+
+서브 agent (SubAgent)를 시작하여 복잡한 다단계 태스크를 자율적으로 처리합니다. 서브 agent는 독립된 서브프로세스로, 각각 전용 도구 세트와 컨텍스트를 가집니다. Agent는 최신 Claude Code 버전에서 Task 도구의 이름이 변경된 버전입니다.
+
+## 파라미터
+
+| 파라미터 | 타입 | 필수 | 설명 |
+|----------|------|------|------|
+| `prompt` | string | 예 | 서브 agent가 실행할 태스크 설명 |
+| `description` | string | 예 | 3~5단어의 짧은 요약 |
+| `subagent_type` | string | 예 | 서브 agent 타입, 사용 가능한 도구 세트를 결정 |
+| `model` | enum | 아니오 | 모델 지정 (sonnet / opus / haiku), 기본값은 부모로부터 상속 |
+| `max_turns` | integer | 아니오 | 최대 agentic 턴 수 |
+| `run_in_background` | boolean | 아니오 | 백그라운드 실행 여부. 백그라운드 태스크는 output_file 경로를 반환 |
+| `resume` | string | 아니오 | 재개할 agent ID, 이전 실행에서 계속. 컨텍스트를 잃지 않고 이전 서브 agent를 이어받는 데 유용 |
+| `isolation` | enum | 아니오 | 격리 모드, `worktree`로 임시 git worktree 생성 |
+
+## 서브 agent 타입
+
+| 타입 | 용도 | 사용 가능한 도구 |
+|------|------|------------------|
+| `Bash` | 명령 실행, git 작업 | Bash |
+| `general-purpose` | 범용 다단계 태스크 | 전체 도구 |
+| `Explore` | 코드베이스 빠른 탐색 | Agent/Edit/Write/NotebookEdit/ExitPlanMode 외 모든 도구 |
+| `Plan` | 구현 방안 설계 | Agent/Edit/Write/NotebookEdit/ExitPlanMode 외 모든 도구 |
+| `claude-code-guide` | Claude Code 사용 가이드 Q&A | Glob, Grep, Read, WebFetch, WebSearch |
+| `statusline-setup` | 상태 표시줄 설정 | Read, Edit |
+
+## 사용 시나리오
+
+**적합한 경우:**
+- 다단계로 자율 완료해야 하는 복잡한 태스크
+- 코드베이스 탐색 및 심층 조사 (Explore 타입 사용)
+- 격리 환경이 필요한 병렬 작업
+- 백그라운드 실행이 필요한 장시간 태스크
+
+**적합하지 않은 경우:**
+- 특정 파일 경로 읽기 — 직접 Read 또는 Glob 사용
+- 2~3개 알려진 파일 내 검색 — 직접 Read 사용
+- 특정 클래스 정의 검색 — 직접 Glob 사용
+
+## 주의사항
+
+- 서브 agent는 완료 후 단일 메시지를 반환하며, 그 결과는 사용자에게 보이지 않으므로 메인 agent가 전달해야 함
+- 단일 메시지 내에서 여러 병렬 Agent 호출을 발행하여 효율 향상 가능
+- 백그라운드 태스크는 TaskOutput 도구로 진행 상황 확인
+- Explore 타입은 직접 Glob/Grep 호출보다 느리므로, 단순 검색으로 충분하지 않을 때만 사용
+- 장시간 실행되며 즉시 결과가 필요 없는 태스크에는 `run_in_background: true` 권장; 결과가 필요한 경우 포그라운드(기본값) 사용
+- `resume` 파라미터를 통해 이전에 시작한 서브 agent 세션을 계속할 수 있으며, 축적된 컨텍스트를 유지
+
+## 원문
+
+<textarea readonly>Launch a new agent to handle complex, multi-step tasks autonomously.
+
+The Agent tool launches specialized agents (subprocesses) that autonomously handle complex tasks. Each agent type has specific capabilities and tools available to it.
+
+Available agent types and the tools they have access to:
+- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)
+- statusline-setup: Use this agent to configure the user's Claude Code status line setting. (Tools: Read, Edit)
+- Explore: Fast agent specialized for exploring codebases. Use this when you need to quickly find files by patterns (eg. "src/components/**/*.tsx"), search code for keywords (eg. "API endpoints"), or answer questions about the codebase (eg. "how do API endpoints work?"). When calling this agent, specify the desired thoroughness level: "quick" for basic searches, "medium" for moderate exploration, or "very thorough" for comprehensive analysis across multiple locations and naming conventions. (Tools: All tools except Agent, ExitPlanMode, Edit, Write, NotebookEdit)
+- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, ExitPlanMode, Edit, Write, NotebookEdit)
+- claude-code-guide: Use this agent when the user asks questions ("Can Claude...", "Does Claude...", "How do I...") about: (1) Claude Code (the CLI tool) - features, hooks, slash commands, MCP servers, settings, IDE integrations, keyboard shortcuts; (2) Claude Agent SDK - building custom agents; (3) Claude API (formerly Anthropic API) - API usage, tool use, Anthropic SDK usage. **IMPORTANT:** Before spawning a new agent, check if there is already a running or recently completed claude-code-guide agent that you can resume using the "resume" parameter. (Tools: Glob, Grep, Read, WebFetch, WebSearch)
+
+When using the Agent tool, you must specify a subagent_type parameter to select which agent type to use.
+
+When NOT to use the Agent tool:
+- If you want to read a specific file path, use the Read or Glob tool instead of the Agent tool, to find the match more quickly
+- If you are searching for a specific class definition like "class Foo", use the Glob tool instead, to find the match more quickly
+- If you are searching for code within a specific file or set of 2-3 files, use the Read tool instead of the Agent tool, to find the match more quickly
+- Other tasks that are not related to the agent descriptions above
+
+Usage notes:
+- Always include a short description (3-5 words) summarizing what the agent will do
+- Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses
+- When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.
+- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, you will be automatically notified when it completes — do NOT sleep, poll, or proactively check on its progress. Continue with other work or respond to the user instead.
+- **Foreground vs background**: Use foreground (default) when you need the agent's results before you can proceed — e.g., research agents whose findings inform your next steps. Use background when you have genuinely independent work to do in parallel.
+- Agents can be resumed using the `resume` parameter by passing the agent ID from a previous invocation. When resumed, the agent continues with its full previous context preserved. When NOT resuming, each invocation starts fresh and you should provide a detailed task description with all necessary context.
+- When the agent is done, it will return a single message back to you along with its agent ID. You can use this ID to resume the agent later if needed for follow-up work.
+- Provide clear, detailed prompts so the agent can work autonomously and return exactly the information you need.
+- Agents with "access to current context" can see the full conversation history before the tool call. When using these agents, you can write concise prompts that reference earlier context (e.g., "investigate the error discussed above") instead of repeating information. The agent will receive all prior messages and understand the context.
+- The agent's outputs should generally be trusted
+- Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since it is not aware of the user's intent
+- If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.
+- If the user specifies that they want you to run agents "in parallel", you MUST send a single message with multiple Agent tool use content blocks. For example, if you need to launch both a build-validator agent and a test-runner agent in parallel, send a single message with both tool calls.
+- You can optionally set `isolation: "worktree"` to run the agent in a temporary git worktree, giving it an isolated copy of the repository. The worktree is automatically cleaned up if the agent makes no changes; if changes are made, the worktree path and branch are returned in the result.
+
+Example usage:
+
+<example_agent_descriptions>
+"test-runner": use this agent after you are done writing code to run tests
+"greeting-responder": use this agent to respond to user greetings with a friendly joke
+</example_agent_descriptions>
+
+<example>
+user: "Please write a function that checks if a number is prime"
+assistant: Sure let me write a function that checks if a number is prime
+assistant: First let me use the Write tool to write a function that checks if a number is prime
+assistant: I'm going to use the Write tool to write the following code:
+<code>
+function isPrime(n) {
+  if (n <= 1) return false
+  for (let i = 2; i * i <= n; i++) {
+    if (n % i === 0) return false
+  }
+  return true
+}
+</code>
+<commentary>
+Since a significant piece of code was written and the task was completed, now use the test-runner agent to run the tests
+</commentary>
+assistant: Now let me use the test-runner agent to run the tests
+assistant: Uses the Agent tool to launch the test-runner agent
+</example>
+
+<example>
+user: "Hello"
+<commentary>
+Since the user is greeting, use the greeting-responder agent to respond with a friendly joke
+</commentary>
+assistant: "I'm going to use the Agent tool to launch the greeting-responder agent"
+</example>
+</textarea>

package/concepts/ko/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/ko/Tool-Bash.md

@@ -0,0 +1,167 @@
+# Bash
+
+## 정의
+
+셸 명령을 실행하며, 선택적 타임아웃 설정을 지원합니다. 작업 디렉토리는 명령 간에 유지되지만, 셸 상태 (환경 변수 등)는 유지되지 않습니다.
+
+## 파라미터
+
+| 파라미터 | 타입 | 필수 | 설명 |
+|----------|------|------|------|
+| `command` | string | 예 | 실행할 bash 명령 |
+| `description` | string | 아니오 | 명령의 간단한 설명 |
+| `timeout` | number | 아니오 | 타임아웃 (밀리초), 최대 600000, 기본값 120000 |
+| `run_in_background` | boolean | 아니오 | 백그라운드에서 실행 여부 |
+
+## 사용 시나리오
+
+**적합한 경우:**
+- git 작업 (commit, push, branch 등)
+- npm/yarn 등 패키지 관리 명령
+- docker 작업
+- 컴파일, 빌드 명령
+- 디렉토리 내용 목록 표시 (`ls`)
+- 기타 셸 실행이 필요한 시스템 명령
+
+**적합하지 않은 경우:**
+- 파일 읽기 — Read를 사용해야 함
+- 파일명 검색 — Glob를 사용해야 함
+- 파일 내용 검색 — Grep를 사용해야 함
+- 파일 편집 — Edit를 사용해야 함
+- 파일 쓰기 — Write를 사용해야 함
+- 사용자에게 정보 출력 — 응답 텍스트에 직접 출력
+- 장시간 실행 프로세스 (dev server, watch 모드) — 사용자에게 수동 실행 권장
+
+## 주의사항
+
+- 공백이 포함된 경로는 큰따옴표로 감싸야 함
+- 출력이 30000자를 초과하면 잘림
+- 백그라운드 실행 명령은 TaskOutput으로 결과 획득
+- 가능한 절대 경로를 사용하고 `cd`를 피할 것
+- 독립적인 명령은 여러 Bash를 병렬 호출 가능
+- 의존 관계가 있는 명령은 `&&`로 연결
+- 셸 환경은 사용자의 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 [Claude Code](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/ko/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` |
+
+## 사용 시나리오
+
+**적합한 경우:**
+- 기존 파일 내 특정 코드 섹션 수정
+- 버그 수정, 로직 업데이트
+- 변수 이름 변경 (`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/ko/Tool-EnterPlanMode.md

@@ -0,0 +1,128 @@
+# EnterPlanMode
+
+## 정의
+
+Claude Code를 계획 모드로 전환하여, 구현 전에 코드베이스를 탐색하고 방안을 설계하는 데 사용합니다.
+
+## 파라미터
+
+파라미터 없음.
+
+## 사용 시나리오
+
+**적합한 경우:**
+- 새 기능 구현 — 아키텍처 결정이 필요
+- 여러 실행 가능한 방안이 존재 — 사용자 선택이 필요
+- 코드 변경이 기존 동작이나 구조에 영향
+- 다중 파일 변경 — 2~3개 이상의 파일에 걸칠 가능성
+- 요구사항이 불명확 — 먼저 탐색하여 범위를 이해해야 함
+- 사용자 선호가 중요 — 구현에 여러 합리적인 방향이 있음
+
+**적합하지 않은 경우:**
+- 1줄 또는 소수 줄의 수정 (오타, 명백한 버그)
+- 사용자가 매우 구체적인 지시를 제공한 경우
+- 순수 조사/탐색 태스크 — Task (Explore 타입)를 사용해야 함
+
+## 계획 모드에서의 동작
+
+계획 모드에 진입하면 Claude Code는:
+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/ko/Tool-EnterWorktree.md

@@ -0,0 +1,56 @@
+# EnterWorktree
+
+## 정의
+
+격리된 git worktree를 생성하고 현재 세션을 해당 worktree로 전환합니다. 사용자가 명시적으로 worktree 작업을 요청할 때만 사용합니다.
+
+## 매개변수
+
+| 매개변수명 | 타입 | 필수 | 설명 |
+|---|---|---|---|
+| name | string | 아니오 | worktree 이름. 제공하지 않으면 임의의 이름이 생성됩니다. |
+
+## 사용 사례
+
+**적합한 경우:**
+- 사용자가 명시적으로 "worktree"라고 말한 경우 (예: "worktree 생성", "worktree에서 작업")
+
+**적합하지 않은 경우:**
+- 사용자가 브랜치 생성/전환을 요청 — git 명령어 사용
+- 사용자가 버그 수정이나 기능 개발을 요청 — worktree를 명시하지 않는 한 일반 git 워크플로우 사용
+
+## 참고사항
+
+- git 저장소 내에 있거나 WorktreeCreate/WorktreeRemove hooks가 구성되어 있어야 함
+- 이미 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>