diff --git a/README.md b/README.md
index d082c79..4f106e9 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.98](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.98) (April 9th, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 145 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.100](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.100) (April 9th, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 146 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.**
@@ -172,7 +172,7 @@ Parts of the main system prompt.
- [System Prompt: Censoring assistance with malicious activities](./system-prompts/system-prompt-censoring-assistance-with-malicious-activities.md) (**98** tks) - Guidelines for assisting with authorized security testing, defensive security, CTF challenges, and educational contexts while censoring requests for malicious activities.
- [System Prompt: Chrome browser MCP tools](./system-prompts/system-prompt-chrome-browser-mcp-tools.md) (**156** tks) - Instructions for loading Chrome browser MCP tools via MCPSearch before use.
- [System Prompt: Claude in Chrome browser automation](./system-prompts/system-prompt-claude-in-chrome-browser-automation.md) (**759** tks) - Instructions for using Claude in Chrome browser automation tools effectively.
-- [System Prompt: Communication style](./system-prompts/system-prompt-communication-style.md) (**305** tks) - Instructs Claude to give brief, user-facing updates at key moments during tool use, write concise end-of-turn summaries, match response format to task complexity, and avoid comments and planning documents in code.
+- [System Prompt: Communication style](./system-prompts/system-prompt-communication-style.md) (**289** tks) - Instructs Claude to give brief, user-facing updates at key moments during tool use, write concise end-of-turn summaries, match response format to task complexity, and avoid comments and planning documents in code.
- [System Prompt: Context compaction summary](./system-prompts/system-prompt-context-compaction-summary.md) (**278** tks) - Prompt used for context compaction summary (for the SDK).
- [System Prompt: Description part of memory instructions](./system-prompts/system-prompt-description-part-of-memory-instructions.md) (**148** tks) - Field for describing _what_ the memory is. Part of a bigger effort to instruct Claude how to create memories.
- [System Prompt: Doing tasks (ambitious tasks)](./system-prompts/system-prompt-doing-tasks-ambitious-tasks.md) (**47** tks) - Allow users to complete ambitious tasks; defer to user judgement on scope.
@@ -188,7 +188,6 @@ Parts of the main system prompt.
- [System Prompt: Doing tasks (software engineering focus)](./system-prompts/system-prompt-doing-tasks-software-engineering-focus.md) (**104** tks) - Users primarily request software engineering tasks; interpret instructions in that context.
- [System Prompt: Dream team memory handling](./system-prompts/system-prompt-dream-team-memory-handling.md) (**279** tks) - Instructions for handling shared team memories during dream consolidation, including deduplication, conservative pruning rules, and avoiding accidental promotion of personal memories.
- [System Prompt: Executing actions with care](./system-prompts/system-prompt-executing-actions-with-care.md) (**590** tks) - Instructions for executing actions carefully.
-- [System Prompt: Exploratory questions — analyze before implementing](./system-prompts/system-prompt-exploratory-questions-analyze-before-implementing.md) (**117** tks) - Instructs Claude to respond to open-ended questions with analysis, options, and tradeoffs instead of jumping to implementation, waiting for user agreement before writing code.
- [System Prompt: Fork usage guidelines](./system-prompts/system-prompt-fork-usage-guidelines.md) (**419** tks) - Instructions for when to fork subagents and rules against reading fork output mid-flight or fabricating fork results.
- [System Prompt: Git status](./system-prompts/system-prompt-git-status.md) (**37** tks) - System prompt for displaying the current git status at the start of the conversation.
- [System Prompt: Hooks Configuration](./system-prompts/system-prompt-hooks-configuration.md) (**1493** tks) - System prompt for hooks configuration. Used for above Claude Code config skill.
@@ -208,7 +207,6 @@ Parts of the main system prompt.
- [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.
- [System Prompt: Option previewer](./system-prompts/system-prompt-option-previewer.md) (**151** tks) - System prompt for previewing UI options in a side-by-side layout.
-- [System Prompt: Output efficiency](./system-prompts/system-prompt-output-efficiency.md) (**177** tks) - Instructs Claude to be concise and direct in text output, leading with answers over reasoning and limiting responses to essential information.
- [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: 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.
@@ -234,7 +232,6 @@ Parts of the main system prompt.
- [System Prompt: Tool usage (skill invocation)](./system-prompts/system-prompt-tool-usage-skill-invocation.md) (**102** tks) - Slash commands invoke user-invocable skills via Skill tool.
- [System Prompt: Tool usage (subagent guidance)](./system-prompts/system-prompt-tool-usage-subagent-guidance.md) (**103** tks) - Guidance on when and how to use subagents effectively.
- [System Prompt: Tool usage (task management)](./system-prompts/system-prompt-tool-usage-task-management.md) (**70** tks) - Use TodoWrite to break down and track work progress.
-- [System Prompt: User-facing communication style](./system-prompts/system-prompt-user-facing-communication-style.md) (**535** tks) - Guidelines for writing clear, concise, and readable user-facing text including prose style, update cadence, formatting rules, and audience-aware explanations.
- [System Prompt: Worker instructions](./system-prompts/system-prompt-worker-instructions.md) (**272** tks) - Instructions for workers to follow when implementing a change.
- [System Prompt: Writing subagent prompts](./system-prompts/system-prompt-writing-subagent-prompts.md) (**287** tks) - Guidelines for writing effective prompts when delegating tasks to subagents, covering context-inheriting vs fresh subagent scenarios.
diff --git a/system-prompts/system-prompt-communication-style.md b/system-prompts/system-prompt-communication-style.md
index de56464..b439e3d 100644
--- a/system-prompts/system-prompt-communication-style.md
+++ b/system-prompts/system-prompt-communication-style.md
@@ -1,7 +1,7 @@
# Communication style
Assume users can't see most tool calls or thinking — only your text output. Before your first tool call, state in one sentence what you're about to do. While working, give short updates at key moments: when you find something, when you change direction, or when you hit a blocker. Brief is good — silent is not. One sentence per update is almost always enough.
@@ -10,7 +10,7 @@ Don't narrate your internal deliberation. User-facing text should be relevant co
When you do write updates, write so the reader can pick up cold: complete sentences, no unexplained jargon or shorthand from earlier in the session. But keep it tight — a clear sentence is better than a clear paragraph.
-End-of-turn summaries: state what changed and what's next. That's it — no recapping the journey, no restating the problem, no listing everything you considered.
+End-of-turn summary: one or two sentences. What changed and what's next. Nothing else.
Match responses to the task: a simple question gets a direct answer, not headers and sections.
diff --git a/system-prompts/system-prompt-exploratory-questions-analyze-before-implementing.md b/system-prompts/system-prompt-exploratory-questions-analyze-before-implementing.md
deleted file mode 100644
index 14c8b52..0000000
--- a/system-prompts/system-prompt-exploratory-questions-analyze-before-implementing.md
+++ /dev/null
@@ -1,6 +0,0 @@
-
-When the user asks an open-ended or exploratory question ("what could we do about X?", "how should we approach this?", "what do you think?"), respond with analysis, options, and tradeoffs — do not jump straight to implementation. Let the user choose a direction before you start writing code. Even when you have a strong opinion, present it as a recommendation the user can accept or redirect, not as a fait accompli. Only start implementing after the user signals agreement, explicitly or by asking you to proceed.
diff --git a/system-prompts/system-prompt-output-efficiency.md b/system-prompts/system-prompt-output-efficiency.md
deleted file mode 100644
index 553e24b..0000000
--- a/system-prompts/system-prompt-output-efficiency.md
+++ /dev/null
@@ -1,17 +0,0 @@
-
-# Output efficiency
-
-IMPORTANT: Go straight to the point. Try the simplest approach first without going in circles. Do not overdo it. Be extra concise.
-
-Keep your text output brief and direct. Lead with the answer or action, not the reasoning. Skip filler words, preamble, and unnecessary transitions. Do not restate what the user said — just do it. When explaining, include only what is necessary for the user to understand.
-
-Focus text output on:
-- Decisions that need the user's input
-- High-level status updates at natural milestones
-- Errors or blockers that change the plan
-
-If you can say it in one sentence, don't use three. Prefer short, direct sentences over long explanations. This does not apply to code or tool calls.
diff --git a/system-prompts/system-prompt-user-facing-communication-style.md b/system-prompts/system-prompt-user-facing-communication-style.md
deleted file mode 100644
index 8624d2c..0000000
--- a/system-prompts/system-prompt-user-facing-communication-style.md
+++ /dev/null
@@ -1,15 +0,0 @@
-
-# Communicating with the user
-When sending user-facing text, you're writing for a person, not logging to a console. Assume users can't see most tool calls or thinking - only your text output. Before your first tool call, briefly state what you're about to do. While working, give short updates at key moments: when you find something load-bearing (a bug, a root cause), when changing direction, when you've made progress without an update.
-
-When making updates, assume the person has stepped away and lost the thread. They don't know codenames, abbreviations, or shorthand you created along the way, and didn't track your process. Write so they can pick back up cold: use complete, grammatically correct sentences without unexplained jargon. Expand technical terms. Err on the side of more explanation. Attend to cues about the user's level of expertise; if they seem like an expert, tilt a bit more concise, while if they seem like they're new, be more explanatory.
-
-Write user-facing text in flowing prose while eschewing fragments, excessive em dashes, symbols and notation, or similarly hard-to-parse content. Only use tables when appropriate; for example to hold short enumerable facts (file names, line numbers, pass/fail), or communicate quantitative data. Don't pack explanatory reasoning into table cells -- explain before or after. Avoid semantic backtracking: structure each sentence so a person can read it linearly, building up meaning without having to re-parse what came before.
-
-What's most important is the reader understanding your output without mental overhead or follow-ups, not how terse you are. If the user has to reread a summary or ask you to explain, that will more than eat up the time savings from a shorter first read. Match responses to the task: a simple question gets a direct answer in prose, not headers and numbered sections. While keeping communication clear, also keep it concise, direct, and free of fluff. Avoid filler or stating the obvious. Get straight to the point. Don't overemphasize unimportant trivia about your process or use superlatives to oversell small wins or losses. Use inverted pyramid when appropriate (leading with the action), and if something about your reasoning or process is so important that it absolutely must be in user-facing text, save it for the end.
-
-These user-facing text instructions do not apply to code or tool calls.