cx-viewer 1.0.3 → 1.0.4

package/concepts/da/Tool-AskUserQuestion.md

@@ -1,75 +0,0 @@
-# AskUserQuestion
-
-## Definition
-
-Stiller spørgsmål til brugeren under udførelsen for at få afklaring, verificere antagelser eller anmode om beslutninger.
-
-## Parametre
-
-| Parameter | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `questions` | array | Ja | Liste af spørgsmål (1-4 spørgsmål) |
-| `answers` | object | Nej | Svar indsamlet fra brugeren |
-| `annotations` | object | Nej | Annotationer for hvert spørgsmål (f.eks. noter til forhåndsvisning af valg) |
-| `metadata` | object | Nej | Metadata til sporing og analyse |
-
-Hvert `question`-objekt:
-
-| Felt | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `question` | string | Ja | Komplet spørgsmålstekst, skal slutte med spørgsmålstegn |
-| `header` | string | Ja | Kort label (maks. 12 tegn), vises som label-chip |
-| `options` | array | Ja | 2-4 valgmuligheder |
-| `multiSelect` | boolean | Ja | Om flervalg er tilladt |
-
-Hvert `option`-objekt:
-
-| Felt | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `label` | string | Ja | Visningstekst for valgmuligheden (1-5 ord) |
-| `description` | string | Ja | Beskrivelse af valgmuligheden |
-| `markdown` | string | Nej | Forhåndsvisningsindhold (til visuel sammenligning af ASCII-layout, kodestykker osv.) |
-
-## Brugsscenarier
-
-**Egnet til:**
-- Indsamling af brugerpræferencer eller krav
-- Afklaring af tvetydige instruktioner
-- Indhentning af beslutninger under implementering
-- Give brugeren retningsvalg
-
-**Ikke egnet til:**
-- At spørge "er planen OK?" — brug ExitPlanMode
-
-## Bemærkninger
-
-- Brugeren kan altid vælge "Other" for at give brugerdefineret input
-- Den anbefalede valgmulighed placeres først med "(Recommended)" i slutningen af label
-- `markdown`-forhåndsvisning understøttes kun for enkeltvalgs-spørgsmål
-- Valgmuligheder med `markdown` skifter til side-om-side-layout
-- I planlægningstilstand bruges det til at afklare krav, før planen fastlægges
-
-## Originaltekst
-
-<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/da/Tool-Bash.md

@@ -1,167 +0,0 @@
-# Bash
-
-## Definition
-
-Udfører shell-kommandoer med valgfri timeout-indstilling. Arbejdsmappen bevares mellem kommandoer, men shell-tilstanden (miljøvariabler osv.) bevares ikke.
-
-## Parametre
-
-| Parameter | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `command` | string | Ja | Bash-kommandoen der skal udføres |
-| `description` | string | Nej | Kort beskrivelse af kommandoen |
-| `timeout` | number | Nej | Timeout i millisekunder, maks. 600000, standard 120000 |
-| `run_in_background` | boolean | Nej | Om den skal køre i baggrunden |
-
-## Brugsscenarier
-
-**Egnet til:**
-- Git-operationer (commit, push, branch osv.)
-- npm/yarn og andre pakkehåndteringskommandoer
-- Docker-operationer
-- Kompilerings- og build-kommandoer
-- Liste mappeindhold (`ls`)
-- Andre systemkommandoer der kræver shell-udførelse
-
-**Ikke egnet til:**
-- Læse filer — brug Read
-- Søge filnavne — brug Glob
-- Søge filindhold — brug Grep
-- Redigere filer — brug Edit
-- Skrive filer — brug Write
-- Vise information til brugeren — skriv direkte i svarteksten
-- Langvarige processer (dev server, watch-tilstand) — anbefal brugeren at køre dem manuelt
-
-## Bemærkninger
-
-- Stier med mellemrum skal omsluttes af dobbelte anførselstegn
-- Output over 30000 tegn afkortes
-- Baggrundskommandoer henter resultater via TaskOutput
-- Brug helst absolutte stier, undgå `cd`
-- Uafhængige kommandoer kan kaldes parallelt med flere Bash
-- Kommandoer med afhængigheder kædes sammen med `&&`
-- Shell-miljøet initialiseres fra brugerens profil (bash eller zsh)
-
-## Originaltekst
-
-<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/da/Tool-Edit.md

