Hub › Lessons › Extra lesson
Build a prompt library in Notion from the prompts you reuse
Most of us rewrite the same prompt every week: the order reply, the payment reminder, the meeting recap. Each time a rule gets lost, such as the one line that stopped the AI promising same-day delivery. A small prompt library fixes that. Keep each prompt you reuse in one Notion database, with blanks for what changes, the checks to run on the result and what went wrong before. This lesson shows the setup and gives you a tested prompt that turns any prompt you have used into a tidy library entry.
What you will be able to do: keep your reusable AI prompts in one Notion database, each with [PLACEHOLDERS] for what changes, checks for the result, known problems and a status, so you paste a proven prompt instead of rewriting it.
Step 1: Pick three prompts you reused this month (5 minutes)
- Look for repeats. Scroll back through your AI chats and find prompts you have typed more than once. Order replies, reminders and recaps are common.
- Copy the latest version. Take the one you last used, with the rules you added after something went wrong.
- Write one or two lines of notes. What went wrong, what you changed, and whether it has worked since. These notes become the "Known problems" and "Status" of the entry.
- Start with three, not thirty. A short library you use beats a long one you scroll past. You can add more later.
Step 2: Make the library database in Notion (10 minutes)
In Notion, start a new page and choose Table, or type /database on an existing page. Call it "Prompt library" and add these properties:
| Property | Type | What goes in it |
|---|---|---|
| Name | Title (already there) | A short name that starts with a verb, such as "Reply to cake orders" |
| Use when | Text | One sentence on when to use it |
| You paste | Text | The blanks you fill in each time, such as [CUSTOMER MESSAGE] |
| Status | Select | Three options: Works, Needs testing, Retired |
| Last tested | Date | The last date you used it and checked the result |
Every row in a Notion database is also a page. Open the row and paste the full prompt, the checks and the known problems into the page itself. Then add two views with the + next to the view name:
- Ready to use: filter Status is Works. This is the view you open when you need a prompt.
- Check next: sort by Last tested, oldest first. The prompt at the top is the one to try again and update, or mark Retired.
Step 3: Turn each prompt into an entry
Open a new chat, paste this prompt, and put your old prompt and your notes under the matching labels. Do this once for each prompt you picked.
Turn a prompt I use again and again into an entry for my prompt library. Do not improve the prompt or add new instructions. Only tidy it so I can reuse it. My prompt (as I last used it): My notes (what went wrong, what I changed, how it went): Write the entry with exactly these headings: Name: a short name that starts with a verb, 6 words or fewer. Use when: one sentence on when to use it. You paste: a list of what I paste in each time, one line each, written as [IN CAPITALS]. Prompt: my prompt, with every detail that changes from job to job (names, prices, dates, order or invoice numbers, the message itself) replaced by the matching [IN CAPITALS] placeholder from "You paste". Keep every instruction in my prompt word for word. Check the result: 2 to 4 things to check before I use the output. Take them only from my prompt's own rules and my notes. Known problems: what my notes say went wrong, in one line each. Write "None noted" if my notes do not say. Status: write "Works" only if my notes say it worked after my last change. Otherwise write "Needs testing". Rules: - Replace any password, bank account number, card number, phone number or email address with [REMOVED] and list it under "Removed" at the end. Do not put it in "You paste". - Do not add rules, steps, examples or advice that are not in my prompt or my notes. - If my prompt is missing, ask for it and stop.
Copy Name, Use when, You paste and Status into the matching properties. Paste the Prompt, Check the result and Known problems into the row's page. If anything is listed under "Removed", keep it out of Notion and type it in yourself when you use the prompt, or delete that line if it was a customer's detail.
Step 4: Keep it small (5 minutes a month)
- Once a month, open "Check next". Use the top prompt on a real job, read the result against its checks, and update Last tested.
- When you fix a prompt, update the entry the same day. Add the new rule to the prompt and one line to Known problems saying what it fixed.
- Retire what you no longer need. Set Status to Retired instead of deleting it, so the old version is still there if you want it back.
Worked example
A made-up home baker in Punggol has used the same WhatsApp reply prompt for months. It once promised "same-day delivery", which she does not offer, so she added one rule. The bakery, customer, phone number and prices are illustrative.
Input (illustrative)
My prompt (as I last used it): You are helping me reply to a cake order on WhatsApp. I run a home bakery in Punggol. Customer: Mrs Tan, phone 9123 4567. Her message: "Hi, can I order a 1kg chocolate cake for 12 Dec? Can you write Happy 60th Birthday Papa on it? How much and can you deliver?" My prices: 1kg chocolate cake S$68. Writing on cake is free. Delivery S$12 to anywhere in Singapore, or self-collect in Punggol. Write a short, friendly reply. Answer every question she asks. Use only my prices. Do not promise delivery times. End by asking her to confirm the order. My notes (what went wrong, what I changed, how it went): The first time, it promised "same-day delivery", which I don't do. I added "Do not promise delivery times." Used it on 3 orders since then and it was fine.
Output (as returned)
Shown word for word from the first run, in the Markdown Claude returned.
**Name:** Reply to WhatsApp cake orders **Use when:** A customer sends a cake order or enquiry on WhatsApp and you need a reply. **You paste:** - [CUSTOMER NAME] - [CUSTOMER MESSAGE] - [MY PRICES] **Prompt:** ``` You are helping me reply to a cake order on WhatsApp. I run a home bakery in Punggol. Customer: [CUSTOMER NAME], phone [REMOVED]. Her message: "[CUSTOMER MESSAGE]" My prices: [MY PRICES] Write a short, friendly reply. Answer every question she asks. Use only my prices. Do not promise delivery times. End by asking her to confirm the order. ``` **Check the result:** - It answers every question in the customer's message. - It uses only the prices you gave. - It does not promise a delivery time, such as "same-day delivery". - It ends by asking the customer to confirm the order. **Known problems:** - The first version promised "same-day delivery", which you don't do. You fixed this by adding "Do not promise delivery times." **Status:** Works **Removed:** - Phone number (9123 4567)
Her rule against promising delivery times survived word for word, and the customer's name, message and phone number came out of the prompt. One thing to fix by hand: the line still says "phone [REMOVED]". She does not need the customer's phone number in the prompt at all, so she deletes those two words before saving the entry.
What the test showed
- Instructions were kept word for word. In all nine runs on three made-up prompts, every rule we checked was still in the entry exactly as written, and our script found no added sentence in the prompt lines it could compare (lines without a placeholder).
- Private details were taken out. The bakery's customer phone number and a freelancer's bank account number were replaced with [REMOVED] in all six runs that had them. Customer names, the invoice number and the amount became placeholders.
- Status followed the notes. "Works" for the two prompts whose notes said they worked after the last change (six of six), and "Needs testing" for the one with no notes (three of three).
- It treated prices as something you paste each time. In all three bakery runs, her price list became [MY PRICES]. If your prices rarely change, put them back into the prompt, or keep them in your business memory page.
- It often added a short note after the entry. In five of nine runs it explained a choice, such as keeping "she" and "him" because it was told to copy the wording, or keeping a business registration number because it is not on the list to remove. Useful to read, but do not paste the note into Notion.
- With no prompt, it asked for one. In two of two runs with an empty prompt, it asked for it and did not invent an entry.
Watch out for
- Keep secrets out of Notion. No passwords, bank or card numbers, or customers' phone numbers in the library. Type them in when you use a prompt, if you need them at all.
- The entry is only as good as your notes. If you do not write what went wrong, Known problems will say "None noted" and Status will say "Needs testing".
- Read the prompt before you save it. Check that every rule you added is still there, and that no customer detail slipped through.
- A saved prompt still needs checking. Run the "Check the result" list every time you use it. A prompt that worked last month can give a different answer today.
Next step
Add the review prompt first
A good first entry: the review prompt from checking an AI draft against your facts. You can run it after any other prompt in your library.
Go to the review lessonKeep your facts next to it
Prompts change less when your prices and terms live on one page. Build that page in the business memory lesson and keep it in the same Notion workspace.
Go to the business memory lessonHow we checked this lesson
- On 18 Nov 2026 we ran the entry prompt with Claude Code 2.1.326 in print mode on four illustrative inputs: a home baker's order reply with notes (three runs), a freelancer's payment reminder with a bank account number and no notes (three runs), a meeting notes prompt from our meeting notes lesson with notes (three runs), and an empty prompt (two runs).
- A separate script checked every output: all seven headings present; every placeholder in the prompt listed under "You paste"; no sentence in the prompt that was not in the original; the rules we named still there word for word; no customer name, phone number, bank account number or invoice number left in; the right Status; and the right Known problems. All 11 runs passed. We also fed the script two broken entries (a phone number put back, a rule swapped and the wrong status) and it failed both. We read every output, which is where the [MY PRICES] and added-note findings above come from.
- The worked example is the first bakery run, unchanged. We did not change the prompt between runs; this is version 1.
- The Notion steps were checked against Notion's Help Center on 18 Nov 2026: Intro to databases (every item is a page; Table or /database), Database properties (Text, Select, Date) and Views, filters and sorts (the + button, filters and sorts per view). We did not build this database in a Notion workspace for this lesson.
- We tested one assistant on made-up prompts. AI output varies by tool, model and input, so read each entry before you save it.
- Where the idea came from: a How I AI episode in which a Figma product manager shows a shared folder of reusable instructions (skills) that the team kept trimming as they used it (The AI chief of staff that this Figma PM uses all day). The Notion setup, prompt and tests here are our own.
- Last reviewed: 18 November 2026.