Build a prompt library your team can share

Why a library beats everyone’s chat history

Right now your team’s best prompts probably live in one person’s chat history. Everyone else starts from a blank box, results depend on who typed what, and when a price or policy changes, nobody knows which prompts still carry the old one.

A shared library fixes that. It isn’t a new tool, just a plain doc kept where your team already works, such as a shared drive in Google Workspace or Microsoft 365, with one entry per task. Nobody needs to be good at prompting to use it; they only need to know which entry to open.

Good candidates are tasks someone does every week, where a first draft saves real time and the check is clear: customer replies, meeting follow-ups, summaries, report drafts.

What goes in an entry

A prompt on its own isn’t enough for someone else to reuse. The example matters most: it shows a teammate what a good result looks like, so they can spot one that isn’t, and it sets the level of detail you expect.

Name each entry after the job it does (“Reply to a late-delivery email”) rather than the tool, and group entries by team. Each one needs:

• A plain name and one line on when to use it
• The prompt, with anything that changes each time in [square brackets]
• An example of a good result, with names and customer details removed
• The human check for that task
• An owner, the date it was last tested, and which assistant it was tested in

Keep it small, and keep it alive

Start with three prompts that already work, not thirty you hope will. A 15-minute team session does it: everyone brings one prompt that saved them time, and you keep the best. Add entries when someone reuses a prompt successfully, and retire any that nobody has used in a couple of months.

Retest the top entries when your AI tool updates or a policy changes. The same prompt can behave differently after an update, and an old example can quietly teach an old price. Each entry’s owner does that and updates the last-tested date; one person looks after the library as a whole.

Put two rules at the top of the doc. First, no customer names, personal details or passwords in prompts or examples, because the library gets copied and shared. Second, every prompt that writes for customers asks the AI to mark anything it’s unsure of with [CHECK].