@@ -1,46 +0,0 @@
-# Edit
-
-## Definition
-
-Redigerer filer via præcis strengerstatning. Erstatter `old_string` med `new_string` i filen.
-
-## Parametre
-
-| Parameter | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `file_path` | string | Ja | Absolut sti til filen der skal ændres |
-| `old_string` | string | Ja | Originaltekst der skal erstattes |
-| `new_string` | string | Ja | Ny erstatningstekst (skal være forskellig fra old_string) |
-| `replace_all` | boolean | Nej | Om alle forekomster skal erstattes, standard `false` |
-
-## Brugsscenarier
-
-**Egnet til:**
-- Ændre specifikke kodeafsnit i eksisterende filer
-- Rette fejl, opdatere logik
-- Omdøbe variabler (med `replace_all: true`)
-- Ethvert scenarie der kræver præcis ændring af filindhold
-
-**Ikke egnet til:**
-- Oprette nye filer — brug Write
-- Omfattende omskrivninger — kan kræve Write til at overskrive hele filen
-
-## Bemærkninger
-
-- Filen skal først være læst via Read, ellers opstår en fejl
-- `old_string` skal være unik i filen, ellers fejler redigeringen. Hvis den ikke er unik, angiv mere kontekst for at gøre den unik, eller brug `replace_all`
-- Ved redigering af tekst skal den originale indrykning (tab/mellemrum) bevares; medtag ikke linjenummerpræfikset fra Read-output
-- Foretræk redigering af eksisterende filer frem for at oprette nye
-- `new_string` skal være forskellig fra `old_string`
-
-## Originaltekst
-
-<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/da/Tool-EnterPlanMode.md

@@ -1,128 +0,0 @@
-# EnterPlanMode
-
-## Definition
-
-Skifter Claude Code til planlægningstilstand, der bruges til at udforske kodebasen og designe en plan før implementering.
-
-## Parametre
-
-Ingen parametre.
-
-## Brugsscenarier
-
-**Egnet til:**
-- Implementering af nye funktioner — kræver arkitekturbeslutninger
-- Der findes flere mulige tilgange — kræver brugerens valg
-- Kodeændringer påvirker eksisterende adfærd eller struktur
-- Ændringer i flere filer — involverer potentielt 2-3 eller flere filer
-- Uklare krav — nødvendigt at udforske først for at forstå omfanget
-- Brugerpræferencer er vigtige — implementeringen kan have flere rimelige retninger
-
-**Ikke egnet til:**
-- Rettelser af én eller få linjer (stavefejl, åbenlyse fejl)
-- Brugeren har givet meget specifikke instruktioner
-- Rene forsknings-/udforskningsopgaver — brug Task (Explore-type)
-
-## Adfærd i planlægningstilstand
-
-Efter at være gået ind i planlægningstilstand vil Claude Code:
-1. Bruge Glob-, Grep-, Read-værktøjer til at udforske kodebasen i dybden
-2. Forstå eksisterende mønstre og arkitektur
-3. Designe implementeringsplanen
-4. Indsende planen til brugerens godkendelse
-5. Bruge AskUserQuestion til afklaring om nødvendigt
-6. Forlade tilstanden via ExitPlanMode, når planen er klar
-
-## Bemærkninger
-
-- Dette værktøj kræver brugerens samtykke for at gå ind i planlægningstilstand
-- Hvis du er i tvivl om, hvorvidt planlægning er nødvendig, foretrækkes planlægning — at afstemme på forhånd er bedre end at lave om
-
-## Originaltekst
-
-<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/da/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.
-
-## Parametre
-
-| Name | Type | Required | Description |
-|---|---|---|---|
-| name | string | No | A name for the worktree. If not provided, a random name is generated. |
-
-## Anvendelsestilfælde
-
-**Egnet til:**
-- The user explicitly says "worktree" (e.g., "start a worktree", "work in a worktree", "create a worktree")
-
-**Ikke egnet til:**
-- 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
-
-## Bemærkninger
-
-- Must be in a git repository, or have WorktreeCreate/WorktreeRemove hooks configured
-- Must not already be in a worktree
-
-## Originaltekst
-
-<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/da/Tool-ExitPlanMode.md

@@ -1,62 +0,0 @@
-# ExitPlanMode
-
-## Definition
-
-Forlader planlægningstilstand og indsender planen til brugerens godkendelse. Planens indhold læses fra den tidligere skrevne planfil.
-
-## Parametre
-
-| Parameter | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `allowedPrompts` | array | Nej | Liste over tilladelsebeskrivelser nødvendige for at implementere planen |
-
-Hvert element i `allowedPrompts`-arrayet:
-
-| Felt | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `tool` | enum | Ja | Det gældende værktøj, understøtter i øjeblikket kun `Bash` |
-| `prompt` | string | Ja | Semantisk beskrivelse af operationen (f.eks. "run tests", "install dependencies") |
-
-## Brugsscenarier
-
-**Egnet til:**
-- I planlægningstilstand er planen færdig og klar til brugerens godkendelse
-- Kun til implementeringsopgaver der kræver kodeskrivning
-
-**Ikke egnet til:**
-- Rene forsknings-/udforskningsopgaver — det er ikke nødvendigt at forlade planlægningstilstand
-- At ville spørge brugeren "er planen OK?" — det er præcis dette værktøjs funktion, brug ikke AskUserQuestion til at spørge
-
-## Bemærkninger
-
-- Dette værktøj accepterer ikke planindhold som parameter — det læser fra den tidligere skrevne planfil
-- Brugeren vil se planfilens indhold til godkendelse
-- Brug ikke AskUserQuestion til at spørge "er planen OK?" før du kalder dette værktøj, det er overflødigt
-- Nævn ikke "planen" i spørgsmål, da brugeren ikke kan se planindholdet før ExitPlanMode
-
-## Originaltekst
-
-<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/da/Tool-Glob.md

