cx-viewer 1.0.3 → 1.0.4

package/concepts/de/Tool-Bash.md

@@ -1,167 +0,0 @@
-# Bash
-
-## Definition
-
-Führt Shell-Befehle aus, mit optionaler Timeout-Einstellung. Das Arbeitsverzeichnis bleibt zwischen Befehlen bestehen, der Shell-Zustand (Umgebungsvariablen usw.) jedoch nicht.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `command` | string | Ja | Der auszuführende Bash-Befehl |
-| `description` | string | Nein | Kurze Beschreibung des Befehls |
-| `timeout` | number | Nein | Timeout in Millisekunden, maximal 600000, Standard 120000 |
-| `run_in_background` | boolean | Nein | Ob im Hintergrund ausgeführt werden soll |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Git-Operationen (commit, push, branch usw.)
-- npm/yarn und andere Paketverwaltungsbefehle
-- Docker-Operationen
-- Kompilierungs- und Build-Befehle
-- Verzeichnisinhalte auflisten (`ls`)
-- Andere Systembefehle, die Shell-Ausführung erfordern
-
-**Nicht geeignet für:**
-- Dateien lesen – dafür Read verwenden
-- Dateinamen suchen – dafür Glob verwenden
-- Dateiinhalte suchen – dafür Grep verwenden
-- Dateien bearbeiten – dafür Edit verwenden
-- Dateien schreiben – dafür Write verwenden
-- Informationen an den Benutzer ausgeben – direkt im Antworttext ausgeben
-- Lang laufende Prozesse (Dev-Server, Watch-Modus) – der Benutzer sollte diese manuell starten
-
-## Hinweise
-
-- Pfade mit Leerzeichen müssen in doppelte Anführungszeichen eingeschlossen werden
-- Ausgaben über 30.000 Zeichen werden abgeschnitten
-- Im Hintergrund laufende Befehle liefern Ergebnisse über TaskOutput
-- Verwenden Sie möglichst absolute Pfade und vermeiden Sie `cd`
-- Unabhängige Befehle können parallel in mehreren Bash-Aufrufen ausgeführt werden
-- Abhängige Befehle werden mit `&&` verkettet
-- Die Shell-Umgebung wird aus dem Benutzerprofil (bash oder zsh) initialisiert
-
-## Originaltext
-
-<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/de/Tool-Edit.md

@@ -1,46 +0,0 @@
-# Edit
-
-## Definition
-
-Bearbeitet Dateien durch exakte Zeichenkettenersetzung. Ersetzt `old_string` in der Datei durch `new_string`.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `file_path` | string | Ja | Absoluter Pfad der zu ändernden Datei |
-| `old_string` | string | Ja | Der zu ersetzende Originaltext |
-| `new_string` | string | Ja | Der neue Ersetzungstext (muss sich von old_string unterscheiden) |
-| `replace_all` | boolean | Nein | Ob alle Vorkommen ersetzt werden sollen, Standard `false` |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Ändern bestimmter Codeabschnitte in vorhandenen Dateien
-- Bugfixes, Logik-Updates
-- Variablen umbenennen (mit `replace_all: true`)
-- Jedes Szenario, das präzise Dateiänderungen erfordert
-
-**Nicht geeignet für:**
-- Neue Dateien erstellen – dafür Write verwenden
-- Umfangreiche Neuschreibungen – möglicherweise Write zum Überschreiben der gesamten Datei erforderlich
-
-## Hinweise
-
-- Vor der Verwendung muss die Datei über Read gelesen worden sein, sonst tritt ein Fehler auf
-- `old_string` muss in der Datei eindeutig sein, sonst schlägt die Bearbeitung fehl. Bei Nicht-Eindeutigkeit mehr Kontext angeben oder `replace_all` verwenden
-- Beim Bearbeiten von Text muss die ursprüngliche Einrückung (Tab/Leerzeichen) beibehalten werden; das Zeilennummernpräfix der Read-Ausgabe nicht einschließen
-- Vorhandene Dateien bearbeiten hat Vorrang vor dem Erstellen neuer Dateien
-- `new_string` muss sich von `old_string` unterscheiden
-
-## Originaltext
-
-<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/de/Tool-EnterPlanMode.md

