v2.0.54 (+128 tokens)

This commit is contained in:
bl-ue 2025-11-25 17:11:24 -07:00
parent 365e8168ef
commit 3bd3a890d1
3 changed files with 9 additions and 7 deletions

View File

@ -1,6 +1,6 @@
# Claude Code System Prompts
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.0.53](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.53) (November 24th, 2025).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 34 versions since v2.0.14.
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.0.54](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.54) (November 25th, 2025).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 35 versions since v2.0.14.
Why multiple "system prompts?"
@ -55,7 +55,7 @@ Sub-agents and utilities.
- [Agent Prompt: Claude Code guide agent](./system-prompts/agent-prompt-claude-code-guide-agent.md) (**589** tks) - System prompt for the claude-code-guide agent that helps users understand and use Claude Code and the Claude Agent SDK.
- [Agent Prompt: Conversation summarization with additional instructions](./system-prompts/agent-prompt-conversation-summarization-with-additional-instructions.md) (**1133** tks) - Extended summarization prompt with support for custom additional instructions.
- [Agent Prompt: Conversation summarization](./system-prompts/agent-prompt-conversation-summarization.md) (**1121** tks) - System prompt for creating detailed conversation summaries.
- [Agent Prompt: Multi-Agent Planning Note](./system-prompts/agent-prompt-multi-agent-planning-note.md) (**324** tks) - Part of the Plan mode system reminder instructing the model how to use multiple agents to plan solutions. Included only if the CLAUDE_CODE_PLAN_V2_AGENT_COUNT environment variable is set to a number greater than 1..
- [Agent Prompt: Multi-Agent Planning Note](./system-prompts/agent-prompt-multi-agent-planning-note.md) (**348** tks) - Part of the Plan mode system reminder instructing the model how to use multiple agents to plan solutions. Included only if the CLAUDE_CODE_PLAN_V2_AGENT_COUNT environment variable is set to a number greater than 1..
- [Agent Prompt: Prompt Hook execution](./system-prompts/agent-prompt-prompt-hook-execution.md) (**134** tks) - Prompt given to Claude when acting evaluating whether to pass or fail a prompt hook..
- [Agent Prompt: Session notes template](./system-prompts/agent-prompt-session-notes-template.md) (**260** tks) - Template structure for session notes tracking coding work and decisions.
- [Agent Prompt: Session notes update instructions](./system-prompts/agent-prompt-session-notes-update-instructions.md) (**759** tks) - Instructions for updating session notes files during conversations.
@ -91,7 +91,7 @@ Text for large system reminders.
> [!NOTE]
> Note that we're planning to add a **system reminder creator/editor** to [tweakcc](https://github.com/Piebald-AI/tweakcc); :+1: [this issue](https://github.com/Piebald-AI/tweakcc/issues/113) if you're interested in that idea.
- [System Reminder: Plan mode is active (enhanced)](./system-prompts/system-reminder-plan-mode-is-active-enhanced.md) (**789** tks) - Enhanced plan mode system reminder with parallel exploration and multi-agent planning.
- [System Reminder: Plan mode is active (enhanced)](./system-prompts/system-reminder-plan-mode-is-active-enhanced.md) (**893** tks) - Enhanced plan mode system reminder with parallel exploration and multi-agent planning.
- [System Reminder: Plan mode is active (for subagents)](./system-prompts/system-reminder-plan-mode-is-active-for-subagents.md) (**310** tks) - Simplified plan mode system reminder for sub agents.
- [System Reminder: Plan mode is active](./system-prompts/system-reminder-plan-mode-is-active.md) (**242** tks) - System reminder sent to Claude when the user enters plan mode.
- [System Reminder: Plan mode re-entry](./system-prompts/system-reminder-plan-mode-re-entry.md) (**236** tks) - System reminder sent when the user enters Plan mode after having previously exited it either via shift+tab or by approving Claude's plan..

View File

@ -1,7 +1,7 @@
<!--
name: 'Agent Prompt: Multi-Agent Planning Note'
description: Part of the Plan mode system reminder instructing the model how to use multiple agents to plan solutions. Included only if the CLAUDE_CODE_PLAN_V2_AGENT_COUNT environment variable is set to a number greater than 1.
ccVersion: 2.0.47
ccVersion: 2.0.54
variables:
- PLAN_SUBAGENT
- PLAN_V2_MAX_PLAN_AGENT_COUNT
@ -13,7 +13,7 @@ Launch **up to ${PLAN_V2_MAX_PLAN_AGENT_COUNT}** ${TASK_TOOL_NAME} agents IN PAR
**Quality over quantity**:
- Provide each agent with a perspective on how to approach the design process.
- Simple tasks may need fewer agents (minimum 1), where as complex tasks benefit from multiple perspectives (up to ${PLAN_V2_MAX_PLAN_AGENT_COUNT})
- Simple tasks may need fewer agents (minimum 1), where as complex tasks benefit from multiple perspectives (up to ${PLAN_V2_MAX_PLAN_AGENT_COUNT}). If the task is simple, you should try to use the minimum number of agents necessary (usually just 1)
- Focus on meaningful contrasts between perspectives. Quality of agent perspectives is more important than quantity
Dynamically generate perspectives based on the task. Examples:

View File

@ -1,7 +1,7 @@
<!--
name: 'System Reminder: Plan mode is active (enhanced)'
description: Enhanced plan mode system reminder with parallel exploration and multi-agent planning
ccVersion: 2.0.47
ccVersion: 2.0.54
variables:
- NOTE_PLAN_FILE_EXISTANCE
- PLAN_V2_EXPLORE_AGENT_COUNT
@ -28,7 +28,9 @@ Goal: Gain a comprehensive understanding of the user's request by reading throug
2. **Launch up to ${EXPLORE_SUBAGENT} ${PLAN_V2_EXPLORE_AGENT_COUNT.agentType} agents IN PARALLEL** (single message, multiple tool calls) to efficiently explore the codebase. Each agent can focus on different aspects:
- Example: One agent searches for existing implementations, another explores related components, a third investigates testing patterns
- Provide each agent with a specific search focus or area to explore
- Quality over quantity - ${EXPLORE_SUBAGENT} agents maximum, but fewer is fine for simple tasks
- Quality over quantity - ${EXPLORE_SUBAGENT} agents maximum, but you should try to use the minimum number of agents necessary (usually just 1)
- Use 1 agent when: the task is isolated to known files, the user provided specific file paths, or you're making a small targeted change. Use multiple agents when: the scope is uncertain, multiple areas of the codebase are involved, or you need to understand existing patterns before planning.
- Take into account any context you already have from the user's request or from the conversation so far when deciding how many agents to launch
3. Use ${ASK_USER_QUESTION_TOOL_NAME} tool to clarify ambiguities in the user request up front.