Building and Using a Personal Prompt Library
Every prompt you write from scratch is one you have written or will write again. Save what works, name, when-to-use, output note, and in six months you have prompts you actually reach for.
Lesson 4
Start at 70%, not zero.
Personal prompt library
Core principles
- Capture when: output beat prior attempts, repeatable task type, taught you framing, colleague would ask how you did it.
- Organize by use case (writing, analysis, meetings, editing) or by framework, pick one and keep it findable.
- Save three parts: full prompt with [PLACEHOLDERS], one-sentence when-to-use, one-sentence what to watch for in outputs.
- Monthly review: delete unused 60+ days; refresh prompts improved through iteration.
- Starter patterns worth customizing: first draft, tightener, plain language, pre-mortem, devil's advocate, meeting recap, tone shift, question generator, synthesizer, subject lines.
Check yourself
What three parts should every saved prompt in your library include?
Without the when-to-use, you will not reach for it when it matters. Without the what-to-watch-for, you will use it uncritically. The placeholders make it reusable without starting from scratch every time.
Do this in Copilot
Create a library (OneNote, Word, Teams). Save at least three prompts with name, when-to-use, output note.
Paste this into Copilot Chat and work through it before moving on.
First draft pattern
Draft a first version of [DOCUMENT TYPE] for [AUDIENCE]. Key points: [LIST]. Tone: [TONE]. Length: [LENGTH]. First draft only, structure and main arguments, not perfection.
- Library pattern
- Tightener: Rewrite this to be 30% shorter. Keep the main argument. Cut what does not earn its place.
- Pre-mortem: Assume this plan fails. What are the three most likely reasons? What early warning signs would appear?
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNext lesson: Prompting as a Professional Skill →
Navigate: press j for next lesson, k for previous.