TL;DR: Mixed format styles across your AI config files force the LLM to re-parse syntax before it can reason. Switching to a single format reclaimed enough context to notice. One rule change. Five minutes.
I had 6 different config files. Each used a different format style.
Some used YAML frontmatter. Some used markdown tables. One used bullet lists with bold labels. Another used ## sections with -> arrows. Every time the AI agent switched from one file to another, it paid a parsing tax — figuring out "how do I read this one?" before it could even start "what does this say?"
The Tax You Don't See
When your AI agent reads your config, it's not just "reading." It's parsing. Every file format switch costs tokens. Not a lot per switch — but multiplied across 50 sessions, with 6+ files per session:
6 files × 3 format switches avg × 50 sessions = 900 unnecessary parsing events
That's context budget burned on how to read, not what to read.
The Data Point
This isn't hypothetical. Across multiple config files spanning different tools, the formats had drifted — YAML here, markdown tables there, nested bullets elsewhere. Consolidating to a consistent style cut total config size measurably and produced noticeably more consistent agent behavior.
The LLM wasn't following rules worse because the rules were bad. It was following them worse because it was burning attention on format translation.
The Fix
One rule. Add this to your config:
Use exactly one format style across all config files. Pick one (markdown headers + bullet lists, or YAML frontmatter, or structured tables) and stick to it. The LLM pays a parsing tax every time you switch.
That's it. No tooling. No scripts. Just discipline.
Why Nobody Talks About This
Most AI agent advice focuses on what to write — better prompts, better rules, better examples. Almost nobody talks about how to write it — the format that carries the message.
Think of it as signal-to-noise ratio. Your rules are the signal. The format is the noise floor. Lower the noise, and the same signal becomes clearer.
Going Further
If you want the full config overhaul, I open-sourced a DeepSeek + Claude Code starter kit with consistent formatting baked in — 9 agents, 7 rules, zero format inconsistency.
I also contributed this exact finding as an anti-pattern to the agent-best-practices repo. It's now part of their official guidance.
How many config files does your AI agent read? Count them. Are they all the same format? If you have 3+ files with different styles, pick one format right now and convert the others. Your next session will be smarter for it.
Related: DeepSeek V4 + Claude Code starter kit • LLM compaction isn't linear
Top comments (0)