Every team that starts using AI eventually creates a shared prompt document. A month later it has 140 prompts, nobody can find anything, and everyone has gone back to typing from scratch.
A prompt library that gets used is small, organised around tasks, owned by someone, and pruned regularly. Here is how to build one.
Organise by task, not by tool
People look for "write the monthly report", not "ChatGPT prompts". Group by the job:
- Client communication
- Reports and updates
- Meetings
- Analysis
- Internal documents
Five or six groups is plenty. More and people stop browsing.
Every entry has the same five fields
NAME: Monthly client report, first draft
USE WHEN: Last week of the month, data exported
PROMPT: [the prompt, with [brackets] for inputs]
EXAMPLE: Link to a good output it produced
OWNER: [role]The example output is what makes people trust a prompt enough to try it.
Store it where the work happens
A document people have to open separately gets forgotten. Better options:
- Saved prompts in the tool itself, where your AI assistant supports shared prompts.
- A project or agent per task, with the prompt built into the instructions, so nobody needs to copy it.
- A pinned page in your team channel as the index, linking to each.
Turning your five most-used prompts into projects or agents usually does more than a library of fifty.
What gets in
One rule: a prompt joins the library only after it has worked three times for at least two people. That keeps out the clever one-offs that clutter most libraries.
Prune monthly
Once a month, the owner spends fifteen minutes on:
- Removing prompts nobody has used.
- Merging near-duplicates.
- Updating prompts broken by tool changes.
- Promoting the top three to projects or agents.
Starting from zero
Ask each person for the one prompt they use most. You will have a first library of genuinely useful prompts in a week. If you want a head start, adapt our AI prompt templates for work and system prompt examples.
Questions people ask
How many prompts should a team library have?
Twenty to forty well-maintained prompts beat two hundred unmaintained ones.
Are free AI prompt libraries worth using?
As inspiration, yes. The ones that stick are usually rewritten around your team's actual work.
Who should own the library?
One person who uses AI daily. Ownership by committee means no pruning.
Where to take this next
The Work Arsenal is a ready-made library of 40 playbooks that install into ChatGPT, Claude, Gemini or Copilot. For company-wide rules every assistant follows, see The House Rules.
Leave a comment: