BeginnerLesson 10 of 306 min read

Beginner Project: Your Personal Prompt Kit

Build a small kit of five tested prompt templates, check each for completeness and private details, try them on real work, and write a one-page guide, with a real checker.

In this lesson you will

  • Write reusable templates with blanks
  • Test them for the five ingredients
  • Check for private details and save the kit
  • Try, improve and document them

About 25 minutes

Noor builds a kit instead of starting over

Noor now has the whole Beginner course behind her. Her problem has changed. She no longer asks, ‘What is Claude?’ She asks, ‘How do I stop reinventing my requests every time?’ Each week she needs an email, a summary, a plan, an explanation and a check of a draft. She keeps writing them from scratch, forgetting what worked last time. So for her project, she builds something that lasts: a small prompt kit, a set of tested templates she can fill in and reuse. This project uses everything from lessons 1 to 9.

The brief

  • Five templates for five jobs: email, summary, plan, explain and check.
  • Each template includes the five ingredients from lesson 3: task, context, format, length and rules.
  • Each has fill-in blanks for the audience, topic and length, so it can be reused.
  • The kit passes a quality check and a privacy check, and can be saved and loaded without loss.
  • A short note says how to use each template and how to check its results.

Step 1: write templates with blanks

A template is a prompt with placeholders in curly brackets, such as the audience or the topic. You fill them in each time. Good templates keep the parts that stay the same, like the format and the rules, and leave blanks only for what changes. Keep each template to one job. A template that tries to do three jobs does none well.

Step 2: test them like software

The program below holds the five templates in a small library, fills the blanks with sample values, and then runs three checks on each result. It scores every prompt on the five ingredients, using the same style of word-pattern checker as lesson 3. It looks for leftover blanks that were never filled. And it checks the whole kit for anything that looks like a card number. Finally, it saves the library as JSON text and loads it back to prove nothing was lost.

import json, re

library = {
    "email":   "Write a friendly email to {audience} about {topic}. Use three short paragraphs, under {limit} words, and avoid jargon.",
    "summary": "Summarise the text below for {audience} in {limit} words or fewer. Use bullet points and say if anything is unclear.",
    "plan":    "Plan {topic} for {audience}. Give a numbered list of steps, no more than {limit} words, and avoid anything that costs money.",
    "explain": "Explain {topic} for {audience} in plain English. Use one short paragraph, under {limit} words, with one example.",
    "check":   "Check this draft for {audience}. List problems as bullet points, only the top {limit}, and do not rewrite it.",
}
CHECKS = {
    "task": r"\b(write|summari[sz]e|plan|explain|check)\b",
    "context": r"\b(for|about)\b",
    "format": r"\b(bullet|list|paragraphs?|numbered)\b",
    "length": r"(under \d+|\d+ words|no more than|top \d+)",
    "rules": r"\b(avoid|do not|only|say if|plain)\b",
}
values = {"audience": "parents", "topic": "the bake sale", "limit": "100"}

filled = {k: v.format(**values) for k, v in library.items()}
print("templates:", len(library))
for name, p in filled.items():
    score = sum(bool(re.search(rx, p.lower())) for rx in CHECKS.values())
    leftover = re.findall(r"\{\w+\}", p)
    print(f"{name}: {score} of 5, {len(p.split())} words, leftover {len(leftover)}")

card = re.compile(r"\b\d{13,16}\b")
print()
print("any card numbers:", any(card.search(p) for p in filled.values()))
saved = json.dumps(library, indent=1)
print("saved and loaded the same:", json.loads(saved) == library)
templates: 5
email: 5 of 5, 20 words, leftover 0
summary: 5 of 5, 20 words, leftover 0
plan: 5 of 5, 23 words, leftover 0
explain: 5 of 5, 19 words, leftover 0
check: 5 of 5, 19 words, leftover 0

any card numbers: False
saved and loaded the same: True

