From 0b6cc0cad8432200f6d794031d0207a8bc6d5420 Mon Sep 17 00:00:00 2001 From: Mike Date: Fri, 3 Apr 2026 18:54:48 -0600 Subject: [PATCH] v2.1.92 (-167 tokens) --- README.md | 14 ++++++-------- ...ent-prompt-hook-condition-evaluator-stop.md | 12 ++++++++++++ .../agent-prompt-hook-condition-evaluator.md | 10 ---------- .../agent-prompt-session-search-assistant.md | 4 ++-- ...system-prompt-mcp-tool-result-truncation.md | 4 ++-- ...system-prompt-remote-plan-mode-ultraplan.md | 13 +++++-------- ...ystem-prompt-team-memory-content-display.md | 14 -------------- system-prompts/tool-description-sleep.md | 18 ------------------ system-prompts/tool-description-write.md | 7 +++---- 9 files changed, 30 insertions(+), 66 deletions(-) create mode 100644 system-prompts/agent-prompt-hook-condition-evaluator-stop.md delete mode 100644 system-prompts/agent-prompt-hook-condition-evaluator.md delete mode 100644 system-prompts/system-prompt-team-memory-content-display.md delete mode 100644 system-prompts/tool-description-sleep.md diff --git a/README.md b/README.md index ea2c142..5634de7 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,7 @@ Download it and try it out for free! **https://piebald.ai/** > [!important] > **NEW (January 23, 2026): We've added all of Claude Code's ~40 system reminders to this list—see [System Reminders](#system-reminders).** -This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.1.91](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.91) (April 2nd, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 140 versions since v2.0.14. From the team behind [ **Piebald.**](https://piebald.ai/) +This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.1.92](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.92) (April 3rd, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 141 versions since v2.0.14. From the team behind [ **Piebald.**](https://piebald.ai/) **This repository is updated within minutes of each Claude Code release. See the [changelog](./CHANGELOG.md), and follow [@PiebaldAI](https://x.com/PiebaldAI) on X for a summary of the system prompt changes in each release.** @@ -103,14 +103,14 @@ Sub-agents and utilities. - [Agent Prompt: Determine which memory files to attach](./system-prompts/agent-prompt-determine-which-memory-files-to-attach.md) (**265** tks) - Agent for determining which memory files to attach for the main agent. - [Agent Prompt: Dream memory consolidation](./system-prompts/agent-prompt-dream-memory-consolidation.md) (**727** tks) - Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index. - [Agent Prompt: General purpose](./system-prompts/agent-prompt-general-purpose.md) (**285** tks) - System prompt for the general-purpose subagent that searches, analyzes, and edits code across a codebase while reporting findings concisely to the caller. -- [Agent Prompt: Hook condition evaluator](./system-prompts/agent-prompt-hook-condition-evaluator.md) (**78** tks) - System prompt for evaluating hook conditions in Claude Code. +- [Agent Prompt: Hook condition evaluator (stop)](./system-prompts/agent-prompt-hook-condition-evaluator-stop.md) (**145** tks) - System prompt for evaluating hook conditions, specifically stop conditions, in Claude Code. - [Agent Prompt: Prompt Suggestion Generator v2](./system-prompts/agent-prompt-prompt-suggestion-generator-v2.md) (**296** tks) - V2 instructions for generating prompt suggestions for Claude Code. - [Agent Prompt: Quick PR creation](./system-prompts/agent-prompt-quick-pr-creation.md) (**806** tks) - Streamlined prompt for creating a commit and pull request with pre-populated context. - [Agent Prompt: Quick git commit](./system-prompts/agent-prompt-quick-git-commit.md) (**510** tks) - Streamlined prompt for creating a single git commit with pre-populated context. - [Agent Prompt: Recent Message Summarization](./system-prompts/agent-prompt-recent-message-summarization.md) (**724** tks) - Agent prompt used for summarizing recent messages. - [Agent Prompt: Security monitor for autonomous agent actions (first part)](./system-prompts/agent-prompt-security-monitor-for-autonomous-agent-actions-first-part.md) (**3101** tks) - Instructs Claude to act as a security monitor that evaluates autonomous coding agent actions against block/allow rules to prevent prompt injection, scope creep, and accidental damage. - [Agent Prompt: Security monitor for autonomous agent actions (second part)](./system-prompts/agent-prompt-security-monitor-for-autonomous-agent-actions-second-part.md) (**3325** tks) - Defines the environment context, block rules, and allow exceptions that govern which tool actions the agent may or may not perform. -- [Agent Prompt: Session Search Assistant](./system-prompts/agent-prompt-session-search-assistant.md) (**439** tks) - Agent prompt for the session search assistant that finds relevant sessions based on user queries and metadata. +- [Agent Prompt: Session Search Assistant](./system-prompts/agent-prompt-session-search-assistant.md) (**426** tks) - Agent prompt for the session search assistant that finds relevant sessions based on user queries and metadata. - [Agent Prompt: Session memory update instructions](./system-prompts/agent-prompt-session-memory-update-instructions.md) (**756** tks) - Instructions for updating session memory files during conversations. - [Agent Prompt: Session title and branch generation](./system-prompts/agent-prompt-session-title-and-branch-generation.md) (**307** tks) - Agent for generating succinct session titles and git branch names. - [Agent Prompt: Verification specialist](./system-prompts/agent-prompt-verification-specialist.md) (**2938** tks) - System prompt for a verification subagent that adversarially tests implementations by running builds, test suites, linters, and adversarial probes, then issuing a PASS/FAIL/PARTIAL verdict. @@ -188,7 +188,7 @@ Parts of the main system prompt. - [System Prompt: Insights suggestions](./system-prompts/system-prompt-insights-suggestions.md) (**748** tks) - Generates actionable suggestions including CLAUDE.md additions, features to try, and usage patterns. - [System Prompt: Learning mode (insights)](./system-prompts/system-prompt-learning-mode-insights.md) (**142** tks) - Instructions for providing educational insights when learning mode is active. - [System Prompt: Learning mode](./system-prompts/system-prompt-learning-mode.md) (**1042** tks) - Main system prompt for learning mode with human collaboration instructions. -- [System Prompt: MCP Tool Result Truncation](./system-prompts/system-prompt-mcp-tool-result-truncation.md) (**147** tks) - Guidelines for handling long outputs from MCP tools, including when to use direct file queries vs subagents for analysis. +- [System Prompt: MCP Tool Result Truncation](./system-prompts/system-prompt-mcp-tool-result-truncation.md) (**164** tks) - Guidelines for handling long outputs from MCP tools, including when to use direct file queries vs subagents for analysis. - [System Prompt: Memory description of user feedback](./system-prompts/system-prompt-memory-description-of-user-feedback.md) (**139** tks) - Describes the user feedback memory type that stores guidance about work approaches, emphasizing recording both successes and failures and checking for contradictions with team memories. - [System Prompt: Minimal mode](./system-prompts/system-prompt-minimal-mode.md) (**164** tks) - Describes the behavior and constraints of minimal mode, which skips hooks, LSP, plugins, auto-memory, and other features while requiring explicit context via CLI flags. - [System Prompt: One of six rules for using sleep command](./system-prompts/system-prompt-one-of-six-rules-for-using-sleep-command.md) (**23** tks) - One of the six rules for using the sleep command. @@ -198,12 +198,11 @@ Parts of the main system prompt. - [System Prompt: Partial compaction instructions](./system-prompts/system-prompt-partial-compaction-instructions.md) (**725** tks) - Instructions on how to compact when the user decided to compact only a portion of the conversation, with a structured summary format and analysis process. - [System Prompt: Phase four of plan mode](./system-prompts/system-prompt-phase-four-of-plan-mode.md) (**142** tks) - Phase four of plan mode. - [System Prompt: PowerShell edition for 5.1](./system-prompts/system-prompt-powershell-edition-for-51.md) (**285** tks) - System prompt for providing information about Windows PowerShell 5.1. -- [System Prompt: Remote plan mode (ultraplan)](./system-prompts/system-prompt-remote-plan-mode-ultraplan.md) (**652** tks) - System reminder injected during remote planning sessions that instructs Claude to explore the codebase, produce a diagram-rich plan via ExitPlanMode, and implement it with a pull request upon approval. +- [System Prompt: Remote plan mode (ultraplan)](./system-prompts/system-prompt-remote-plan-mode-ultraplan.md) (**617** tks) - System reminder injected during remote planning sessions that instructs Claude to explore the codebase, produce a diagram-rich plan via ExitPlanMode, and implement it with a pull request upon approval. - [System Prompt: Remote planning session](./system-prompts/system-prompt-remote-planning-session.md) (**432** tks) - System reminder that configures a remote planning session to explore the codebase, produce an implementation plan via ExitPlanMode, and handle plan approval, rejection, or teleportation back to the user's local terminal. - [System Prompt: Scratchpad directory](./system-prompts/system-prompt-scratchpad-directory.md) (**170** tks) - Instructions for using a dedicated scratchpad directory for temporary files. - [System Prompt: Skillify Current Session](./system-prompts/system-prompt-skillify-current-session.md) (**1882** tks) - System prompt for converting the current session in to a skill. - [System Prompt: Subagent delegation examples](./system-prompts/system-prompt-subagent-delegation-examples.md) (**606** tks) - Provides example interactions showing how a coordinator agent should delegate tasks to subagents, handle waiting states, and report results. -- [System Prompt: Team memory content display](./system-prompts/system-prompt-team-memory-content-display.md) (**55** tks) - Renders shared team memory file contents with path and content for injection into the conversation context. - [System Prompt: Teammate Communication](./system-prompts/system-prompt-teammate-communication.md) (**130** tks) - System prompt for teammate communication in swarm. - [System Prompt: Tone and style (code references)](./system-prompts/system-prompt-tone-and-style-code-references.md) (**39** tks) - Instruction to include file_path:line_number when referencing code. - [System Prompt: Tone and style (concise output — short)](./system-prompts/system-prompt-tone-and-style-concise-output-short.md) (**16** tks) - Instruction for short and concise responses. @@ -282,14 +281,13 @@ Text for large system reminders. - [Tool Description: ReadFile](./system-prompts/tool-description-readfile.md) (**473** tks) - Tool description for reading files. - [Tool Description: SendMessageTool](./system-prompts/tool-description-sendmessagetool.md) (**362** tks) - Agent teams version of SendMessageTool. - [Tool Description: Skill](./system-prompts/tool-description-skill.md) (**326** tks) - Tool description for executing skills in the main conversation. -- [Tool Description: Sleep](./system-prompts/tool-description-sleep.md) (**154** tks) - Tool for waiting/sleeping with early wake capability on user input. - [Tool Description: TaskCreate](./system-prompts/tool-description-taskcreate.md) (**499** tks) - Tool description for TaskCreate tool. - [Tool Description: TeamDelete](./system-prompts/tool-description-teamdelete.md) (**154** tks) - Tool description for the TeamDelete tool. - [Tool Description: TeammateTool](./system-prompts/tool-description-teammatetool.md) (**1585** tks) - Tool for managing teams and coordinating teammates in a swarm. - [Tool Description: TodoWrite](./system-prompts/tool-description-todowrite.md) (**2037** tks) - Tool description for creating and managing task lists. - [Tool Description: WebFetch](./system-prompts/tool-description-webfetch.md) (**297** tks) - Tool description for web fetch functionality. - [Tool Description: WebSearch](./system-prompts/tool-description-websearch.md) (**321** tks) - Tool description for web search functionality. -- [Tool Description: Write](./system-prompts/tool-description-write.md) (**132** tks) - Tool for writing files to the local filesystem. +- [Tool Description: Write](./system-prompts/tool-description-write.md) (**138** tks) - Tool for writing files to the local filesystem. **Additional notes for some Tool Descriptions** diff --git a/system-prompts/agent-prompt-hook-condition-evaluator-stop.md b/system-prompts/agent-prompt-hook-condition-evaluator-stop.md new file mode 100644 index 0000000..dd5ba25 --- /dev/null +++ b/system-prompts/agent-prompt-hook-condition-evaluator-stop.md @@ -0,0 +1,12 @@ + +You are evaluating a stop-condition hook in Claude Code. Read the conversation transcript carefully, then judge whether the user-provided condition is satisfied. + +Your response must be a JSON object with one of these shapes: +- {"ok": true, "reason": ""} +- {"ok": false, "reason": ""} + +Always include a "reason" field, quoting specific text from the transcript whenever possible. If the transcript does not contain clear evidence that the condition is satisfied, return {"ok": false, "reason": "insufficient evidence in transcript"}. diff --git a/system-prompts/agent-prompt-hook-condition-evaluator.md b/system-prompts/agent-prompt-hook-condition-evaluator.md deleted file mode 100644 index 8b0069e..0000000 --- a/system-prompts/agent-prompt-hook-condition-evaluator.md +++ /dev/null @@ -1,10 +0,0 @@ - -You are evaluating a hook in Claude Code. - -Your response must be a JSON object matching one of the following schemas: -1. If the condition is met, return: {"ok": true} -2. If the condition is not met, return: {"ok": false, "reason": "Reason for why it is not met"} diff --git a/system-prompts/agent-prompt-session-search-assistant.md b/system-prompts/agent-prompt-session-search-assistant.md index 8faae73..24409a1 100644 --- a/system-prompts/agent-prompt-session-search-assistant.md +++ b/system-prompts/agent-prompt-session-search-assistant.md @@ -1,7 +1,7 @@ Your goal is to find relevant sessions based on a user's search query. @@ -9,7 +9,7 @@ You will be given a list of sessions with their metadata and a search query. Ide Each session may include: - Title (display name or custom title) -- Tag (user-assigned category, shown as [tag: name] - users tag sessions with /tag command to categorize them) +- Tag (user-assigned category, shown as [tag: name]) - Branch (git branch name, shown as [branch: name]) - Summary (AI-generated summary) - First message (beginning of the conversation) diff --git a/system-prompts/system-prompt-mcp-tool-result-truncation.md b/system-prompts/system-prompt-mcp-tool-result-truncation.md index 9922bfb..6681e2d 100644 --- a/system-prompts/system-prompt-mcp-tool-result-truncation.md +++ b/system-prompts/system-prompt-mcp-tool-result-truncation.md @@ -1,10 +1,10 @@ - For targeted queries (find a row, filter by field): use jq or grep on the file directly. -- For analysis or summarization that requires reading the full content: use the ${AGENT_TOOL_NAME} tool to process the file in an isolated context so the full output does not enter your main context. Be explicit about what the subagent must return — e.g. "Read ALL of ${FILE_PATH}; summarize it and quote any key findings, decisions, or action items verbatim" — a vague "summarize this" may lose the detail you actually need. Require it to read the entire file before answering. +- For analysis or summarization that requires reading the full content: use the ${AGENT_TOOL_NAME} tool to process the file in an isolated context so the full output does not enter your main context. Be explicit about what the subagent must return — e.g. "Read ${FILE_PATH} in sequential chunks using offset/limit until you have read 100% of it, then summarize it and quote any key findings, decisions, or action items verbatim" — a vague "summarize this" may lose the detail you actually need. Require it to read the entire file in chunks before answering. diff --git a/system-prompts/system-prompt-remote-plan-mode-ultraplan.md b/system-prompts/system-prompt-remote-plan-mode-ultraplan.md index b223ac7..840e941 100644 --- a/system-prompts/system-prompt-remote-plan-mode-ultraplan.md +++ b/system-prompts/system-prompt-remote-plan-mode-ultraplan.md @@ -1,7 +1,7 @@ You're running in a remote planning session. The user triggered this from their local terminal. @@ -10,13 +10,10 @@ Run a lightweight planning process, consistent with how you would in regular pla - Explore the codebase directly with Glob, Grep, and Read. Read the relevant code, understand how the pieces fit, look for existing functions and patterns you can reuse instead of proposing new ones, and shape an approach grounded in what's actually there. - Do not spawn subagents. -When you've settled on an approach, call ExitPlanMode with the plan. -Your primary objective is to make the plan effective for implementation: write it for someone who'll implement it without being able to ask you follow-up questions — they need enough specificity to act (which files, what changes, what order, how to verify), but they don't need you to restate the obvious or pad it with generic advice. -Your second objective is to make the plan easy to parse and review. Lean on diagrams to carry structure that prose would bury: -- Use mermaid blocks (```mermaid ... ```) for anything with flow or hierarchy — a flowchart for control/data flow, a sequence diagram for request/response or multi-actor interactions, a state diagram for mode transitions, a graph for dependency ordering. -- For file-level changes, a simple before/after tree or a table of file → change → why reads faster than paragraphs. -- Keep diagrams tight: a handful of nodes that show the shape of the change, not an exhaustive map. If a diagram needs a legend, it's too big. -Diagrams supplement the plan, they don't replace it — the implementation details still live in prose. Reach for a diagram when a reviewer would otherwise have to hold the structure in their head; skip it when the change is linear or trivially small. +When you've decided on an approach, call ExitPlanMode with the plan. Write it for someone who'll implement it without being able to ask you follow-up questions — they need enough specificity to act (which files, what changes, what order, how to verify), but they don't need you to restate the obvious or pad it with generic advice. + +A plan should be easy for someone to inspect and verify. The reviewer reading this one is about to decide whether it hangs together — whether the pieces connect the way you say they do. Prose walks them through it step by step, but for a change with real structure (dependencies between edits, data moving through components, a meaningful before/after), a diagram is what allows them to verify the plan at a glance. Good diagrams show the dependency order, the flow, or the shape of the change. +Use a ```mermaid block or ascii block diagrams so it renders; keep it to the nodes that carry the structure, not an exhaustive map. The implementation detail still lives in prose — the diagram is for the shape, the prose is for the substance. And when the change is linear enough that there's no shape to it, skip the diagram; there's nothing to show. After calling ExitPlanMode: - If it's approved, implement the plan in this session and open a pull request when done. diff --git a/system-prompts/system-prompt-team-memory-content-display.md b/system-prompts/system-prompt-team-memory-content-display.md deleted file mode 100644 index a220c9a..0000000 --- a/system-prompts/system-prompt-team-memory-content-display.md +++ /dev/null @@ -1,14 +0,0 @@ - -Contents of ${MEMORY_ITEM.path}${MEMORY_TYPE_DESCRIPTION}: - - -${MEMORY_CONTENT} - diff --git a/system-prompts/tool-description-sleep.md b/system-prompts/tool-description-sleep.md deleted file mode 100644 index 2b75098..0000000 --- a/system-prompts/tool-description-sleep.md +++ /dev/null @@ -1,18 +0,0 @@ - -Wait for a specified duration. The user can interrupt the sleep at any time. - -Use this when the user tells you to sleep or rest, when you have nothing to do, or when you're waiting for something. - -You may receive <${TICK_PROMPT}> prompts — these are periodic check-ins. Look for useful work to do before sleeping. - -You can call this concurrently with other tools — it won't interfere with them. - -Prefer this over `Bash(sleep ...)` — it doesn't hold a shell process. - -Each wake-up costs an API call, but the prompt cache expires after 5 minutes of inactivity — balance accordingly. diff --git a/system-prompts/tool-description-write.md b/system-prompts/tool-description-write.md index b19ff9c..3580979 100644 --- a/system-prompts/tool-description-write.md +++ b/system-prompts/tool-description-write.md @@ -1,16 +1,15 @@ Writes a file to the local filesystem. Usage: -- This tool will overwrite the existing file if there is one at the provided path.${GET_NEW_FILE_NOTE_FN()}${WRITE_FILE_NOTE} -- Prefer the Edit tool for modifying existing files — it only sends the diff. ${PREFER_EDIT_NOTE} +- This tool will overwrite the existing file if there is one at the provided path.${GET_NEW_FILE_NOTE_FN()} +- Prefer the Edit tool for modifying existing files — it only sends the diff.${PREFER_EDIT_NOTE} Only use this tool to create new files or for complete rewrites. - NEVER create documentation files (*.md) or README files unless explicitly requested by the User. - Only use emojis if the user explicitly requests it. Avoid writing emojis to files unless asked.