A library shelf with books and glowing teal glass blocks in the shape of hexagons.

How to build a prompt library your team will actually use

W

hen people tell me that AI texts all sound the same, they are right. The tool has read half the internet and knows nothing about you. If you ask it for “a LinkedIn post about our new project”, you get the average of all LinkedIn posts about new projects.

Better tools won't change this. Better briefing will. A prompt library is simply your briefing, written down once and shared, so that nobody starts from an empty box.

What a prompt library is

It is a document with two parts. The first part describes you: who you are, who you write for and how you sound. The second part holds a handful of ready-made instructions for the texts you write again and again.

It can live in a shared document, in your wiki or in the project function of your AI tool. Where it lives matters less than whether everyone can find it in ten seconds.

Part one: the context block

This is the paragraph you paste in before every task. It should answer four things.

  • Who we are. Two or three sentences, taken from your core message.
  • Who we write for. The reader you have in mind, in plain terms.
  • How we sound. Three or four qualities, each with a short example. “Direct: we say ‘we were wrong’, not ‘challenges were encountered’.”
  • What we avoid. Words, phrases and habits you don't want. This list does more for your texts than any other line.

If you have no written message or tone of voice yet, start there. A prompt library can only pass on what you have decided.

Part two: five prompts for recurring tasks

Don't try to cover everything. Look at what your team wrote last month and pick the five kinds of text that came up most often. For many small organisations these are a newsletter item, a social media post from a longer text, an update for funders or members, an event invitation and a summary of a long document.

Each prompt follows the same simple pattern:

  1. Task. What kind of text, for which channel, how long.
  2. Material. The facts, notes or source text. This is the part you fill in each time.
  3. Reader. Who will read it and what they already know.
  4. Form. Structure, length, and what the reader should do at the end.
  5. Limits. What to leave out, and that the tool should ask if something is missing and never invent facts.

A template to copy

Here is one I use as a starting point for a newsletter item:

Write a newsletter item of about 150 words for our monthly newsletter. Use only the facts in the notes below. Our readers are supporters who know us but don't follow the detail. Start with what happened and why it matters to them, then give one concrete example, then one clear next step. Use short sentences and no jargon. If a fact is missing, ask me and don't fill the gap. Notes: [paste here]

Put your context block in front of it, and the draft will be much closer to something you would send.

What makes people use it

I have seen careful libraries with forty prompts that nobody opened twice. Three things make the difference.

  • Keep it small. Five prompts that work are better than forty that might.
  • Build it with the people who write. Take a real task from this week, test the prompt together and improve it until the draft is usable.
  • Give it an owner. One person collects what works and removes what doesn't, about once a quarter.

One rule stays the same however good the prompts get: the draft comes from the tool, and the decision stays with you. Someone reads every text, checks the facts and takes responsibility for it.

If you would like to build your first five prompts together with your team, book a free intro call. It is one of my most requested workshops.

Smiling woman with curly blonde hair, wearing glasses, a white top, and a necklace with a round pendant.

Connect with Kristin!

Follow me on LinkedIn for practical thoughts on clear messages, AI in everyday communication and the work of small teams.

Notes from AliveCo
straight to your inbox!

@-Symbol icon in black.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Sign up for Notes from AliveCo, my newsletter.