Volatile content sits ahead of stable content
PrefixAudit rule ordering · v0.1.0
Why it breaks your cache
Caching is a prefix match: the first changed byte kills the cache for everything after it. The correct order is tools, then the static system prompt, then reference docs, then history, then the live user query.
How to fix it
Reorder so the prompt goes most-stable to least-stable. Anything that can change must come AFTER the last cache breakpoint.
How common is it?
Detected in 4 of 236 production system prompts (1.7%) across 16 vendors.
Estimated impact
Modelled as invalidating 0% of the cached prefix.
Is your prompt affected?
Paste it and find out. Static analysis, in-browser, nothing leaves the page.
Run the audit →