Compare commits

...
5 Commits
Author SHA1 Message Date
Mike 1fdb4df9a3 Update changelog for v2.0.76 2025-12-22 17:54:59 -07:00
Mike 3c9c213328 v2.0.76 (+0 tokens) 2025-12-22 17:54:54 -07:00
Mike 1cc9c6cbc1 Update changelog for v2.0.75 2025-12-20 11:15:33 -07:00
Mike d290cd4001 v2.0.75 (-183 tokens) 2025-12-20 11:13:57 -07:00
Mike 31b275b92c Update changelog for v2.0.74 2025-12-20 10:05:13 -07:00
4 changed files with 29 additions and 17 deletions
+26
View File
@@ -2,8 +2,34 @@
Note: Only use **NEW:** for entirely new prompt files, NOT for new additions/sections within existing prompts. Note: Only use **NEW:** for entirely new prompt files, NOT for new additions/sections within existing prompts.
--> -->
# [2.0.76](https://github.com/Piebald-AI/claude-code-system-prompts/commit/3c9c213)
_+0 tokens_
<sub>_No changes to the system prompts in v2.0.76._</sub>
### Claude Code System Prompts Changelog ### Claude Code System Prompts Changelog
# [2.0.75](https://github.com/Piebald-AI/claude-code-system-prompts/commit/d290cd4)
_-183 tokens_
- **REMOVED:** Agent Prompt: Task tool (extra notes) - additional notes for Task tool usage (absolute paths, no emojis, no colons before tool calls)
- Main system prompt - removed instruction about not using colons before tool calls
# [2.0.74](https://github.com/Piebald-AI/claude-code-system-prompts/commit/33fc177)
_-1693 tokens_
- **NEW:** Agent Prompt: Session Search Assistant - agent prompt for finding relevant sessions based on user queries, with priority matching on tags, titles, branches, summaries, and transcripts
- **REMOVED:** Agent Prompt: Exit plan mode with swarm - instructions for launching swarm teammates when ExitPlanMode is called with `isSwarm` set to true
- **REMOVED:** System Reminder: Delegate mode prompt - system reminder for delegate mode with restricted tool access
- **REMOVED:** System Reminder: Team Coordination - system reminder for team coordination with teammate identity and resources
- **REMOVED:** Tool Description: TaskList - tool for listing all tasks in the task list
- **REMOVED:** Tool Description: TaskUpdate - tool for updating task status and adding comments
- **REMOVED:** Tool Description: TeammateTool's operation parameter - description of TeammateTool operations
- Tool Description: Bash (Git commit and PR creation instructions) - simplified pre-commit hook failure handling; removed detailed amend rules for auto-modified files, now just advises to fix and create a new commit
# [2.0.73](https://github.com/Piebald-AI/claude-code-system-prompts/commit/085fb45) # [2.0.73](https://github.com/Piebald-AI/claude-code-system-prompts/commit/085fb45)
_+91 tokens_ _+91 tokens_
+2 -3
View File
@@ -28,7 +28,7 @@ Download it and try it out for free! **https://piebald.ai/**
[![Mentioned in Awesome Claude Code](https://awesome.re/mentioned-badge.svg)](https://github.com/hesreallyhim/awesome-claude-code) [![Mentioned in Awesome Claude Code](https://awesome.re/mentioned-badge.svg)](https://github.com/hesreallyhim/awesome-claude-code)
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.74](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.74) (December 19th, 2025).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 55 versions since v2.0.14. From the team behind [<img src="https://github.com/Piebald-AI/piebald/raw/main/assets/logo.svg" width="15"> **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.0.76](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.0.76) (December 22nd, 2025).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 57 versions since v2.0.14. From the team behind [<img src="https://github.com/Piebald-AI/piebald/raw/main/assets/logo.svg" width="15"> **Piebald.**](https://piebald.ai/)
Why multiple "system prompts?" Why multiple "system prompts?"
@@ -60,7 +60,6 @@ Sub-agents and utilities.
- [Agent Prompt: Explore](./system-prompts/agent-prompt-explore.md) (**516** tks) - System prompt for the Explore subagent. - [Agent Prompt: Explore](./system-prompts/agent-prompt-explore.md) (**516** tks) - System prompt for the Explore subagent.
- [Agent Prompt: Plan mode (enhanced)](./system-prompts/agent-prompt-plan-mode-enhanced.md) (**633** tks) - Enhanced prompt for the Plan subagent. - [Agent Prompt: Plan mode (enhanced)](./system-prompts/agent-prompt-plan-mode-enhanced.md) (**633** tks) - Enhanced prompt for the Plan subagent.
- [Agent Prompt: Task tool (extra notes)](./system-prompts/agent-prompt-task-tool-extra-notes.md) (**129** tks) - Additional notes for using the Task tool effectively.
- [Agent Prompt: Task tool](./system-prompts/agent-prompt-task-tool.md) (**294** tks) - System prompt given to the subagent spawned via the Task tool. - [Agent Prompt: Task tool](./system-prompts/agent-prompt-task-tool.md) (**294** tks) - System prompt given to the subagent spawned via the Task tool.
### Creation Assistants ### Creation Assistants
@@ -108,7 +107,7 @@ Misc large strings.
Parts of the main system prompt. Parts of the main system prompt.
- [**System Prompt: Main system prompt**](./system-prompts/system-prompt-main-system-prompt.md) (**3035** tks) - Core system prompt for Claude Code defining behavior, tone, and tool usage policies. - [**System Prompt: Main system prompt**](./system-prompts/system-prompt-main-system-prompt.md) (**2981** tks) - Core system prompt for Claude Code defining behavior, tone, and tool usage policies.
- [System Prompt: Claude in Chrome browser automation](./system-prompts/system-prompt-claude-in-chrome-browser-automation.md) (**758** tks) - Instructions for using Claude in Chrome browser automation tools effectively. - [System Prompt: Claude in Chrome browser automation](./system-prompts/system-prompt-claude-in-chrome-browser-automation.md) (**758** tks) - Instructions for using Claude in Chrome browser automation tools effectively.
- [System Prompt: Git status](./system-prompts/system-prompt-git-status.md) (**95** tks) - System prompt for displaying the current git status at the start of the conversation. - [System Prompt: Git status](./system-prompts/system-prompt-git-status.md) (**95** tks) - System prompt for displaying the current git status at the start of the conversation.
- [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 (insights)](./system-prompts/system-prompt-learning-mode-insights.md) (**142** tks) - Instructions for providing educational insights when learning mode is active.
@@ -1,12 +0,0 @@
<!--
name: 'Agent Prompt: Task tool (extra notes)'
description: Additional notes for using the Task tool effectively
ccVersion: 2.0.70
-->
Notes:
- Agent threads always have their cwd reset between bash calls, as a result please only use absolute file paths.
- In your final response always share relevant file names and code snippets. Any file paths you return in your response MUST be absolute. Do NOT use relative paths.
- For clear communication with the user the assistant MUST avoid using emojis.
- Do not use a colon before tool calls. Text like "Let me read the file:" followed by a read tool call should just be "Let me read the file." with a period.
@@ -1,7 +1,7 @@
<!-- <!--
name: 'System Prompt: Main system prompt' name: 'System Prompt: Main system prompt'
description: Core system prompt for Claude Code defining behavior, tone, and tool usage policies description: Core system prompt for Claude Code defining behavior, tone, and tool usage policies
ccVersion: 2.0.73 ccVersion: 2.0.75
variables: variables:
- OUTPUT_STYLE_CONFIG - OUTPUT_STYLE_CONFIG
- SECURITY_POLICY - SECURITY_POLICY
@@ -48,7 +48,6 @@ ${OUTPUT_STYLE_CONFIG!==null?"":`# Tone and style
- Your output will be displayed on a command line interface. Your responses should be short and concise. You can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification. - Your output will be displayed on a command line interface. Your responses should be short and concise. You can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
- Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like ${BASH_TOOL_NAME} or code comments as means to communicate with the user during the session. - Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like ${BASH_TOOL_NAME} or code comments as means to communicate with the user during the session.
- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files. - NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files.
- Do not use a colon before tool calls. Your tool calls may not be shown directly in the output, so text like "Let me read the file:" followed by a read tool call should just be "Let me read the file." with a period.
# Professional objectivity # Professional objectivity
Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if Claude honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs. Avoid using over-the-top validation or excessive praise when responding to users such as "You're absolutely right" or similar phrases. Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if Claude honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs. Avoid using over-the-top validation or excessive praise when responding to users such as "You're absolutely right" or similar phrases.