cx-viewer 1.0.0

package/concepts/es/Tool-Agent.md

@@ -0,0 +1,125 @@
+# Agent
+
+## Definición
+
+Inicia un sub-agent (SubAgent) para manejar de forma autónoma tareas complejas de múltiples pasos. Los sub-agents son subprocesos independientes, cada uno con su propio conjunto de herramientas y contexto dedicados. Agent es la versión renombrada de la herramienta Task en las versiones más recientes de Claude Code.
+
+## Parámetros
+
+| Parámetro | Tipo | Requerido | Descripción |
+|-----------|------|-----------|-------------|
+| `prompt` | string | Sí | Descripción de la tarea a ejecutar por el sub-agent |
+| `description` | string | Sí | Resumen breve de 3-5 palabras |
+| `subagent_type` | string | Sí | Tipo de sub-agent, determina el conjunto de herramientas disponibles |
+| `model` | enum | No | Especificar modelo (sonnet / opus / haiku), por defecto hereda del padre |
+| `max_turns` | integer | No | Número máximo de turnos agénticos |
+| `run_in_background` | boolean | No | Si se ejecuta en segundo plano; las tareas en segundo plano devuelven la ruta del output_file |
+| `resume` | string | No | ID del agent a reanudar, continúa desde la última ejecución. Útil para retomar un sub-agent anterior sin perder el contexto |
+| `isolation` | enum | No | Modo de aislamiento, `worktree` crea un git worktree temporal |
+
+## Tipos de sub-agent
+
+| Tipo | Propósito | Herramientas disponibles |
+|------|-----------|--------------------------|
+| `Bash` | Ejecución de comandos, operaciones git | Bash |
+| `general-purpose` | Tareas generales de múltiples pasos | Todas las herramientas |
+| `Explore` | Exploración rápida de la base de código | Todas las herramientas excepto Agent/Edit/Write/NotebookEdit/ExitPlanMode |
+| `Plan` | Diseñar planes de implementación | Todas las herramientas excepto Agent/Edit/Write/NotebookEdit/ExitPlanMode |
+| `claude-code-guide` | Preguntas y respuestas sobre la guía de uso de Claude Code | Glob, Grep, Read, WebFetch, WebSearch |
+| `statusline-setup` | Configurar la barra de estado | Read, Edit |
+
+## Casos de uso
+
+**Adecuado para:**
+- Tareas complejas que requieren completarse de forma autónoma en múltiples pasos
+- Exploración de la base de código e investigación profunda (usar tipo Explore)
+- Trabajo paralelo que necesita entornos aislados
+- Tareas de larga duración que necesitan ejecutarse en segundo plano
+
+**No adecuado para:**
+- Leer rutas de archivos específicas — usar directamente Read o Glob
+- Buscar en 2-3 archivos conocidos — usar directamente Read
+- Buscar definiciones de clases específicas — usar directamente Glob
+
+## Notas
+
+- El sub-agent devuelve un solo mensaje al completarse, sus resultados no son visibles para el usuario y el agent principal necesita transmitirlos
+- Se pueden lanzar múltiples llamadas Agent en paralelo en un solo mensaje para mejorar la eficiencia
+- Las tareas en segundo plano verifican el progreso mediante la herramienta TaskOutput
+- El tipo Explore es más lento que llamar directamente a Glob/Grep, usar solo cuando la búsqueda simple no es suficiente
+- Use `run_in_background: true` para tareas de larga duración que no necesitan resultados inmediatos; use el modo en primer plano (predeterminado) cuando se necesita el resultado antes de continuar
+- El parámetro `resume` permite continuar una sesión de sub-agent iniciada previamente, preservando el contexto acumulado
+
+## Texto original
+
+<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/es/Tool-AskUserQuestion.md

