Prompt Bloat

Prompt Bloat is an anti-pattern where developers pack dozens of disparate instructions, generic style guides, defensive guardrails, and full API references into an LLM’s system prompt.

Symptoms of Prompt Bloat

• Instruction Shadowing: Long rule lists cause newer rules to override or contradict earlier directives.
• High Per-Turn Latency & Cost: Every single turn re-processes hundreds of bloated prompt tokens before reading the user’s message.
• Sycophancy & Hedging: Models weighed down by overly cautious instructions spend more time explaining why they can’t do something than executing the code.

How to Kill Prompt Bloat

1. Apply the Defensibility Test: For every sentence in a prompt or instruction file, ask: “Can I defend why this is here with a real failure case?” If not, delete it.
2. Move Docs to the Filesystem: Keep system prompts minimal and point to local files (docs/, skills/, CONTEXT.md) that the agent loads only when needed.
3. Use Tool Definitions: Replace large textual output formats with structured tool calling schemas (e.g. JSON schema parameters).

Related

context rot, progressive disclosure, agents md spec, context engineering.