Most of us use LLMs by trial and error. This post gives you a structure: the building blocks of an LLM, and a reusable template for writing production prompts.

What is an LLM?

Foundation models are very large models pretrained on internet-data; that's what builds Generative AI. With a foundation model, you can adapt one pretrained model to many tasks.

A Large Language Model (LLM) is a foundation model for text, and at its core, the same FM can be used for many tasks: summarisation, classification, translation, code generation.

So what an LLM does is predict the next word (next token) in a sequence. At each step it checks the surrounding context of what it has seen so far and then produces a probability distribution over the possible next tokens. Running this in a loop produces fluent, coherent new content. So basically, an LLM gets text and returns text. The input is called the prompt and the output is called completion.

What goes into a prompt

A prompt is any input given to a generative model to produce a desired output. Prompt engineering is the practice of designing and refining those prompts to get the best possible results from the model. Refining a prompt means experimenting with the factors that influence the model's output. A vague prompt can lead to many reasonable responses; every constraint you add reduces the number of possible responses.

A well-structured prompt is usually assembled from four parts.

The instruction and context here are two of the template slots, Task and Context, we'll pull together at the end.

And best practice for writing prompts can be organised into four dimensions. Strong prompts attend to all four.

Think of a prompt like a search beam. Vague = wide beam, the model lands somewhere in a large valid region. Each constraint narrows the beam. Specificity isn't politeness toward the model; it's aiming.

Who reads the output: code or a person

The output is the more interesting part for us. An LLM's output has two possible audiences, a parser and a person, and you write a contract for each. Even when a person reads the output, "looks fine" isn't the same as "matches what I needed." When an LLM's output is read by code instead of eyes, the output is an API response and the prompt is its schema. A human forgives a messy answer; json.loads() doesn't. It either succeeds or throws. Without an explicit spec, the model decides format, length, tone, and depth, and it picks something plausible but generic. Controlling output here means moving that decision from the model to you.

Two kinds of control:

• Format control: the shape of the output (JSON keys and types; or prose vs. bullets vs. table, headings, sections).
• Behavior control: what the model may and may not do (e.g. "valid Terraform only, no comments"; or "concise executive tone, no technical jargon").

Each audience fails differently, and one of them fails silently:

A loud failure is annoying; a quiet failure is more dangerous because a subtly off-target answer can go unnoticed.

There are some mitigations you can apply for better results:

For the parser:

1. Specify the exact schema.
2. Forbid the noise.
3. Give one example of the exact shape.
4. Set temperature: 0.
5. Use native structured outputs / tool-calling.

For the person:

1. State the structure explicitly.
2. Give a length budget.
3. Name the audience.
4. List the required elements.
5. For a recurring format, show one example of the desired output.

So the point here is that prompt-only format control is a request; decode-time constraints are a guarantee. Treat the model's output as an API response, and the prompt as its schema.

Constraints and Output are template slots too: the rules that prune behavior, and the exact shape you contract for.

The system and user split

We already saw the role as one of the four dimensions of an effective prompt. It's the part lots of people forget about.

A prompt can include three types of messages: system, user, and assistant.

• System message: defines the model's behavior, rules, and overall role.
• User message: contains the request or input for the current task.
• Assistant message: previous responses from the model, used as conversational context or examples.

The "type" is usually set through the role field of each message.

The system message is the component's configuration, while the user message is the input for a specific call.

The system prompt defines persistent behavior and rules. The user message provides the variable data for that particular request. The system sets how the component behaves in general; the user message tells it what to do right now.

Why do roles work? It's not magic.

When you say, "Act as a senior security engineer," the model shifts its output toward patterns statistically associated with that kind of writing in its training data.

Likewise, "Explain this to a junior developer" pushes the model toward simpler, more educational, and more heavily explained responses.

A role doesn't give the model a real personality. It changes the probability distribution of the kind of text the model is likely to generate. This is the Role slot, the first line of the template.

Why the system/user split matters in production:

1. Caching. The system message is usually stable and reused across requests, which makes it ideal for prompt caching. Keep the system prompt consistent, and place most of the changing data in the user message.
2. Testability. The system prompt is one of the highest-leverage parts of an AI application. Treat it like code: version it, compare changes, and test it carefully.
3. Security. Trusted instructions should live in the system message. Untrusted content (user input, retrieved documents, tool outputs) should stay in the user message. When untrusted text lands somewhere the model treats as instructions, you get prompt injection. Clean separation is the first line of defense.

