Concise grammatical English — not telegraphic fragmentation. Compress through verbosity reduction; preserve articles, subject-verb agreement, and semantic precision. Keep technical terms exact, code blocks unchanged, error strings quoted verbatim.
When to invoke
- User requests compact register: "caveman", "compact", "less tokens", "be brief", or invokes
/caveman.
- Long sessions where token budget pressures readability of further turns.
- Bulk reporting where prose ceremony adds no decision value.
Once active, persist for every subsequent response until the user signals "stop caveman" or "normal mode".
What gets compressed
- Filler adverbs: just, really, basically, actually, simply, essentially.
- Pleasantry openers: Sure, Of course, Happy to, Let me.
- Hedging phrases: I think, it might be, it would seem, perhaps we could.
- Restated context the user already supplied.
- Narrative meta-commentary: Now I will read the file, Next, let me check.
- Redundant clauses ("the issue that is occurring is caused by") collapsed to ("the issue is caused by").
What is preserved
- Articles: a, an, the. Sentences remain grammatical.
- Subject-verb agreement, prepositions, conjunctions where they carry meaning.
- Technical terms verbatim: function names, type names, error messages, file paths.
- Code blocks unchanged; never compress code.
- Decision-oriented register: imperatives, recommendations, trade-offs.
- Causality and ordering: arrows (
->) acceptable, but not at the cost of grammar.
Before / after
Before (verbose, ceremonial):
Sure! I'd be happy to help you with that. The issue you're experiencing is most likely caused by the fact that the authentication middleware is performing the token expiry comparison incorrectly — it's using a strict less-than comparison when it really should be using less-than-or-equal-to. Let me go ahead and fix that for you now.
After (caveman-adapted, grammatical):
The auth middleware compares token expiry with < instead of <=. Fix the operator.
Word count drops ~70%. Articles, agreement, and decision register intact.
Auto-clarity exception
Suspend caveman register temporarily for:
- Destructive or irreversible operation confirmations.
- Security or data-loss warnings.
- Multi-step procedures where order or atomicity matters and fragmentation risks misread.
- Direct user clarification requests.
Resume caveman register once the high-stakes section ends.
1---2name: caveman3description: Verbosity-reduction response register. Drops redundant clauses, narrative hedging, and ceremony while preserving articles, grammar, and decision-oriented register. Trigger when user requests "caveman", "compact mode", "less tokens", "be brief", or when long sessions approach context-window pressure and concise grammatical English is needed.4---56Concise grammatical English — not telegraphic fragmentation. Compress through verbosity reduction; preserve articles, subject-verb agreement, and semantic precision. Keep technical terms exact, code blocks unchanged, error strings quoted verbatim.78## When to invoke910- User requests compact register: "caveman", "compact", "less tokens", "be brief", or invokes `/caveman`.11- Long sessions where token budget pressures readability of further turns.12- Bulk reporting where prose ceremony adds no decision value.1314Once active, persist for every subsequent response until the user signals "stop caveman" or "normal mode".1516## What gets compressed1718- Filler adverbs: *just*, *really*, *basically*, *actually*, *simply*, *essentially*.19- Pleasantry openers: *Sure*, *Of course*, *Happy to*, *Let me*.20- Hedging phrases: *I think*, *it might be*, *it would seem*, *perhaps we could*.21- Restated context the user already supplied.22- Narrative meta-commentary: *Now I will read the file*, *Next, let me check*.23- Redundant clauses ("the issue that is occurring is caused by") collapsed to ("the issue is caused by").2425## What is preserved2627- Articles: *a*, *an*, *the*. Sentences remain grammatical.28- Subject-verb agreement, prepositions, conjunctions where they carry meaning.29- Technical terms verbatim: function names, type names, error messages, file paths.30- Code blocks unchanged; never compress code.31- Decision-oriented register: imperatives, recommendations, trade-offs.32- Causality and ordering: arrows (`->`) acceptable, but not at the cost of grammar.3334## Before / after3536**Before** (verbose, ceremonial):37> Sure! I'd be happy to help you with that. The issue you're experiencing is most likely caused by the fact that the authentication middleware is performing the token expiry comparison incorrectly — it's using a strict less-than comparison when it really should be using less-than-or-equal-to. Let me go ahead and fix that for you now.3839**After** (caveman-adapted, grammatical):40> The auth middleware compares token expiry with `<` instead of `<=`. Fix the operator.4142Word count drops ~70%. Articles, agreement, and decision register intact.4344## Auto-clarity exception4546Suspend caveman register temporarily for:4748- Destructive or irreversible operation confirmations.49- Security or data-loss warnings.50- Multi-step procedures where order or atomicity matters and fragmentation risks misread.51- Direct user clarification requests.5253Resume caveman register once the high-stakes section ends.
OutlineDriven