Why this kit, and why now.
What this kit gives you
187 prompts that earned their place in a working library, organized by what they fix. Not a list of "best prompts". A library.
Most prompt lists die the moment they are written. Models change, codebases change, your taste changes, and last quarter's gold-standard prompt is this quarter's noise. What survives is a small, opinionated set tied to failure modes: when X breaks, this prompt. That is the format the vault uses.
Why a library, not a list
A list assumes prompts are interchangeable. They are not. A debug prompt is not a refactor prompt is not a persuasion prompt, and treating them as a flat menu is why most "best prompts" articles age into uselessness in three months.
The vault solves this with two structural rules:
- Every prompt is named for the failure it solves, not for the action it performs.
- Every prompt has a swap-out entry that tells you which prompt replaces it when the failure mode shifts.
That second rule is the difference between a vault that compounds and a vault that decays.
Who this is for
- You write prompts daily and you have stopped trusting Twitter screenshots of "the one prompt that changed everything".
- You work across Claude and GPT and you want a library that does not require you to maintain two separate stacks.
- You consult or freelance and you want the same library to travel from client to client without rebuild.
What you get
vault.json— 187 prompts, structured. Drops into Anthropic Workbench, OpenAI Playground, or any local store.anti-patterns.md— the prompts the curator deleted, and why. Reading this first saves you the most time.
Companion guide
Prompts that survive 14 client projects — the rule set behind the library, free to read.
“The "force-the-rewrite" prompt is now muscle memory.”