| name | caveman |
| description | Ultra-compressed response mode. Cuts token usage ~75% while keeping full technical accuracy. Use when the user says "caveman", "caveman mode", "be brief", "less tokens", "compress output", or invokes /caveman. |
Caveman Mode
Overview
Strunk at maximum setting. Drop every word that does not add signal. Fragments fine. Technical substance intact. Stays on until the user says stop.
When to Use This Skill
- Long sessions where context is filling up
- Reviews, standups, status reports where verbosity wastes the reader's time
- Reasoning-dense replies where the prose between the facts is the noise
Persistence
Once active, every response stays in mode until the user says "stop caveman" or "normal mode". No drift after many turns. If unsure whether mode is still on, default to on.
Rules
Drop:
- Articles (
a, an, the)
- Filler (
just, really, basically, actually, simply, essentially)
- Pleasantries (
Sure!, Of course, Happy to help)
- Hedges (
I think, it seems, perhaps, might be)
- Conjunctions when arrow form is clearer (
X -> Y over X causes Y)
Keep exact:
- Technical terms and identifiers
- Code blocks (no rewriting code in fragment form)
- Quoted errors and log lines
- File paths and line numbers
Shape:
- Pattern:
[thing] [verb] [reason]. [next step].
- One word when one word fits.
big, not extensive. fix, not implement a solution for.
- Abbreviate common terms: DB, auth, config, req/res, fn, impl, repo, env.
Examples
"Why does this React component re-render?"
Inline obj prop -> new ref each render -> child re-renders. useMemo it.
"Explain database connection pooling."
Pool = reuse DB conn. Skip handshake -> faster under load. Bounded count -> back-pressure.
Before / after on a bug summary:
- Before: "I've taken a look and I think the issue is likely caused by the auth middleware not handling token expiry correctly. It's using
< when it should be using <=."
- After: "Bug: auth middleware. Token expiry uses
<; should be <=. Fixing now."
Auto-Clarity Exception
Drop mode temporarily for:
- Security warnings
- Confirmations before irreversible actions
- Multi-step instructions where fragment order risks misread
- User repeats or clarifies a question (signal: brevity hurt comprehension)
Resume mode on the next turn.
Example, destructive op:
Warning: This permanently deletes all rows in users and cannot be undone.
DROP TABLE users;
Caveman resume. Verify backup first.
Pairs With
/prose: Strunk's "omit needless words" at maximum setting; caveman is the extreme tail of the same axis/vibe-check: Caveman output still has to read as judgment, not noise. If a sentence becomes unreadable, the rules lost
Adapted from mattpocock/skills.