@@ -0,0 +1,75 @@
+# AskUserQuestion
+
+## Definición
+
+Hace preguntas al usuario durante la ejecución para obtener aclaraciones, verificar suposiciones o solicitar decisiones.
+
+## Parámetros
+
+| Parámetro | Tipo | Requerido | Descripción |
+|-----------|------|-----------|-------------|
+| `questions` | array | Sí | Lista de preguntas (1-4 preguntas) |
+| `answers` | object | No | Respuestas recopiladas del usuario |
+| `annotations` | object | No | Anotaciones para cada pregunta (como notas de vista previa de selección) |
+| `metadata` | object | No | Metadatos para seguimiento y análisis |
+
+Cada objeto `question`:
+
+| Campo | Tipo | Requerido | Descripción |
+|-------|------|-----------|-------------|
+| `question` | string | Sí | Texto completo de la pregunta, debe terminar con signo de interrogación |
+| `header` | string | Sí | Etiqueta corta (máximo 12 caracteres), se muestra como chip de etiqueta |
+| `options` | array | Sí | 2-4 opciones |
+| `multiSelect` | boolean | Sí | Si se permite selección múltiple |
+
+Cada objeto `option`:
+
+| Campo | Tipo | Requerido | Descripción |
+|-------|------|-----------|-------------|
+| `label` | string | Sí | Texto de visualización de la opción (1-5 palabras) |
+| `description` | string | Sí | Descripción de la opción |
+| `markdown` | string | No | Contenido de vista previa (para comparación visual de diseños ASCII, fragmentos de código, etc.) |
+
+## Casos de uso
+
+**Adecuado para:**
+- Recopilar preferencias o requisitos del usuario
+- Aclarar instrucciones ambiguas
+- Obtener decisiones durante la implementación
+- Ofrecer opciones de dirección al usuario
+
+**No adecuado para:**
+- Preguntar "¿está bien el plan?" — se debe usar ExitPlanMode
+
+## Notas
+
+- El usuario siempre puede seleccionar "Other" para proporcionar una entrada personalizada
+- La opción recomendada se coloca en primer lugar, con "(Recommended)" al final del label
+- La vista previa `markdown` solo es compatible con preguntas de selección única
+- Las opciones con `markdown` cambian a un diseño lado a lado
+- En modo de planificación, se usa para aclarar requisitos antes de definir el plan
+
+## Texto original
+
+<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/es/Tool-Bash.md

@@ -0,0 +1,167 @@
+# Bash
+
+## Definición
+
+Ejecuta comandos shell con configuración de tiempo de espera opcional. El directorio de trabajo persiste entre comandos, pero el estado del shell (variables de entorno, etc.) no persiste.
+
+## Parámetros
+
+| Parámetro | Tipo | Requerido | Descripción |
+|-----------|------|-----------|-------------|
+| `command` | string | Sí | Comando bash a ejecutar |
+| `description` | string | No | Descripción breve del comando |
+| `timeout` | number | No | Tiempo de espera (milisegundos), máximo 600000, por defecto 120000 |
+| `run_in_background` | boolean | No | Si se ejecuta en segundo plano |
+
+## Casos de uso
+
+**Adecuado para:**
+- Operaciones git (commit, push, branch, etc.)
+- Comandos de gestión de paquetes npm/yarn
+- Operaciones docker
+- Comandos de compilación y construcción
+- Listar contenido de directorios (`ls`)
+- Otros comandos del sistema que requieren ejecución en shell
+
+**No adecuado para:**
+- Leer archivos — usar Read
+- Buscar nombres de archivos — usar Glob
+- Buscar contenido de archivos — usar Grep
+- Editar archivos — usar Edit
+- Escribir archivos — usar Write
+- Mostrar información al usuario — mostrar directamente en el texto de respuesta
+- Procesos de larga duración (dev server, modo watch) — recomendar al usuario ejecutar manualmente
+
+## Notas
+
+- Las rutas con espacios deben estar entre comillas dobles
+- La salida que exceda 30000 caracteres será truncada
+- Los comandos en segundo plano obtienen resultados mediante TaskOutput
+- Usar preferentemente rutas absolutas, evitar `cd`
+- Los comandos independientes pueden ejecutar múltiples Bash en paralelo
+- Los comandos con dependencias se encadenan con `&&`
+- El entorno shell se inicializa desde el profile del usuario (bash o zsh)
+
+## Texto original
+
+<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/es/Tool-Edit.md