Showing the model examples

One good prompt gets you far. A few techniques get you further. The most useful one: showing the model examples.

In few-shot prompting, the prompt includes a few worked demonstrations. The model uses in-context learning to infer the pattern and apply it to the new input.

The few-shot examples are unit tests that double as a spec.

Why it works: the model is a pattern continuator. A few input→output pairs establish a strong, low-ambiguity pattern, and the model continues it.

When to use which:

• Zero-shot: simple, common tasks the model has clearly seen many times.
  

  [
    {
      "role": "user",
      "content": "Summarize this article in 3 bullet points."
    }
  ]
  

• One-shot: when you mainly need to pin the format.
  

  [
    {
      "role": "user",
      "content": "Convert countries to JSON.\n\nExample:\nFrance -> {\"country\": \"France\"}\n\nNow convert:\nBrazil"
    }
  ]
  

• Few-shot: classification, structured output, code style, anything with a specific schema or edge cases the model wouldn't guess.

Those worked demonstrations are the Examples slot.

In the example below, the last message is the new input; the model produces the assistant turn.

[
   {"role": "user",      "content": "Today the weather is fantastic"},
   {"role": "assistant", "content": "positive"},
   {"role": "user",      "content": "I don't like your attitude"},
   {"role": "assistant", "content": "negative"},
   {"role": "user",      "content": "That shot selection was awful"},
]

Tokens are what you pay for

LLMs are not free, and the token is the meter. For an LLM, it's the unit of both cost and latency. For most of us the mental model is familiar: tokens are network payload, and each LLM call is a billable, latency-bearing API request.

Output tokens dominate latency. The model generates text one token at a time, and each new token depends on all the previous ones, so generation has to happen sequentially.

Input works differently: the prompt is processed in a single parallel "prefill" pass, which is relatively fast (even though you still pay for those tokens).

Four levers do most of the work:

1. Compress the input

   Instead of sending entire documents, summarize them first or extract only the relevant parts. Most prompts ship context the model never reads.

2. Limit and structure the output

   Set max_tokens, prefer structured formats like JSON or arrays instead of long prose, and ask for concise summaries such as "keep under 120 tokens."

3. Use the right model for the task

   Small models are faster and cheaper for simple work like classification, routing, or extraction. Save the stronger models for tasks that actually require reasoning or synthesis.

4. Use caching

   There are two different kinds:

   Prompt/prefix caching

   Reuses stable prompt sections like system prompts, examples, or reference documents. Since the provider caches this server-side, you avoid recomputing the expensive input processing step.

   Practical implication: put stable content first and variable content last to maximize cache hits.

   Response/semantic caching

   Your own infrastructure stores previous answers and reuses them when the same or a very similar request appears again. This caches outputs, not prompts.

A Reusable Prompt Template

All that we've seen here gives us the structure to build a template to use when working on a production prompt.

The template R-T-C-C-E-O:

[ROLE]        Who the model acts as. Sets the output distribution.
[TASK]        The one thing to do, stated unambiguously.
[CONTEXT]     Inputs, background, data; clearly delimited from instructions.
[CONSTRAINTS] Rules that prune the space. Each maps to a real failure mode.
[EXAMPLES]    1–3 representative input→output pairs (for structured/edge-case tasks).
[OUTPUT]      The exact shape of the response. Schema + example if machine-consumed.

Not every prompt needs all six, but every prompt should be a deliberate subset, not an accident.

Finally, let's make the production checklist, a pre-flight pass before a prompt ships:

• Role set and matched to the task?
• Task: could a competent stranger misread it?
• Constraints: does each map to a failure mode you've actually seen? Drop the decorative ones.
• Output contract: explicit; schema + example if consumed by code?
• Format guarantee: decode-time constraint (structured output / tool call), not just a worded request?
• Examples: present for classification/structured work; diverse, consistent, minimal?
• Sampling: temperature matched to the task?
• Token budget: max_tokens capped; output format compact?
• Model: right-sized, not just "the strong one"?
• Cache-friendliness: stable content first, variable content last?
• Injection safety: instructions in the system message, data in the user message?
• Versioned & tested: in source control with a few regression cases?

So we covered six slots: Role, Task, Context, Constraints, Examples, Output, plus a pre-flight checklist. Run every production prompt through both, and you've turned a hopeful request into a tested component. A prompt is not a conversation. It's a component contract.