Find the ordering mistakes that kill cache reuse
A stable prefix is what every caching scheme rewards, and it is easy to break by accident. Paste your prompt structure, one block per line, and the linter points at the volatile content and out-of-order blocks costing you cache hits.
Label each block with a hint - system, developer, tools, schema, workspace, checkpoint, retrieval, user, tool result. Nothing you type leaves your browser.
No layout problems found. Stable content leads, the latest user input is last. This is the order every caching scheme rewards.
A single request id in the system block can drop hit rate to near zero, and nobody notices until the bill does not move. The linter catches that from structure alone, before you measure it on real traffic.
The order it checks against.
Stable first, volatile last. The linter maps each labeled block onto this sequence and flags anything that puts dynamic content ahead of stable content, or stable content where it cannot cache.
- 1System policy
- 2Developer policy
- 3Stable tool bundle
- 4Response schema
- 5Workspace / tenant context
- 6Compacted checkpoints
- 7Ordered branch history
- 8Dynamic retrieval blocks
- 9Latest user input
- 10Latest tool result
The linter, answered.
Does this send my prompt anywhere?
No. The linter runs entirely in your browser. It classifies blocks and applies heuristics client-side; nothing you paste leaves the page.
What counts as a reuse-killer?
Anything that breaks a stable prefix: a timestamp, UUID, or request id near the top; dynamic content ahead of stable content; tool or schema blocks pushed below the user message; or the latest user message not appearing last.
How does it know what each block is?
It reads a hint on each line - words like system, tools, schema, retrieval, user. Label your blocks and it maps them onto the recommended order from the platform spec.
Is this a substitute for a diagnostic?
No. It catches layout mistakes from structure alone. A diagnostic measures realized capture on real traffic and confirms whether fixing the order actually moved the number.
Order it right, then measure it.
The linter catches layout mistakes from structure. A diagnostic confirms the fix on your real traffic.