Cuts spec documentation down to about 25% of original token count while keeping precision intact. Drops articles, filler words, and auxiliary verbs, then leans on symbols like → for "leads to" and ∴ for "therefore". Works well for SPEC.md files, invariants, and bug tracking tables where you're writing for yourself or your team, not external stakeholders. Leaves code, paths, error strings, and identifiers completely untouched. The compression is aggressive but reversible in your head, which makes it useful for high-churn design docs where you're iterating fast and token budgets matter. Switch back to prose when writing commits, PRs, or anything a non-team member will read.
npx skills add https://github.com/juliusbrussee/cavekit --skill caveman