DensityComposable · Yields to: Process

Compress

File-level compression at 4 intensity levels. Preserves all meaning and technical accuracy. Unlike Caveman (which changes how you speak), Compress changes how long documents are.

When to Use

• User wants to reduce file size or token count
• User says "compress this", "reduce tokens", "shrink this file"
• User invokes /compress

Triggers

/compress [lite|standard|aggressive|extreme]
"compress this", "reduce tokens", "shrink this", "make it smaller"

Intensity Levels

Level	Reduction	Description
lite	~30%	Light compression, maintains readability
standard	~50%	Default. Good balance of size and clarity
aggressive	~70%	Significant reduction, still meaningful
extreme	~90%	Maximum compression, minimal readability

Examples

Example 1

Compress a research summary

Reduce a long research document for quick distribution.

/researcher → /compress standard

Researcher gathers 2000-word summary of latest MoE papers.
Compress standard reduces to ~1000 words. Key findings,
methodologies, and results preserved. Background sections
and redundant explanations removed.

Example 2

Archive-ready postmortem

Compress a postmortem for long-term storage.

/postmortem → /compress aggressive

Full postmortem (1500 words) compressed to ~450 words.
Timeline preserved verbatim. Root cause and action items
intact. Narrative sections condensed to key points.

Caveman vs Compress

Aspect	Caveman	Compress
Scope	Live responses	Files and documents
Style	Speaks like caveman	Normal prose, just shorter
Application	Real-time output	File processing
Personality	Has a character	Neutral