The kit has 5 templates, and every one scores 5 of 5, with no leftover blanks. The words per template, between 19 and 23, show that none is long. The last lines show that no card numbers appear, and that saving and loading the kit gives back exactly the same templates. Notice that the first run of this checker, when we built it, found two templates at 4 of 5: the checker looked for the word ‘paragraph’ and one template said ‘paragraphs’, and another had no word such as ‘for’ to show who it was written for. We fixed both. That is the normal process: write, test, find the weak spot, fix. A checker like this cannot say whether a template is good. It can say it is complete, which catches the most common problem.

Step 3: try each template on real work

A prompt that passes a checker still has to earn its place with real tasks. Take each template and use it for something you actually need this week. Here is the email template, filled in:

Write a friendly email to parents about the bake sale. Use three short paragraphs, under 100 words, and avoid jargon.
Subject: Bake sale on Saturday

Dear parents,

Our bake sale is this Saturday at the school hall, from 10am to 2pm. Everything on the tables is baked by local families, and the money raised goes to the library.

Could you bake or help for an hour? Just reply to this email.

Thank you, and we hope to see you there!

Read the reply with the habits from earlier lessons. Are the facts right, such as the day, the time and the place? Is the length within the limit? Does it sound like you? Did it invent anything? Fix and save what works. Where a template fails, improve the template, not just the one reply, so the next use benefits.

Step 4: write a one-page guide

  1. List each template with one line on when to use it.
  2. For each, note what to check afterwards: facts, length, tone, private details.
  3. Add three rules for yourself: no private details, check numbers and names, and start a new chat when it drifts.
  4. Keep the guide and the templates somewhere easy to find, such as a project’s knowledge files or a note on your phone.
  5. Review the kit every month. Remove what you never use and improve what you do.

Your finished-kit checklist

  • Does every template state its task, context, format, length and rules?
  • Are the blanks clear, and does each template do one job?
  • Has each been tried on real work and improved?
  • Is there nothing private in the kit?
  • Is there a short guide on how to check each result?
  • Can you find it in under a minute?
Common mistake: a template graveyard

Collecting dozens of templates you never use. A kit of five that you use weekly beats fifty that you forgot. Add a new template only when you notice yourself repeating a request a third time.

Beginner level complete

You have now finished the Beginner level of Claude basics. You can set up, converse, prompt, give context, shape replies, edit, check facts, organise work and protect your privacy. Next come deeper skills, such as longer workflows and analysis.

Build your own kit of five templates for jobs you really do. Run the five-ingredient check from lesson 3 on each, try each on real work, and fix the weakest. Write the one-page guide, and use the kit for a week.

Practice for this lesson

Check what you learned

Five quick questions. Pick an answer and you will see straight away whether it is right and why.

What is a prompt template?

  1. A prompt with blanks you fill in each time
  2. A kind of font
  3. A chat error
  4. A file type

A template keeps what stays the same and leaves blanks for what changes.

What can the checker tell you about a template?

  1. Whether it is perfect
  2. Whether it is complete
  3. Whether it is funny
  4. Whether it is true

A checker finds missing ingredients, but cannot judge quality or truth.

What should you improve when a template fails on real work?

  1. Nothing
  2. The computer
  3. The date
  4. The template itself

Improving the template means every later use benefits.

Why scan the kit for card numbers?

  1. Cards are long
  2. Private details should never be in templates
  3. Templates need cards
  4. It speeds up Claude

A shared or saved kit should hold no private details.

When should you add a new template?

  1. Every day
  2. Never
  3. Before reading anything
  4. When you have repeated a request a third time

Repeated requests are the signal that a template will pay off.

Summary

  • A kit of tested templates saves time and improves results.
  • A checker finds incomplete prompts but cannot judge quality or truth.
  • Improve the template when it fails, not only the reply.
  • Keep the kit small, private-detail free and reviewed.

Next lesson

The Intermediate level of Claude basics begins with lesson 11.

Questions

How many templates should I have?

Start with five jobs you do every week. Add more only when you notice a repeated request.

Where should I keep my kit?

Somewhere you can find in a minute: a project's knowledge files, a notes app, or a document. Keep private details out of it.

Do the templates work in other AI tools?

Mostly yes. The five ingredients are general. Details such as projects and files differ between tools.

Progress is saved in this browser.