Why this matters: Prompt engineering has moved from trial-and-error to a disciplined engineering practice. Whether you are writing system prompts, designing chain-of-thought pipelines, tuning sampling parameters, or defending against prompt injection, you need precise vocabulary to collaborate and communicate effectively.

Key prompt engineering vocabulary

Prompt structure

  • "The system prompt sets the assistant's persona and constraints."
  • "We use few-shot examples to steer output format reliably."
  • "Adding chain-of-thought improved reasoning accuracy by 18%."

Sampling & chaining

  • "Lower temperature gives more deterministic, consistent outputs."
  • "We decomposed the task using a prompt chain with three steps."
  • "The map-reduce prompt pattern handles long documents in chunks."

Security & testing

  • "Our input pipeline includes prompt injection detection."
  • "We run a prompt regression suite on every model update."
  • "Jailbreak attempts are logged and reviewed by the safety team."

Frequently Asked Questions

What exactly is a 'Few-Shot' prompt in this exercise series, and why does it matter?

In Few-shot learning, you provide the model with a few example input-output pairs within your prompt itself. This demonstrates the desired behavior without needing to explicitly train the model on a large dataset; it leverages the model's existing knowledge and guides its response toward the specific format or task you're requesting.

I'm getting inconsistent results when I use 'Chain-of-Thought' prompting. What am I doing wrong?

Chain-of-Thought (CoT) prompts encourage the model to explicitly outline its reasoning steps before arriving at an answer. Ensure you're providing clear, sequential instructions that guide the model through a logical progression of thought – simply adding 'Let's think step by step' isn't enough; it needs concrete guidance.

Can I use negative constraints in my prompts to limit the model's output?

Yes, you can! Negative constraints are instructions that tell the model *what not* to include in its response. For example, 'Generate a Python function but do not use any external libraries' or 'Describe the concept of recursion without using the word 'stack'.