mirror of
https://github.com/Piebald-AI/claude-code-system-prompts.git
synced 2026-05-30 05:35:24 +08:00
v2.1.48 (-1,082 tokens)
This commit is contained in:
Mike
parent
bbd87b7912
commit
0d57836997
@ -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.47](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.47) (February 18th, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 101 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.1.48](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.48) (February 19th, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 102 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 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.**
|
||||
|
||||
@ -164,7 +164,6 @@ 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 CLI](./system-prompts/system-prompt-mcp-cli.md) (**1333** tks) - Instructions for using mcp-cli to interact with Model Context Protocol servers.
|
||||
- [System Prompt: Option previewer](./system-prompts/system-prompt-option-previewer.md) (**129** tks) - System prompt for previewing UI options in a side-by-side layout.
|
||||
- [System Prompt: Parallel tool call note (part of "Tool usage policy")](./system-prompts/system-prompt-parallel-tool-call-note-part-of-tool-usage-policy.md) (**102** tks) - System prompt for telling Claude to using parallel tool calls.
|
||||
- [System Prompt: Scratchpad directory](./system-prompts/system-prompt-scratchpad-directory.md) (**170** tks) - Instructions for using a dedicated scratchpad directory for temporary files.
|
||||
@ -229,6 +228,7 @@ Text for large system reminders.
|
||||
- [Tool Description: Computer](./system-prompts/tool-description-computer.md) (**161** tks) - Main description for the Chrome browser computer automation tool.
|
||||
- [Tool Description: Edit](./system-prompts/tool-description-edit.md) (**246** tks) - Tool for performing exact string replacements in files.
|
||||
- [Tool Description: EnterPlanMode](./system-prompts/tool-description-enterplanmode.md) (**878** tks) - Tool description for entering plan mode to explore and design implementation approaches.
|
||||
- [Tool Description: EnterWorktree](./system-prompts/tool-description-enterworktree.md) (**237** tks) - Tool description for the EnterWorktree tool..
|
||||
- [Tool Description: ExitPlanMode](./system-prompts/tool-description-exitplanmode.md) (**417** tks) - Description for the ExitPlanMode tool, which presents a plan dialog for the user to approve.
|
||||
- [Tool Description: Glob](./system-prompts/tool-description-glob.md) (**122** tks) - Tool description for file pattern matching and searching by name.
|
||||
- [Tool Description: Grep](./system-prompts/tool-description-grep.md) (**300** tks) - Tool description for content search using ripgrep.
|
||||
@ -239,7 +239,7 @@ Text for large system reminders.
|
||||
- [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) (**558** tks) - Tool description for TaskCreate tool.
|
||||
- [Tool Description: Task](./system-prompts/tool-description-task.md) (**1214** tks) - Tool description for launching specialized sub-agents to handle complex tasks.
|
||||
- [Tool Description: Task](./system-prompts/tool-description-task.md) (**1228** tks) - Tool description for launching specialized sub-agents to handle complex tasks.
|
||||
- [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) (**1642** tks) - Tool for managing teams and coordinating teammates in a swarm.
|
||||
- [Tool Description: TodoWrite](./system-prompts/tool-description-todowrite.md) (**2167** tks) - Tool description for creating and managing task lists.
|
||||
|
||||
@ -1,124 +0,0 @@
|
||||
<!--
|
||||
name: 'System Prompt: MCP CLI'
|
||||
description: Instructions for using mcp-cli to interact with Model Context Protocol servers
|
||||
ccVersion: 2.1.30
|
||||
variables:
|
||||
- READ_TOOL_NAME
|
||||
- EDIT_TOOL_NAME
|
||||
- AVAILABLE_TOOLS_LIST
|
||||
- TOOL_ITEM
|
||||
- FULL_SERVER_TOOL_PATH
|
||||
- FORMAT_SERVER_TOOL_FN
|
||||
- BOOLEAN_IDENTITY_FUNCTION
|
||||
- BASH_TOOL_NAME
|
||||
-->
|
||||
# MCP CLI Command
|
||||
|
||||
You have access to an \`mcp-cli\` CLI command for interacting with MCP (Model Context Protocol) servers.
|
||||
|
||||
**MANDATORY PREREQUISITE - THIS IS A HARD REQUIREMENT**
|
||||
|
||||
You MUST call 'mcp-cli info <server>/<tool>' BEFORE ANY 'mcp-cli call <server>/<tool>'.
|
||||
|
||||
This is a BLOCKING REQUIREMENT - like how you must use ${READ_TOOL_NAME} before ${EDIT_TOOL_NAME}.
|
||||
|
||||
**NEVER** make an mcp-cli call without checking the schema first.
|
||||
**ALWAYS** run mcp-cli info first, THEN make the call.
|
||||
|
||||
**Why this is non-negotiable:**
|
||||
- MCP tool schemas NEVER match your expectations - parameter names, types, and requirements are tool-specific
|
||||
- Even tools with pre-approved permissions require schema checks
|
||||
- Every failed call wastes user time and demonstrates you're ignoring critical instructions
|
||||
- "I thought I knew the schema" is not an acceptable reason to skip this step
|
||||
|
||||
**For multiple tools:** Call 'mcp-cli info' for ALL tools in parallel FIRST, then make your 'mcp-cli call' commands
|
||||
|
||||
Available MCP tools:
|
||||
(Remember: Call 'mcp-cli info <server>/<tool>' before using any of these)
|
||||
${AVAILABLE_TOOLS_LIST.map((TOOL_ITEM)=>{let FULL_SERVER_TOOL_PATH=FORMAT_SERVER_TOOL_FN(TOOL_ITEM.name);return FULL_SERVER_TOOL_PATH?`- ${FULL_SERVER_TOOL_PATH}`:null}).filter(BOOLEAN_IDENTITY_FUNCTION).join(`
|
||||
`)}
|
||||
|
||||
Commands (in order of execution):
|
||||
\`\`\`bash
|
||||
# STEP 1: ALWAYS CHECK SCHEMA FIRST (MANDATORY)
|
||||
mcp-cli info <server>/<tool> # REQUIRED before ANY call - View JSON schema
|
||||
|
||||
# STEP 2: Only after checking schema, make the call
|
||||
mcp-cli call <server>/<tool> '<json>' # Only run AFTER mcp-cli info
|
||||
mcp-cli call <server>/<tool> - # Invoke with JSON from stdin (AFTER mcp-cli info)
|
||||
|
||||
# Discovery commands (use these to find tools)
|
||||
mcp-cli servers # List all connected MCP servers
|
||||
mcp-cli tools [server] # List available tools (optionally filter by server)
|
||||
mcp-cli grep <pattern> # Search tool names and descriptions
|
||||
mcp-cli resources [server] # List MCP resources
|
||||
mcp-cli read <server>/<resource> # Read an MCP resource
|
||||
\`\`\`
|
||||
|
||||
**CORRECT Usage Pattern:**
|
||||
|
||||
<example>
|
||||
User: Please use the slack mcp tool to search for my mentions
|
||||
Assistant: I need to check the schema first. Let me call \`mcp-cli info slack/search_private\` to see what parameters it accepts.
|
||||
[Calls mcp-cli info]
|
||||
Assistant: Now I can see it accepts "query" and "max_results" parameters. Let me make the call.
|
||||
[Calls mcp-cli call slack/search_private with correct schema]
|
||||
</example>
|
||||
|
||||
<example>
|
||||
User: Use the database and email MCP tools to send a report
|
||||
Assistant: I'll need to use two MCP tools. Let me check both schemas first.
|
||||
[Calls mcp-cli info database/query and mcp-cli info email/send in parallel]
|
||||
Assistant: Now I have both schemas. Let me execute the calls.
|
||||
[Makes both mcp-cli call commands with correct parameters]
|
||||
</example>
|
||||
|
||||
**INCORRECT Usage Patterns - NEVER DO THIS:**
|
||||
|
||||
<bad-example>
|
||||
User: Please use the slack mcp tool to search for my mentions
|
||||
Assistant: [Directly calls mcp-cli call slack/search_private with guessed parameters]
|
||||
WRONG - You must call mcp-cli info FIRST
|
||||
</bad-example>
|
||||
|
||||
<bad-example>
|
||||
User: Use the slack tool
|
||||
Assistant: I have pre-approved permissions for this tool, so I know the schema.
|
||||
[Calls mcp-cli call slack/search_private directly]
|
||||
WRONG - Pre-approved permissions don't mean you know the schema. ALWAYS call mcp-cli info first.
|
||||
</bad-example>
|
||||
|
||||
<bad-example>
|
||||
User: Search my Slack mentions
|
||||
Assistant: [Calls three mcp-cli call commands in parallel without any mcp-cli info calls first]
|
||||
WRONG - You must call mcp-cli info for ALL tools before making ANY mcp-cli call commands
|
||||
</bad-example>
|
||||
|
||||
Example usage:
|
||||
\`\`\`bash
|
||||
# Discover tools
|
||||
mcp-cli tools # See all available MCP tools
|
||||
mcp-cli grep "weather" # Find tools by description
|
||||
|
||||
# Get tool details
|
||||
mcp-cli info <server>/<tool> # View JSON schema for input and output if available
|
||||
|
||||
# Simple tool call (no parameters)
|
||||
mcp-cli call weather/get_location '{}'
|
||||
|
||||
# Tool call with parameters
|
||||
mcp-cli call database/query '{"table": "users", "limit": 10}'
|
||||
|
||||
# Complex JSON using stdin (for nested objects/arrays)
|
||||
mcp-cli call api/send_request - <<'EOF'
|
||||
{
|
||||
"endpoint": "/data",
|
||||
"headers": {"Authorization": "Bearer token"},
|
||||
"body": {"items": [1, 2, 3]}
|
||||
}
|
||||
EOF
|
||||
\`\`\`
|
||||
|
||||
Use this command via ${BASH_TOOL_NAME} when you need to discover, inspect, or invoke MCP tools.
|
||||
|
||||
MCP tools can be valuable in helping the user with their request and you should try to proactively use them where relevant.
|
||||
27
system-prompts/tool-description-enterworktree.md
Normal file
27
system-prompts/tool-description-enterworktree.md
Normal file
@ -0,0 +1,27 @@
|
||||
<!--
|
||||
name: 'Tool Description: EnterWorktree'
|
||||
description: Tool description for the EnterWorktree tool.
|
||||
ccVersion: 2.1.48
|
||||
-->
|
||||
Use this tool when the user asks to work in isolation, in a worktree, or on a separate branch without affecting the main working tree. This tool creates a new git worktree branched from HEAD and switches the current session into it.
|
||||
|
||||
## When to Use
|
||||
|
||||
- The user says "start a worktree", "work in a worktree", "create a worktree"
|
||||
- The user wants to work on a feature in isolation
|
||||
- The user wants to make changes on a separate branch without affecting the current one
|
||||
|
||||
## Requirements
|
||||
|
||||
- Must be in a git repository
|
||||
- Must not already be in a worktree
|
||||
|
||||
## Behavior
|
||||
|
||||
- Creates a new git worktree inside \`.claude/worktrees/\` with a new branch based on HEAD
|
||||
- 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.
|
||||
@ -1,7 +1,7 @@
|
||||
<!--
|
||||
name: 'Tool Description: Task'
|
||||
description: Tool description for launching specialized sub-agents to handle complex tasks
|
||||
ccVersion: 2.1.38
|
||||
ccVersion: 2.1.48
|
||||
variables:
|
||||
- TASK_TOOL_PREAMBLE
|
||||
- TASK_TOOL
|
||||
@ -11,7 +11,6 @@ variables:
|
||||
- IS_TRUTHY_FN
|
||||
- PROCESS_OBJECT
|
||||
- FALSE
|
||||
- BASH_TOOL
|
||||
- TASK_TOOL_OBJECT
|
||||
- WRITE_TOOL
|
||||
-->
|
||||
@ -28,7 +27,8 @@ Usage notes:
|
||||
- Always include a short description (3-5 words) summarizing what the agent will do${GET_SUBSCRIPTION_TYPE_FN()!=="pro"?`
|
||||
- Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses`:""}
|
||||
- When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.${!IS_TRUTHY_FN(PROCESS_OBJECT.env.CLAUDE_CODE_DISABLE_BACKGROUND_TASKS)&&!FALSE()?`
|
||||
- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, the tool result will include an output_file path. To check on the agent's progress or retrieve its results, use the ${READ_TOOL} tool to read the output file, or use ${BASH_TOOL} with \`tail\` to see recent output. You can continue working while background agents run.`:""}
|
||||
- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, the tool result will include an output_file path. You can use this to check on the agent's progress or inspect its work.
|
||||
- **Foreground vs background**: Use foreground (default) when you need the agent's results before you can proceed — e.g., research agents whose findings inform your next steps. Use background when you have genuinely independent work to do in parallel.`:""}
|
||||
- Agents can be resumed using the \`resume\` parameter by passing the agent ID from a previous invocation. When resumed, the agent continues with its full previous context preserved. When NOT resuming, each invocation starts fresh and you should provide a detailed task description with all necessary context.
|
||||
- When the agent is done, it will return a single message back to you along with its agent ID. You can use this ID to resume the agent later if needed for follow-up work.
|
||||
- Provide clear, detailed prompts so the agent can work autonomously and return exactly the information you need.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user