What is 'prompt rot' and what causes it to silently degrade production LLM applications over time?
Prompt rot is the silent quality decay of a production prompt whose code never changed, driven by model upgrades, retrieval drift, and new user behaviors the prompt was not built for.
Imagine writing a recipe for a friend who cooks for you every weekend. The recipe stays the same on paper, but your friend slowly switches brands, the grocery store rearranges its shelves, and you start inviting guests with new diets. Nothing on the page is wrong, yet dinner gets worse week by week. Production prompts decay the same way. The model behind the API gets a quiet upgrade, the documents flowing in shift toward new topics, and users start asking things the prompt was never designed to handle. Nobody touched the prompt, but output quality slides.
Detailed answer & concept explanation~5 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
3 min: the three drift axes + regression-CI mitigation + version pinning + golden-set refresh cadence + production-trace feedback loop.
Real products, models, and research that use this idea.
- Teams using Claude Opus 4.7 via the Anthropic API pin a dated snapshot in production and re-baseline their golden eval whenever they roll forward, because behavior on format strictness shifts between snapshots.
- Perplexity continuously re-evaluates synthesis prompts against fresh web retrievals, since the source distribution shifts faster than any static eval set could track.
- GitHub Copilot Chat samples production traces into a regression bucket, then weights recent failures into the next golden-set refresh.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you detect prompt rot before users complain?
QWhat changes if you switch from a pinned model to a floating one?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Assuming a prompt that worked at launch will keep working forever, because no code changed and tests still pass on the original golden cases from a year ago.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.