Anti-Patterns

Prompt Bloat

Anti-pattern: every bug fix adds a sentence to the system prompt; nothing is ever removed.

Problem

Past a few thousand tokens, the prompt starts to squeeze retrieved context and tool definitions out of the model's attention budget, prompt-cache reuse degrades because every small edit changes the cached prefix, and instructions that were added at different times begin to contradict each other. The model resolves the contradictions inconsistently, so newer rules silently override older ones for some inputs and not others. This is distinct from a hero agent, which is about scope; this is about the accretion process itself, where the prompt is treated as append-only documentation rather than as code.

Solution

Don't. Treat the prompt as code: PR review, eval gate on length, quarterly pruning sprints. Lift recurring procedures into agent-skills. Move stable rules into a constitutional charter.

When to use

  • Cite this entry when every bug fix lands as one more sentence in the system prompt.
  • You are already here if nobody can say which prompt rules are still load-bearing.
  • Put prompts under PR review with a length budget (prompt-versioning), lift procedures into agent-skills, and move stable rules into a constitutional charter.

Open the full interactive page

Diagram, neighbourhood map, code examples, related patterns and full provenance.

Related