response-compression

## Table of Contents - [Elimination Rules](#elimination-rules) - [Before/After Transformations](#beforeafter-transformations) - [Termination Guidelines](#termination-guidelines) - [Directness Guidelines](#directness-guidelines) - [Quick Reference Checklist](#quick-reference-checklist) - [Token Impact](#token-impact) - [Integration](#integration) # Response Compression Eliminate response bloat to save 200-400 tokens per response while maintaining clarity. ## When To Use - Reducing verbose output to save context tokens - Providing concise answers without losing information ## When NOT To Use - Educational explanations where detail improves understanding - First-time setup instructions needing step-by-step clarity ## Elimination Rules ### ELIMINATE | Category | Examples | Replacement | |----------|----------|-------------| | **Decorative Emojis** | `--` | (remove entirely) | | **Filler Words** | "just", "simply", "basically", "essentially" | (remove or rephrase) | | **Hedging Language** | "might", "could", "perhaps", "potentially", "I think" | Use factual statements | | **Hype Words** | "powerful", "amazing", "seamless", "robust", "elegant" | Use precise descriptors | | **Conversational Framing** | "Let's dive in", "Now that we've", "Moving forward" | Start with content | | **Transitions** | "Furthermore", "Additionally", "In conclusion" | (remove, use structure) | | **Call-to-Action** | "Feel free to", "Don't hesitate to", "Let me know if" | (remove from endings) | ...