@@ -1,128 +0,0 @@
-# EnterPlanMode
-
-## Definition
-
-Schaltet Claude Code in den Planungsmodus um, um vor der Implementierung die Codebasis zu erkunden und einen Plan zu entwerfen.
-
-## Parameter
-
-Keine Parameter.
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Neue Feature-Implementierung – erfordert Architekturentscheidungen
-- Mehrere mögliche Ansätze – Benutzerauswahl erforderlich
-- Codeänderungen beeinflussen bestehendes Verhalten oder Struktur
-- Änderungen an mehreren Dateien – möglicherweise 2–3 oder mehr Dateien betroffen
-- Unklare Anforderungen – erst erkunden, dann Umfang verstehen
-- Benutzerpräferenzen sind wichtig – die Implementierung kann mehrere sinnvolle Richtungen haben
-
-**Nicht geeignet für:**
-- Einzeilige oder wenige Zeilen umfassende Korrekturen (Tippfehler, offensichtliche Bugs)
-- Der Benutzer hat sehr spezifische Anweisungen gegeben
-- Reine Recherche-/Erkundungsaufgaben – dafür Task (Explore-Typ) verwenden
-
-## Verhalten im Planungsmodus
-
-Nach dem Eintritt in den Planungsmodus wird Claude Code:
-1. Mit Glob, Grep, Read Tools die Codebasis eingehend erkunden
-2. Bestehende Muster und Architektur verstehen
-3. Einen Implementierungsplan entwerfen
-4. Den Plan dem Benutzer zur Genehmigung vorlegen
-5. Bei Bedarf AskUserQuestion zur Klärung verwenden
-6. Nach Fertigstellung des Plans über ExitPlanMode den Modus verlassen
-
-## Hinweise
-
-- Dieses Tool erfordert die Zustimmung des Benutzers zum Eintritt in den Planungsmodus
-- Im Zweifelsfall lieber planen – frühzeitige Abstimmung ist besser als Nacharbeit
-
-## Originaltext
-
-<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/de/Tool-EnterWorktree.md

@@ -1,56 +0,0 @@
-# EnterWorktree
-
-## Definition
-
-Creates an isolated git worktree and switches the current session into it. Only used when the user explicitly asks to work in a worktree.
-
-## Parameter
-
-| Name | Type | Required | Description |
-|---|---|---|---|
-| name | string | No | A name for the worktree. If not provided, a random name is generated. |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- The user explicitly says "worktree" (e.g., "start a worktree", "work in a worktree", "create a worktree")
-
-**Nicht geeignet für:**
-- 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
-
-## Hinweise
-
-- Must be in a git repository, or have WorktreeCreate/WorktreeRemove hooks configured
-- Must not already be in a worktree
-
-## Originaltext
-
-<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/de/Tool-ExitPlanMode.md

@@ -1,62 +0,0 @@
-# ExitPlanMode
-
-## Definition
-
-Verlässt den Planungsmodus und reicht den Plan zur Benutzerfreigabe ein. Der Planinhalt wird aus der zuvor geschriebenen Plandatei gelesen.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `allowedPrompts` | array | Nein | Liste der für die Planumsetzung benötigten Berechtigungsbeschreibungen |
-
-Jedes Element im `allowedPrompts`-Array:
-
-| Feld | Typ | Erforderlich | Beschreibung |
-|------|-----|--------------|--------------|
-| `tool` | enum | Ja | Das zutreffende Tool, derzeit nur `Bash` unterstützt |
-| `prompt` | string | Ja | Semantische Beschreibung der Operation (z.B. "run tests", "install dependencies") |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Der Plan im Planungsmodus ist fertig und bereit zur Benutzerfreigabe
-- Nur für Implementierungsaufgaben, die Code schreiben erfordern
-
-**Nicht geeignet für:**
-- Reine Recherche-/Erkundungsaufgaben – kein Verlassen des Planungsmodus nötig
-- Den Benutzer fragen „Ist der Plan in Ordnung?" – genau das ist die Funktion dieses Tools, verwenden Sie nicht AskUserQuestion dafür
-
-## Hinweise
-
-- Dieses Tool akzeptiert keinen Planinhalt als Parameter – es liest aus der zuvor geschriebenen Plandatei
-- Der Benutzer sieht den Inhalt der Plandatei zur Genehmigung
-- Verwenden Sie nicht AskUserQuestion vor dem Aufruf dieses Tools, um zu fragen „Ist der Plan in Ordnung?" – das wäre redundant
-- Erwähnen Sie den „Plan" nicht in Fragen, da der Benutzer den Planinhalt vor ExitPlanMode nicht sehen kann
-
-## Originaltext
-
-<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/de/Tool-Glob.md

