Build Your Prompt Library
10 min read
Buried in your chat history is the best prompt you've ever written. It nailed the tone, it covered the edge cases, it produced something you actually sent — and you'll never see it again, because it's under forty conversations titled "New chat." Good prompts die in scrollback. The difference between a founder who uses AI and a business that uses AI is a place where the good prompts live.
From prompt to template
Any prompt that worked once can become a template. The recipe: keep the structure and the standing rules, and swap everything specific to that one situation for [BRACKETED VARIABLES] in caps, so the blanks are impossible to miss.
Take Dev's review-reply prompt from Sales and Customer Messages. As a template, it looks like this:
REVIEW REPLY — v3, updated July 2026
Context: I own [BUSINESS + LOCATION]. A customer left this review:
[CUSTOMER MESSAGE — paste it word for word]
What actually happened: [WHAT ACTUALLY HAPPENED — just the facts,
including anything we already did to fix it]
Here are two past replies so you can match my tone:
[PASTE TWO PAST REPLIES — keep these saved with the template]
Task: Draft a public reply, four sentences or fewer.
Offer: [OFFER, IF ANY — write "none" if none]
Outcome I want: readers see an owner who takes feedback seriously.
Outcome to avoid: corporate tone, defensiveness, or arguing with
the customer's version of events.Anyone on Dev's team can run this on a Tuesday without him. The permanent parts — the tone rules, the outcome lines, the skeleton from The Five-Part Prompt — stay written out in full. Only the brackets change.
Where it lives, what it's called
The tool barely matters. A Google Doc, a Notion page, a pinned note in the team chat — pick whatever your team already opens. The naming matters a lot. "Marketing prompt 2" helps nobody during a March panic; name every template after the job it does, in caps, so it can be found by someone who's stressed: REVIEW REPLY, WIN-BACK EMAIL, MEETING NOTES TO ACTIONS.
Then add a "last updated" date to each one and treat it like a smoke-detector battery. Priya learned this the annoying way — her studio's win-back template kept offering a class pass she'd discontinued in April, and two lapsed members wrote back asking for it. Templates go stale exactly as fast as your prices, offers, and staff do. The maintenance rule is simple: the second time you make the same manual fix to a template's output, bake that fix into the template itself.
Test before you trust
Before a template earns a spot in the library, run it on a real case you've already handled — one where you know what good looked like, because you wrote the answer yourself. If the draft lands within an edit or two of what you actually sent, it's in. If it doesn't, fix the template, not every future output. A template you haven't tested isn't an asset yet; it's a guess with a nice name.
A starter library
Five templates cover a surprising share of what most businesses write. Build them in this order, one per week, each time the task comes up anyway:
| Template | When to use it |
|---|---|
| REVIEW REPLY | Any public review, glowing or brutal |
| CUSTOMER BAD NEWS | Price increase, delay, policy change |
| MEETING NOTES TO ACTIONS | After any meeting with more than two people |
| JOB POSTING | Any role, written in your voice, not HR's |
| PROMO BATCH (10 OPTIONS) | Whenever marketing needs something this week |
Nothing here requires software you don't own or skills you don't have — just the discipline to save what worked while it's still on screen.
Try it now
Scroll your AI chat history for the best output you got this month. Copy the prompt that produced it, swap the one-time specifics for [BRACKETED VARIABLES], put a job-shaped name and today's date at the top, and save it where your team can find it. One down, four to go.