Master Claude: Your AI-Powered Work Assistant / Projects and prompting
Examples, structure and a prompt library
About 10 minutes
Once a prompt works, you should never have to write it from scratch again. This lesson covers two techniques that make prompts reliable, examples and tags, and then shows how to keep a prompt library.
Technique: show, do not only tell
Anthropic's guide calls examples one of the most reliable ways to steer format, tone and structure. It recommends three to five examples that are:
- Relevant: close to your real task.
- Diverse: different enough that Claude does not copy one by accident.
- Clearly marked: wrapped in
<example>tags so Claude knows they are examples, not instructions.
Write a one-line caption for each product photo description I give you. Match the style of these examples.
<examples>
<example>Photo: blue ceramic mug on a wooden table. Caption: Morning coffee, sorted.</example>
<example>Photo: linen tote bag on a shop counter. Caption: Carries the market haul. Folds flat after.</example>
<example>Photo: three scented candles by a window. Caption: Three moods. One shelf.</example>
</examples>
Photo: hand-knitted wool scarf on a coat hook.
Technique: separate parts with tags
When a prompt mixes instructions, background and input, tags stop them blurring together. The guide suggests consistent, descriptive tag names such as <instructions>, <context> and <input>.
<context>
We are a family-run plumbing business in a small town. Most customers are over 50 and phone rather than email.
</context>
<instructions>
Rewrite the input as a short leaflet paragraph. Plain English. Include our phone number exactly as given. Do not add any services not listed.
</instructions>
<input>
[paste your rough notes here]
</input>
Templates with blanks
Turn a working prompt into a template by replacing the specific parts with labelled blanks in square brackets.
<context>
Business: [business name and one-line description]
Reader: [who will read this]
Goal: [what the reader should do after reading]
</context>
<instructions>
Write a [format] of about [length]. Tone: [tone]. Must include: [must-haves]. Must avoid: [must-avoids].
If anything needed is missing, ask me before writing.
</instructions>
<input>
[raw notes]
</input>
Build your prompt library
- Create a simple document called "Prompt library". A text file, a note app or a Google Doc all work.
- For each prompt, record: - Name: for example "Client delay email". - When to use it. - The prompt, with blanks. - Known issues: for example "sometimes too long, add a word limit".
- Store prompts you use inside one Project as a knowledge file in that Project, so you can ask:
Use the "Client delay email" prompt from my prompt library. The client is Priya, the delay is three days, the cause is a supplier problem.
- Review the library once a month. Delete prompts you no longer use.
Let Claude improve your prompts
Here is a prompt I use. Point out anything vague, anything that could be misread, and anything missing. Then give me an improved version. Keep my blanks in square brackets.
[paste prompt]
Test the improved version before you replace the old one. "Improved" is only true if the results are better.
Common mistakes
- One example only. Claude may copy it too closely. Use at least three, varied.
- Examples that break your own rules. If your rule is "under 20 words", every example must be under 20 words.
- Libraries nobody maintains. A long list of stale prompts is worse than ten good ones.
Exercise
- Pick the best prompt from Lesson 4.
- Add three varied examples in
<examples>tags. - Convert it into a template with blanks.
- Start your prompt library with this prompt and two others.
- Add the library to your Project's knowledge.