Build Your Own Prompt Template Library
A template library is not a hundred prompts you saved from someone else. It is the work you already repeat, written down. Using someone else's templates makes the output look like their job.
How to do it
Step 1: Collect material and sort it with “Turn scattered notes into structure”
Go through the last two weeks of real work — weekly reports, emails, specs, retros — and keep one original input, one final output, and a note on where you got stuck. Hand all of it to “Turn scattered notes into structure” and sort by what the input is, what the output needs to be, and where the work stalled. Find the types that appear three times or more. Five to ten pieces usually cover most of your repeat work; a type that appeared once is probably a one-off.
Step 2: Find the slots with “Rewrite the same content for different readers”
Take one real finished piece and use “Rewrite the same content for different readers” to produce three versions: a new colleague, your manager, a client. Where the versions change is a slot; what stays the same is the fixed structure. Write the slots as square brackets and the template has a skeleton. Add one line for the role, one for the task, and three constraints; do not write it as flowing prose.
Step 3: Fix the tone with “One paragraph, three tones”
Use “One paragraph, three tones” to test tone as a slot: write the same paragraph in neutral, friendly, and restrained versions, see which sounds most like you, and check which one the brand can carry. Once decided, put the tone in the fixed part of the template so you do not renegotiate it every time. Mixed tones do more damage than plain wording.
Step 4: Clear the filler with “Strip the AI voice”
Use “Strip the AI voice” on the template itself: remove empty instructions like “please ensure” and “be sure to”, cut adjectives that carry no information, and turn “optimize it” into “change these three things”. Filler inside a template gets copied into every output, so this pass is worth more than editing a single draft.
Step 5: Finalize with “Make the draft read smoothly” and version it
Use “Make the draft read smoothly” on the template's instructions so someone else filling it in knows what belongs in each bracket. Then version it: date, what changed, why. Store three lines at the top of the file — what it is for, the last change, and the cases where it does not apply.
Prompts used
FAQ
How detailed should a template be?
Detailed enough that someone else could fill it in and get a usable result. Any more and it becomes a one-off script that breaks the moment the task changes.
Where should I keep prompt templates?
Somewhere you open every day: a fixed page in your notes app or a code repository. What matters is that it is searchable, editable, and keeps a history.
Can I just use someone else's templates?
As a starting point, yes, but replace the slots and constraints with your own. Copying them wholesale produces work that looks like the original author's, and it jams the moment your project has an unusual constraint.