Agent Prompts That Age Well Versus Agent Prompts That Decay

Every prompt you write has a half-life. Some decay in weeks, others last years. After two years of maintaining a personal prompt library, I have noticed the traits that separate the two, and the difference is almost entirely about specificity in the right places.

The Decay Patterns

Prompts that decay fastest share three traits:

1. Reference specific tool versions or models
2. Assume a specific project structure
3. Embed a specific style that later shifts

A prompt that says use Claude 3.5 Sonnet to refactor this to Next.js 15 with the App Router pattern reads fine in March 2025 and is obsolete by March 2026.

The Aging Patterns

Prompts that age well share three different traits:

1. Describe the outcome, not the path
2. Reference stable abstractions, not specific tools
3. Include verification criteria, not prescriptive steps

A prompt that says produce a refactor that preserves public behavior, adds tests for the boundary, and flags any deprecated patterns ages better because every clause is still true in future releases.

The Rewrite Rule

When I notice a prompt starting to produce worse output, I ask: did the prompt decay, or did my requirements change? Most of the time it is requirement drift, not decay. The prompt is still correct for the original task.

The Specificity Tradeoff

Vague prompts age well because they stay correct. Vague prompts also produce vague output. The balance is specificity where the outcome matters and generality where the tooling does. Use TypeScript strict mode ages well. Use TypeScript 5.6.2 with exactOptionalPropertyTypes does not.

The Test I Run

Every six months I re-run my tier-one prompts against a current project and judge the output. Any prompt whose output I would not ship goes into a rewrite queue. Saves me from the slow rot where every prompt is almost right and nothing is exactly right anymore.

The Survivor Library

Of my original fifty prompts from two years ago, about twelve still work without edits. Another fifteen work with minor updates. The remaining twenty three got deleted or rewritten to be less specific.

That 24 percent survival rate is worth watching. Prompts are not infrastructure. They are draft software with a shelf life.

What I Tell Other Builders

Do not treat your prompt library as permanent. Treat it as a perishable asset. Review, rewrite, delete. A small library of aging prompts is worth more than a large library full of decay.

See Anthropic's prompt engineering overview for patterns that intentionally generalize.