@@ -0,0 +1,46 @@
+# Edit
+
+## Definición
+
+Edita archivos mediante reemplazo exacto de cadenas. Reemplaza `old_string` por `new_string` en el archivo.
+
+## Parámetros
+
+| Parámetro | Tipo | Requerido | Descripción |
+|-----------|------|-----------|-------------|
+| `file_path` | string | Sí | Ruta absoluta del archivo a modificar |
+| `old_string` | string | Sí | Texto original a reemplazar |
+| `new_string` | string | Sí | Nuevo texto de reemplazo (debe ser diferente de old_string) |
+| `replace_all` | boolean | No | Si se reemplazan todas las coincidencias, por defecto `false` |
+
+## Casos de uso
+
+**Adecuado para:**
+- Modificar segmentos específicos de código en archivos existentes
+- Corregir bugs, actualizar lógica
+- Renombrar variables (con `replace_all: true`)
+- Cualquier escenario que requiera modificación precisa del contenido de un archivo
+
+**No adecuado para:**
+- Crear archivos nuevos — usar Write
+- Reescrituras a gran escala — puede requerir Write para sobrescribir el archivo completo
+
+## Notas
+
+- Se debe haber leído el archivo previamente con Read antes de usar, de lo contrario dará error
+- `old_string` debe ser único en el archivo, de lo contrario la edición falla. Si no es único, proporcionar más contexto para hacerlo único, o usar `replace_all`
+- Al editar texto se debe mantener la indentación original (tab/espacios), no incluir el prefijo de número de línea de la salida de Read
+- Preferir editar archivos existentes en lugar de crear nuevos
+- `new_string` debe ser diferente de `old_string`
+
+## Texto original
+
+<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/es/Tool-EnterPlanMode.md

@@ -0,0 +1,128 @@
+# EnterPlanMode
+
+## Definición
+
+Cambia Claude Code al modo de planificación, utilizado para explorar la base de código y diseñar un plan antes de la implementación.
+
+## Parámetros
+
+Sin parámetros.
+
+## Casos de uso
+
+**Adecuado para:**
+- Implementación de nuevas funcionalidades — requiere decisiones de arquitectura
+- Existen múltiples enfoques viables — requiere que el usuario elija
+- Las modificaciones de código afectan el comportamiento o la estructura existente
+- Cambios en múltiples archivos — posiblemente involucra 2-3 o más archivos
+- Requisitos poco claros — necesita explorar primero para entender el alcance
+- Las preferencias del usuario son importantes — la implementación puede tener múltiples direcciones razonables
+
+**No adecuado para:**
+- Correcciones de una línea o pocas líneas (errores tipográficos, bugs obvios)
+- El usuario ya dio instrucciones muy específicas
+- Tareas puramente de investigación/exploración — usar Task (tipo Explore)
+
+## Comportamiento en modo de planificación
+
+Después de entrar en modo de planificación, Claude Code:
+1. Usa las herramientas Glob, Grep, Read para explorar la base de código en profundidad
+2. Comprende los patrones y la arquitectura existentes
+3. Diseña un plan de implementación
+4. Envía el plan al usuario para aprobación
+5. Puede usar AskUserQuestion si necesita aclaraciones
+6. Sale mediante ExitPlanMode cuando el plan está listo
+
+## Notas
+
+- Esta herramienta requiere el consentimiento del usuario para entrar en modo de planificación
+- Si no está seguro de si se necesita planificación, es preferible planificar — alinear de antemano es mejor que rehacer
+
+## Texto original
+
+<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/es/Tool-EnterWorktree.md

@@ -0,0 +1,56 @@
+# EnterWorktree
+
+## Definición
+
+Creates an isolated git worktree and switches the current session into it. Only used when the user explicitly asks to work in a worktree.
+
+## Parámetros
+
+| Name | Type | Required | Description |
+|---|---|---|---|
+| name | string | No | A name for the worktree. If not provided, a random name is generated. |
+
+## Casos de uso
+
+**Adecuado para:**
+- The user explicitly says "worktree" (e.g., "start a worktree", "work in a worktree", "create a worktree")
+
+**No adecuado para:**
+- 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
+
+## Notas
+
+- Must be in a git repository, or have WorktreeCreate/WorktreeRemove hooks configured
+- Must not already be in a worktree
+
+## Texto original
+
+<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>