If your prompts live in a Notion doc that nobody opens, you don’t have a library — you have a graveyard.
What “working” means
A working prompt library has four properties: people actually open it, people actually contribute to it, prompts are versioned, and prompts are tagged in a way that lets you find them in under 10 seconds.
Most libraries fail on at least two of those. Let’s go through each.
1. People open it
The number-one predictor of whether a prompt library gets used is: is it embedded into the workflow? If it lives in Notion but the team works in Linear and Slack, nobody opens it. Solve this by putting the library where the work happens. Slack slash-command. Browser extension. Inline in the CRM. Wherever the operator already is.
2. People contribute
If only one person can add prompts, the library decays. Make it explicit that any team member can submit a new prompt — and bake the submission into the regular workflow. Our default: every Friday, each operator submits one new prompt they shipped that week. Reviewed Monday. Live by Tuesday.
3. Versioning
Prompts change. The same prompt that worked last quarter may not work after the next model update. Version every prompt: v1, v2, v3. Keep older versions visible. Note the model and date each version was tested on. This sounds heavy. It isn’t. Three columns in a spreadsheet.
4. Tagging
Two-axis tagging works best. Axis one: function (sales, support, marketing, ops). Axis two: format (one-shot, system prompt, agent tool). Anything else creates clutter.
Naming conventions
We name prompts using a “verb–noun–context” pattern. “Generate-discovery-questions” beats “Sales prompt 1”. Naming is the unsung hero of usable libraries.
The review cadence
Once a quarter, audit the library. Archive prompts that haven’t been used in 90 days. Re-test prompts that have. Promote new patterns. The review takes 90 minutes and is the single highest-leverage hour your team will spend on AI tooling that quarter.
Tools we like
Notion (most teams, easy to share), Linear cycles (for ops teams), and our own Prompt Vault (for teams that have outgrown a doc). All three work — the tool matters less than the discipline around it.