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.

## 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) |

### PRESERVE (When Appropriate)

| Category | Example | When to Use |
|----------|---------|-------------|
| **Status Indicators** | `[pass] [fail] [warn]` | In structured output, checklists |
| **Technical Precision** | Exact error messages | When debugging |
| **Safety Warnings** | Critical info about data loss | Always preserve |
| **Context Setting** | Brief necessary background | When user lacks context |

## Before/After Transformations

### Example 1: Opening Bloat

**Before** (68 tokens):
```
Great question! I'd be happy to help you understand how this works.
The bloat detector is a powerful tool that analyzes your codebase
and provides comprehensive insights into potential issues...
```

**After** (28 tokens):
```
The bloat detector analyzes codeba