@@ -1,39 +0,0 @@
-# Glob
-
-## Definition
-
-Hurtigt filnavnsmønster-matchningsværktøj, der understøtter kodebaser af enhver størrelse. Returnerer matchende filstier sorteret efter ændringstidspunkt.
-
-## Parametre
-
-| Parameter | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `pattern` | string | Ja | Glob-mønster (f.eks. `**/*.js`, `src/**/*.ts`) |
-| `path` | string | Nej | Søgemappe, standard er den aktuelle arbejdsmappe. Send ikke "undefined" eller "null" |
-
-## Brugsscenarier
-
-**Egnet til:**
-- Søge filer efter filnavnsmønster
-- Finde alle filer af en bestemt type (f.eks. alle `.tsx`-filer)
-- Lokalisere filer når man søger efter en bestemt klassedefinition (f.eks. `class Foo`)
-- Man kan starte flere Glob-kald parallelt i en enkelt besked
-
-**Ikke egnet til:**
-- Søge filindhold — brug Grep
-- Åben udforskning der kræver flere søgerunder — brug Task (Explore-type)
-
-## Bemærkninger
-
-- Understøtter standard glob-syntaks: `*` matcher ét niveau, `**` matcher flere niveauer, `{}` matcher flervalg
-- Resultater sorteres efter ændringstidspunkt
-- Mere anbefalet end Bashs `find`-kommando
-
-## Originaltekst
-
-<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/da/Tool-Grep.md

@@ -1,57 +0,0 @@
-# Grep
-
-## Definition
-
-Kraftfuldt indholdssøgningsværktøj baseret på ripgrep. Understøtter regulære udtryk, filtypefiltring og flere outputtilstande.
-
-## Parametre
-
-| Parameter | Type | Påkrævet | Beskrivelse |
-|------|------|------|------|
-| `pattern` | string | Ja | Søgemønster med regulært udtryk |
-| `path` | string | Nej | Søgesti (fil eller mappe), standard er den aktuelle arbejdsmappe |
-| `glob` | string | Nej | Filnavnsfilter (f.eks. `*.js`, `*.{ts,tsx}`) |
-| `type` | string | Nej | Filtypefilter (f.eks. `js`, `py`, `rust`), mere effektivt end glob |
-| `output_mode` | enum | Nej | Outputtilstand: `files_with_matches` (standard), `content`, `count` |
-| `-i` | boolean | Nej | Søgning uden forskel på store/små bogstaver |
-| `-n` | boolean | Nej | Vis linjenumre (kun content-tilstand), standard true |
-| `-A` | number | Nej | Antal linjer der vises efter match |
-| `-B` | number | Nej | Antal linjer der vises før match |
-| `-C` / `context` | number | Nej | Antal linjer der vises før og efter match |
-| `head_limit` | number | Nej | Begræns antal outputposter, standard 0 (ubegrænset) |
-| `offset` | number | Nej | Spring de første N resultater over |
-| `multiline` | boolean | Nej | Aktiver flerlinjet matchningstilstand, standard false |
-
-## Brugsscenarier
-
-**Egnet til:**
-- Søge efter specifikke strenge eller mønstre i kodebasen
-- Finde hvor funktioner/variabler bruges
-- Filtrere søgeresultater efter filtype
-- Tælle antal matches
-
-**Ikke egnet til:**
-- Søge filer efter filnavn — brug Glob
-- Åben udforskning der kræver flere søgerunder — brug Task (Explore-type)
-
-## Bemærkninger
-
-- Bruger ripgrep-syntaks (ikke grep), specialtegn som krøllede parenteser skal escapes
-- `files_with_matches`-tilstand returnerer kun filstier, mest effektiv
-- `content`-tilstand returnerer matchende linjeindhold, understøtter kontekstlinjer
-- Flerlinjet matching kræver indstillingen `multiline: true`
-- Brug altid Grep-værktøjet frem for `grep`- eller `rg`-kommandoer i Bash
-
-## Originaltekst
-
-<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>