@@ -1,39 +0,0 @@
-# Glob
-
-## Definition
-
-Schnelles Dateinamen-Musterabgleich-Tool, das mit Codebasen jeder Größe funktioniert. Gibt übereinstimmende Dateipfade sortiert nach Änderungszeit zurück.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `pattern` | string | Ja | Glob-Muster (z.B. `**/*.js`, `src/**/*.ts`) |
-| `path` | string | Nein | Suchverzeichnis, Standard ist das aktuelle Arbeitsverzeichnis. Nicht "undefined" oder "null" übergeben |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Dateien nach Dateinamenmuster suchen
-- Alle Dateien eines bestimmten Typs finden (z.B. alle `.tsx`-Dateien)
-- Beim Suchen einer bestimmten Klassendefinition (z.B. `class Foo`) zuerst die Datei lokalisieren
-- Mehrere Glob-Aufrufe können in einer einzelnen Nachricht parallel gestartet werden
-
-**Nicht geeignet für:**
-- Dateiinhalte durchsuchen – dafür Grep verwenden
-- Offene Erkundung mit mehreren Suchrunden – dafür Task (Explore-Typ) verwenden
-
-## Hinweise
-
-- Unterstützt Standard-Glob-Syntax: `*` matcht eine Ebene, `**` matcht mehrere Ebenen, `{}` matcht Alternativen
-- Ergebnisse sind nach Änderungszeit sortiert
-- Wird gegenüber dem `find`-Befehl in Bash bevorzugt
-
-## Originaltext
-
-<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/de/Tool-Grep.md

@@ -1,57 +0,0 @@
-# Grep
-
-## Definition
-
-Leistungsstarkes Inhaltssuchtool basierend auf ripgrep. Unterstützt reguläre Ausdrücke, Dateitypfilterung und mehrere Ausgabemodi.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `pattern` | string | Ja | Reguläres Ausdruckssuchmuster |
-| `path` | string | Nein | Suchpfad (Datei oder Verzeichnis), Standard ist das aktuelle Arbeitsverzeichnis |
-| `glob` | string | Nein | Dateinamenfilter (z.B. `*.js`, `*.{ts,tsx}`) |
-| `type` | string | Nein | Dateitypfilter (z.B. `js`, `py`, `rust`), effizienter als glob |
-| `output_mode` | enum | Nein | Ausgabemodus: `files_with_matches` (Standard), `content`, `count` |
-| `-i` | boolean | Nein | Groß-/Kleinschreibung ignorieren |
-| `-n` | boolean | Nein | Zeilennummern anzeigen (nur content-Modus), Standard true |
-| `-A` | number | Nein | Anzahl der Zeilen nach dem Treffer |
-| `-B` | number | Nein | Anzahl der Zeilen vor dem Treffer |
-| `-C` / `context` | number | Nein | Anzahl der Zeilen vor und nach dem Treffer |
-| `head_limit` | number | Nein | Ausgabeeinträge begrenzen, Standard 0 (unbegrenzt) |
-| `offset` | number | Nein | Erste N Ergebnisse überspringen |
-| `multiline` | boolean | Nein | Mehrzeiligen Abgleichmodus aktivieren, Standard false |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Bestimmte Zeichenketten oder Muster in der Codebasis suchen
-- Verwendungsstellen von Funktionen/Variablen finden
-- Suchergebnisse nach Dateityp filtern
-- Trefferanzahl zählen
-
-**Nicht geeignet für:**
-- Dateien nach Dateinamen suchen – dafür Glob verwenden
-- Offene Erkundung mit mehreren Suchrunden – dafür Task (Explore-Typ) verwenden
-
-## Hinweise
-
-- Verwendet ripgrep-Syntax (nicht grep), geschweifte Klammern und andere Sonderzeichen müssen escaped werden
-- `files_with_matches`-Modus gibt nur Dateipfade zurück, am effizientesten
-- `content`-Modus gibt übereinstimmende Zeileninhalte zurück, unterstützt Kontextzeilen
-- Mehrzeiliger Abgleich erfordert `multiline: true`
-- Immer das Grep-Tool gegenüber `grep` oder `rg` in Bash bevorzugen
-
-## Originaltext
-
-<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>

package/concepts/de/Tool-NotebookEdit.md

