Keep a Personal Prompt Library and Stop Retyping Requests
Count how many times this week you typed some version of "rewrite this so it sounds friendlier but keep it short".

Count how many times this week you typed some version of "rewrite this so it sounds friendlier but keep it short". If you use an AI assistant daily, the answer is probably five or more, and each time you wrote it slightly differently and got slightly different results. A personal prompt library fixes that in about an hour of setup.
A prompt library is nothing fancy: a single document of the requests that already work for you, saved word for word, with a note on when to use them. I have kept one for two years. It holds 31 prompts, and around 8 of them do most of the work.
Why a Prompt Library Beats Starting From Scratch
When you retype a request from memory, you drop details. Last Tuesday you remembered to say "no bullet points" and "under 120 words". Today you forgot, and the assistant gave you a bulleted list of 300 words. You fix it with two follow-up messages, and the minutes add up.
A saved prompt carries the details you learned the hard way. It also makes results comparable. If you use the same wording for every meeting summary, you can tell whether a bad summary came from a messy transcript or from the tool itself. Retyped prompts hide that difference.
Where to Keep It So You Actually Use It
The best place is the one you can reach in two clicks while the assistant is open. Fancy apps fail here because opening them is one step too many.
- A plain notes document pinned in your browser or desktop. Simple, searchable, works anywhere.
- A text expander that turns a short code like ;sum into the full prompt. Fastest for the 5 to 10 prompts you use daily.
- Saved instructions inside the assistant, if your tool offers custom instructions or saved prompts. Handy, but they lock you to one product.
I use a notes file for the full library and a text expander for the top eight. If you switch tools later, the notes file comes with you.
What to Write Down for Each Prompt
A bare prompt is not enough. Six months later you will not remember why it worked or what to paste after it. Give each entry four short parts:
| Part | Example |
|---|---|
| Name | Customer reply, calm tone |
| When to use | Complaint emails where the customer is partly right |
| The prompt | The exact wording, with a marker like [PASTE EMAIL] where input goes |
| Known limits | Tends to over-apologise; delete the second sorry |
The "known limits" line is the one people skip and the one that saves the most time. It tells future you what to check before sending anything.
Build It From Your Real History, Not From Lists Online
Here is where I disagree with most advice. People start a prompt library by copying "100 best prompts" collections. Those lists are written to look impressive, not to fit your work. Most entries are long role-play setups that do little a plain request would not do.
Start instead with your own chat history. Scroll back through the last two weeks and look for three things:
- Requests you made more than twice.
- Conversations where the first answer was already good enough to use.
- Follow-up corrections you keep repeating, such as "shorter" or "British spelling".
Turn each repeated request into one entry, and fold the repeated corrections into its wording. That gives you 10 to 15 prompts that already fit how you work. If you are unsure how to phrase them well, the guide on asking an AI assistant better questions covers the basics.
Use Placeholders for Context, Not Fixed Details
A good library prompt separates the stable part from the changing part. The stable part says what you want: the format, the length, the tone, what to leave out. The changing part is the input, and it should sit in a clearly marked gap.
For example: "Summarise the notes below for a client who missed the meeting. Five sentences maximum. Lead with decisions, then open questions. No names of internal staff. Notes: [PASTE NOTES]".
Notice what is missing: the client's name, the project, the date. Those belong in the input. If you hard-code them, you end up with eleven near-identical versions. Some prompts do need background, like your company's tone or product list; keep that as a separate block you paste in when needed. The piece on giving an AI assistant context it can actually use explains how much is enough.
Review It Once a Month or It Rots
Assistants change. A prompt that needed "do not use headings" last spring might be unnecessary now, or a model update might make an old trick backfire. Put a 15 minute review on your calendar once a month.
- Delete any prompt you have not used in 60 days.
- Test your top five on a fresh example and see if the output still matches the note.
- Update the "known limits" line with anything new you noticed.
- Merge prompts that do almost the same job.
A library of 15 sharp prompts is more useful than one of 80 you never search.
Sharing a Prompt Library With a Small Team
Once your own library works, a shared version can help a team of three to ten people. Keep it in one shared document, give each entry an owner, and mark prompts that touch customer data so people know to remove names first. Resist adding everything anyone suggests; a shared library needs the same monthly pruning, and someone has to be responsible for it.
A shared library also shows where a team disagrees. When two people save different prompts for the same job, such as weekly status updates, that is a sign the team never agreed on what a good update looks like. Settle that first, then keep one prompt. In one five person office I worked with, merging six versions of a "client update" prompt into one cut the back and forth over wording in half within a month.
FAQ
How long should a saved prompt be?
Most good ones are two to five sentences. If a prompt runs past a paragraph, check whether it is really two tasks that should be split into separate entries.
Do saved prompts work across different AI assistants?
Mostly yes. Plain instructions about format, length and tone transfer well. Expect small differences in style and test your most important prompts when you switch tools.
Is it safe to store prompts with company information?
Keep confidential details out of the prompt text itself and paste them in as input only when your company's policy allows it. The library should hold instructions, not data.
Start With Five Prompts This Week
Open a new note today and title it "Prompts". Each time you catch yourself retyping a request this week, paste it in with its four parts. By Friday you will have five entries, and by the end of the month you will notice your follow-up corrections have mostly disappeared. More small habits like this one are collected under practical tips.
More in Tips and Habits
Tips and Habits
Document Templates That Stop You Rebuilding the Same File
Last March I sent a client a project update with another client's name in the footer.
Tips and Habits
Voice Dictation Habits That Make First Drafts Faster
I keep a rough log of how long writing tasks take me, and the entry that bothered me for most of last year was a weekly client...
Tips and Habits
Saved Replies That Answer Common Customer Emails in Seconds
You answer the same customer emails every week: where is my order, can I change my delivery address, do you ship abroad, how do...