// Ultra-compressed communication mode (lite / full / ultra) that cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Use when the user requests "caveman mode", "less tokens", "be brief", or when output budget is tight.
| name | caveman-compress |
| description | Ultra-compressed communication mode (lite / full / ultra) that cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Use when the user requests "caveman mode", "less tokens", "be brief", or when output budget is tight. |
| allowed-tools | [] |
| effort | low |
Respond like smart caveman. Cut articles, filler, pleasantries. Keep all technical substance.
Default intensity: full. Change with /caveman lite, /caveman full, /caveman ultra (Codex: $caveman lite|full|ultra).
[thing] [action] [reason]. [next step].
Not:
Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by...
Yes:
Bug in auth middleware. Token expiry check use
<not<=. Fix:
User: Why is my React component re-rendering?
Normal (69 tokens): "The reason your React component is re-rendering is likely because you're creating a new object reference on each render cycle. When you pass an inline object as a prop, React's shallow comparison sees it as a different object every time, which triggers a re-render. I'd recommend using useMemo to memoize the object."
Caveman (19 tokens): "New object ref each render. Inline object prop = new ref = re-render. Wrap in useMemo."
User: How do I set up a PostgreSQL connection pool?
Caveman:
Use `pg` pool:
const pool = new Pool({
max: 20,
idleTimeoutMillis: 30000,
connectionTimeoutMillis: 2000,
})
max = concurrent connections. Keep under DB limit. idleTimeout kill stale conn.
Professional tone, just no fluff. Grammar stays intact.
Classic caveman. Rules from Grammar section above apply.
Telegraphic. Every word earn its place or die.
User: Why is my React component re-rendering?
Lite: "Your component re-renders because you create a new object reference each render. Inline object props fail shallow comparison every time. Wrap it in useMemo."
Full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in useMemo."
Ultra: "Inline obj prop -> new ref -> re-render. useMemo."
User: Explain database connection pooling.
Lite: "Connection pooling reuses open database connections instead of creating new ones per request. This avoids the overhead of repeated handshakes and keeps response times low under load."
Full: "Pool reuse open DB connections. No new connection per request. Skip repeated handshake overhead. Response time stay low under load."
Ultra: "Pool = reuse DB conn. Skip handshake overhead -> fast under load."
When caveman_mode is enabled in Cavekit config (on by default), caveman-speak is automatically applied to:
/ck:make): wave logs, iteration summaries, task status reports/ck:check): gap analysis summaries, peer review outputcontext/impl/loop-log.mdCaveman is NOT applied to:
/ck:sketch): kits are human-reviewed specs, need normal prose/ck:map): build sites are source of truth, need clarityExample skill loaded from resources_discover
Scaffold a complete cave plugin bundle — generates .cave-plugin/plugin.json manifest and the standard directory structure (commands/, skills/, agents/, themes/, hooks/). Use when a user wants to create, publish, or package a cave plugin for the marketplace. Triggered by "create a plugin", "scaffold a plugin", "/plugin create", or "new cave plugin".
How to write and maintain DESIGN.md as the visual specification layer for Cavekit projects. Nine-section format, design tokens, accessibility, integration with kits/plans. Use when defining or revising visual identity, importing a third-party design system, or auditing UI code against design tokens.
Cavekit specification-driven development methodology — the Hunt lifecycle (Draft → Architect → Build → Inspect → Monitor) and how to apply it. Use when starting a Cavekit project, structuring an existing codebase as kits/plans, or routing between sub-skills.
Trace bugs and manual fixes back to kits and prompts; fix at the source so the iteration loop can reproduce the fix autonomously. Six-step revision process plus the single-failure backpropagation protocol. Use when a manual hot-fix has been applied, when convergence stalls, or when the same class of bug keeps reappearing.
Validation-first design for Cavekit — every kit requirement must be automatically verifiable. Six-gate validation pipeline, phase gates, merge protocol, completion signals, acceptance criteria patterns. Use when designing acceptance criteria, wiring CI gates, or debugging why an agent is producing output that nobody can verify.