@@ -1,33 +0,0 @@
-# NotebookEdit
-
-## Definition
-
-Ersetzt, fügt ein oder löscht bestimmte Zellen in einem Jupyter Notebook (.ipynb-Datei).
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `notebook_path` | string | Ja | Absoluter Pfad der Notebook-Datei |
-| `new_source` | string | Ja | Neuer Inhalt der Zelle |
-| `cell_id` | string | Nein | ID der zu bearbeitenden Zelle. Im Einfügemodus wird die neue Zelle nach dieser ID eingefügt |
-| `cell_type` | enum | Nein | Zellentyp: `code` oder `markdown`. Im Einfügemodus erforderlich |
-| `edit_mode` | enum | Nein | Bearbeitungsmodus: `replace` (Standard), `insert`, `delete` |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Code- oder Markdown-Zellen in Jupyter Notebooks ändern
-- Neue Zellen zum Notebook hinzufügen
-- Zellen aus dem Notebook löschen
-
-## Hinweise
-
-- `cell_number` ist 0-indiziert
-- `insert`-Modus fügt eine neue Zelle an der angegebenen Position ein
-- `delete`-Modus löscht die Zelle an der angegebenen Position
-- Der Pfad muss ein absoluter Pfad sein
-
-## Originaltext
-
-<textarea readonly>Completely replaces the contents of a specific cell in a Jupyter notebook (.ipynb file) with new source. Jupyter notebooks are interactive documents that combine code, text, and visualizations, commonly used for data analysis and scientific computing. The notebook_path parameter must be an absolute path, not a relative path. The cell_number is 0-indexed. Use edit_mode=insert to add a new cell at the index specified by cell_number. Use edit_mode=delete to delete the cell at the index specified by cell_number.</textarea>

package/concepts/de/Tool-Read.md

@@ -1,56 +0,0 @@
-# Read
-
-## Definition
-
-Liest Dateiinhalte aus dem lokalen Dateisystem. Unterstützt Textdateien, Bilder, PDF und Jupyter Notebooks.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `file_path` | string | Ja | Absoluter Pfad der Datei |
-| `offset` | number | Nein | Startzeilennummer (für abschnittsweises Lesen großer Dateien) |
-| `limit` | number | Nein | Anzahl zu lesender Zeilen (für abschnittsweises Lesen großer Dateien) |
-| `pages` | string | Nein | PDF-Seitenbereich (z.B. "1-5", "3", "10-20"), nur für PDF |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Codedateien, Konfigurationsdateien und andere Textdateien lesen
-- Bilddateien anzeigen (Claude ist ein multimodales Modell)
-- PDF-Dokumente lesen
-- Jupyter Notebooks lesen (gibt alle Zellen mit Ausgaben zurück)
-- Mehrere Dateien parallel lesen, um Kontext zu erhalten
-
-**Nicht geeignet für:**
-- Verzeichnisse lesen – dafür den `ls`-Befehl in Bash verwenden
-- Offene Codebasis-Erkundung – dafür Task (Explore-Typ) verwenden
-
-## Hinweise
-
-- Der Pfad muss ein absoluter Pfad sein, kein relativer Pfad
-- Standardmäßig werden die ersten 2000 Zeilen der Datei gelesen
-- Zeilen mit mehr als 2000 Zeichen werden abgeschnitten
-- Die Ausgabe verwendet das `cat -n`-Format, Zeilennummern beginnen bei 1
-- Große PDFs (über 10 Seiten) erfordern den `pages`-Parameter, maximal 20 Seiten pro Aufruf
-- Das Lesen einer nicht existierenden Datei gibt einen Fehler zurück (kein Absturz)
-- Mehrere Read-Aufrufe können in einer einzelnen Nachricht parallel ausgeführt werden
-
-## Originaltext
-
-<textarea readonly>Reads a file from the local filesystem. You can access any file directly by using this tool.
-Assume this tool is able to read all files on the machine. If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.
-
-Usage:
-- The file_path parameter must be an absolute path, not a relative path
-- By default, it reads up to 2000 lines starting from the beginning of the file
-- You can optionally specify a line offset and limit (especially handy for long files), but it's recommended to read the whole file by not providing these parameters
-- Any lines longer than 2000 characters will be truncated
-- Results are returned using cat -n format, with line numbers starting at 1
-- This tool allows Claude Code to read images (eg PNG, JPG, etc). When reading an image file the contents are presented visually as Claude Code is a multimodal LLM.
-- This tool can read PDF files (.pdf). For large PDFs (more than 10 pages), you MUST provide the pages parameter to read specific page ranges (e.g., pages: "1-5"). Reading a large PDF without the pages parameter will fail. Maximum 20 pages per request.
-- This tool can read Jupyter notebooks (.ipynb files) and returns all cells with their outputs, combining code, text, and visualizations.
-- This tool can only read files, not directories. To read a directory, use an ls command via the Bash tool.
-- You can call multiple tools in a single response. It is always better to speculatively read multiple potentially useful files in parallel.
-- You will regularly be asked to read screenshots. If the user provides a path to a screenshot, ALWAYS use this tool to view the file at the path. This tool will work with all temporary file paths.
-- If you read a file that exists but has empty contents you will receive a system reminder warning in place of file contents.</textarea>