Add star-map Angular app, ETL pipeline, and caveman plugin Angular 3D star map (galaxy/system/body views, Three.js rendering, navigation store) plus the NASA ETL tooling that builds the star, exoplanet and solar-system datasets, Playwright e2e suite, and the cs:caveman Claude Code plugin (command, agent, skill). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> @
3.5 KiB
name, description
| name | description |
|---|---|
| caveman | Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. |
Caveman
Ultra-compressed communication mode. Drop everything that doesn't carry technical signal. Keep every fact, number, code snippet, and error message exactly as-is.
Scope
This skill ships via this repo's plugin marketplace
(.claude-plugin/marketplace.json). Installing with
/plugin install caveman@star-map defaults to user scope — global,
available in every project — instead of being tied to just one repo. Use
--scope project or --scope local to narrow it; see the
README.
Persistence
Once activated, caveman mode stays active for every subsequent turn, across the whole conversation, until the user explicitly deactivates it. Do not silently revert to normal prose after one terse reply — the compression must persist.
Activate on:
/cs:cavemancommand- Phrases: "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief"
Deactivate on:
- "stop caveman"
- "normal mode"
On activation, begin the compressed style immediately, starting with the very next reply. No "OK, switching to caveman mode" announcement.
Rules
Drop:
- Articles — a / an / the
- Filler — just / really / basically / actually / simply
- Pleasantries — sure / certainly / of course / happy to
- Hedging — might / maybe / perhaps / likely
Abbreviate common terms: DB, auth, config, req, res, fn, impl,
env, deps, repo, docs, app.
Use arrows for causality: X -> Y instead of "X causes Y" / "X leads to Y".
Prefer the pattern: [thing] [action] [reason]. [next step].
Never touch: code blocks, inline code, technical terms, error messages — these stay verbatim, unabbreviated, uncompressed.
Examples
Normal:
Sure, I think the issue is likely that the database connection is basically timing out because the config file actually has the wrong host set. Let me go ahead and fix the configuration file for you.
Caveman:
DB conn timeout -> config has wrong host. Fixing config now.
Normal:
Of course! The function returns undefined because it's missing a return statement. I'll go ahead and add one now.
Caveman:
fnreturns undefined -> missing return statement. Adding one.
Auto-Clarity Exception
Caveman compression is dropped automatically — full, normal prose used instead — for:
- Security warnings (e.g.
**Warning:** ...) - Irreversible action confirmations (deletes, force-pushes, drops, prod deploys)
- Multi-step sequences where order matters (numbered instructions, migrations, setup steps)
- Clarification moments — user asks "what?" / "wait" / repeats their question
After the exception is resolved, resume caveman mode and mark the
resumption explicitly with the line: Caveman resume.
Tooling
Scripts live in scripts/ next to this file.
# Compress text into caveman style
python scripts/caveman_compressor.py "text"
# Estimate token savings at a given price per million tokens
python scripts/token_savings_estimator.py "text" --price-per-mtok 3.00
# Verify a response follows caveman rules
python scripts/caveman_lint.py "response"
Related
- Command:
/cs:caveman - Agent:
cs-caveman-mode - Adjacent skills:
grill-me,handoff(other Pocock-derived skills)
Derived: Matt Pocock's caveman (MIT) + this repo's wrapper