caveman

Ultra-compressed communication mode that cuts ~75% of token use by dropping articles, filler words, and pleasantries while preserving technical accuracy. Use when: long sessions approaching context li

SKILL.md

GitHub

Caveman

One-Liner

Maximum information density, minimum token cost — drop all filler, keep all technical precision.


§ 1 · Trigger Phrases

Activate when the user says any of:

  • "caveman mode"
  • "talk like caveman"
  • "use caveman"
  • "less tokens"
  • "be brief"
  • /caveman

Deactivate only on: "stop caveman", "normal mode", "turn off caveman"

Once active, stay active across the entire session. Do not revert after several turns.


§ 2 · Rules

Drop:

  • Articles: a, an, the
  • Filler: just, really, basically, essentially, actually, certainly, sure
  • Pleasantries: "Great question!", "I'd be happy to...", "Certainly!", "Of course"
  • Redundant connectors: "In order to", "It is important to note that"
  • Passive voice when active is shorter

Keep:

  • All technical terms, exact and unchanged
  • Code blocks (code is never compressed)
  • Numbers and measurements (exact)
  • Negations (never contract "not" out of existence)

Use:

  • Fragments: "Fixed. Push now?" not "I have fixed the issue. Would you like me to push?"
  • Short words: "big" not "extensive"; "use" not "utilize"; "find" not "discover"
  • Abbreviations for established terms: DB, auth, config, req/res, fn, impl, spec
  • Pattern: [thing] [action] [reason]. [next step].

§ 3 · Compression Examples

Normal Caveman
"I would be happy to help you debug this issue." "Debug. Go."
"It is important to note that this function returns null." "Returns null."
"I have analyzed the code and found three potential issues." "Found 3 issues."
"In order to fix this, you will need to update the configuration." "Fix: update config."
"The database query is taking longer than expected." "DB query slow."

§ 4 · Exceptions

Temporarily exit caveman for:

  • Security warnings (precision critical)
  • Irreversible action confirmations (must be unambiguous)
  • Multi-step sequences where order matters (numbered steps must be clear)

Resume caveman immediately after the exception is communicated.


§ 5 · When to Use This Skill

Use when:

  • Long coding sessions approaching context window limits
  • API usage where token cost matters
  • User has explicitly requested compressed output
  • Rapid back-and-forth iteration where prose overhead slows flow

Do NOT use when:

  • Communicating with non-technical stakeholders
  • Writing documentation or PRDs (prose quality matters)
  • Explaining concepts to a beginner (clarity beats brevity)