Variables and Examples
Use placeholders and few-shot examples to make prompts reusable.
Learning Objectives
- Write descriptive variables that make prompt templates portable.
- Choose examples that demonstrate quality, tone, and structure.
- Use contrast examples to reduce repeated failure modes.
Reusable prompts need variables
Variables turn a one-off request into a reusable workflow. A good variable name tells the user exactly what source material belongs there.
Use `[CUSTOMER_CALL_NOTES]`, `[CRM_CONTEXT]`, or `[SUPPORT_TRANSCRIPT]` instead of generic labels like `[TEXT]`. Specific names reduce misuse and make the prompt easier for teammates to adopt.
Examples show quality
Examples are most useful when the task has judgment in it: tone, specificity, structure, or quality threshold. A strong example teaches the model what a good answer looks like.
Use one or two compact examples. If the prompt keeps producing the wrong style, add a bad example and explain why it fails. Contrast makes the quality bar easier to follow.
Input: [GOOD_SOURCE_EXAMPLE]
Output: [GOOD_TARGET_EXAMPLE]
Why this works: It uses evidence, keeps the answer short, and names the next action.Examples
Descriptive variable naming
Use [CUSTOMER_CALL_NOTES] instead of [TEXT] so another teammate understands what source material belongs in the prompt.
Practice Exercise
Template a repeatable task
Choose a weekly workflow and turn it into a prompt template with at least four named variables and one example input.
- Variables describe source material clearly.
- The example matches the real workflow.
- The template can be reused without rewriting the instructions.
Mini Prompt Templates
Prompt Template Editor
You are a prompt editor. Original prompt: [PASTE_PROMPT] Task: Convert it into a reusable template with descriptive bracket variables and one example input. Format: Template, Variables, Example, Why it works.