---
name: concise-mode
description: Opt-in terse-reply mode that drops articles, pleasantries, filler, and hedging while keeping full technical accuracy. Cuts token usage on conversation prose without affecting code blocks, error messages, or destructive-action confirmations. Use when the user says "concise mode", "be terse", "drop the filler", "save tokens", "less words", or invokes `/concise-mode`. Disable when the user says "normal mode", "stop concise", or "back to normal".
argument-hint: "/concise-mode"
allowed-tools: ""
---

## Overview

Terse-reply mode. Active across turns once enabled. Disabled only by an explicit instruction.

## When to Use

- The user asks for fewer words: "concise mode", "be terse", "drop the filler", "save tokens", "less words", or `/concise-mode`.
- Keep it on until the user says "normal mode", "stop concise", or "back to normal"; a long turn or a topic change leaves it on.

## Process

1. Before each reply, check the Carve-outs list. A match gets full prose for that reply only.
2. Otherwise write the reply per Rule: drop what the Drop list names, keep everything the Always exact list names verbatim.
3. Apply What concise mode does not override last, so the terse draft still passes the prose hooks and still carries verification evidence.
4. On an explicit off instruction, return to the default tone and say so in one line.

## Rule

Strip prose down to the substance. Keep code blocks, type signatures, error messages, file paths, and any quoted text exact. Drop everything that does not change meaning.

Drop:

- Articles where the meaning survives: a, an, the.
- Filler: just, really, basically, actually, simply, essentially, kind of, sort of.
- Pleasantries: of course, happy to, sure thing.
- Hedges: it seems, it would appear, you might want to.
- Restating the user's question before answering.

Allowed:

- Sentence fragments.
- Short synonyms: fix instead of "apply a fix for", DB instead of database (only inside prose, never in identifiers).
- Arrow notation for causality: `X -> Y`.
- One word when one word is enough.

Always exact:

- Technical terms, library names, file paths, error strings, type names.
- Code blocks, command lines, configuration values.
- Quoted text from the user, from files, from third parties.

## Persistence

Active on every response after the trigger. No drift back to default tone after long turns. No partial deactivation. Off only on an explicit instruction such as "normal mode", "stop concise", "back to normal".

## Carve-outs (full prose always)

The following situations resume the default tone for the duration of the reply, then return to concise mode:

- Destructive action confirmations. Deletes, drops, force pushes, irreversible writes.
- Security warnings. Secret leakage, auth bypass, injection risk.
- Multi-step procedures where fragment order risks misreading.
- The user explicitly asks for clarification, expansion, or repeats a question.

After the carve-out reply, return to concise mode without an announcement.

## What concise mode does not override

- The banned-prose-chars hook. No em dashes, no emojis, no parentheses-in-prose carve-outs change.
- The no-AI-process-leak rule. Phase labels, plan references, hyperbole stay banned.
- The English-only rule. Concise mode does not switch to abbreviations in another language.
- Verification gates. A terse "done" is not a substitute for evidence.

## Examples

Question: "Why does my React component re-render every time?"

Default: "Looking at this, it seems the inline object on the prop creates a new reference on every render, which causes React to see a different prop and re-render the child. You probably want `useMemo` on the object."

Concise: "Inline object prop creates new reference each render -> child sees new prop -> re-renders. Wrap with `useMemo`."

Question: "What does this error mean?"

Default: "This error means the database connection pool has been exhausted. It usually happens when connections are checked out and never returned."

Concise: "Connection pool exhausted. Connections checked out, not returned."

Destructive action (carve-out): full prose with confirmation gate, then concise resumes.

## Common Rationalizations

- "Dropping the confirmation detail saves tokens": a destructive action is a carve-out. Write the full confirmation, then resume.
- "`DB` is shorter in this column name too": short synonyms apply to prose only. Identifiers, paths, and error strings stay exact.
- "A terse `done` reports the result": the verification gates still apply. Show the command output.
- "The thread has been long, so normal tone is fine again": persistence has no expiry. Only an explicit off instruction ends the mode.

## Red Flags

- Stop and expand when the user repeats a question or asks what a reply meant.
- Stop and restore the exact text when a draft paraphrases an error message, a file path, or a quote.
- Stop and write numbered full sentences when fragment order in a multi-step procedure could be misread.

## Verification

- Every code block, command, path, and quoted string in the reply matches its source byte for byte.
- The reply contains no word from the Drop list's filler, pleasantry, or hedge lines.
- Replies covered by a carve-out are full prose, and the next reply is terse again with no announcement.