Restricted channel

Access required

This handbook is gated. Enter the access code to continue.

Incorrect code — try again.
Operator's
Edition
Handbook no. 04 — issued for general use

Prompting

Signal, structure & safety for talking to machines

Every exchange with a generative AI system begins with a transmission you write yourself. This handbook covers how to send a clear signal, what happens behind the receiver, and how to spot someone jamming the frequency.

Begin briefing ↓
01 — Briefing

Two jobs, one conversation

A prompt is the plain-language instruction handed to an AI system — the closest thing it has to a control panel. How well that instruction works depends on two different kinds of work, and most operators only ever touch one of them.

User-facing

Prompt design

The craft of wording an instruction so the model understands exactly what is being asked of it.

  • Structuring instructions deliberately
  • Providing worked examples
  • Reusing proven prompt templates
  • Applying shot-prompting techniques
This is the handbook you're holding.
System-facing

Prompt engineering

The technical work that happens behind the interface, usually invisible to whoever's typing.

  • Connecting external data sources
  • Wiring up APIs
  • Tuning parameters like temperature
  • Configuring supporting system code
Usually someone else's job — but it shapes what words alone can do.
The split isn't official terminology — treat it as a way to separate "what I type" from "what's built behind the scenes."
02 — Building blocks

Anatomy of a transmission

Every prompt is built from the same four parts, in different proportions. Learn to spot each one and you can debug a weak prompt by asking which piece is missing.

Action

Instruction

The action that should be performed.

"create" · "summarize" · "classify" · "analyze" · "rephrase"
Background

Context

Additional information the model might not be aware of — examples, demonstrations, or the role and behavior it should adopt.

Material

Input data

The data the task should be performed on.

text · spreadsheet · dataset · image
Shape

Output format

The desired shape or style of the response, and how long it should run.

list · table · tweet · blog post · word/character count
These four blocks map onto the switches in the builder ahead: instruction becomes the task, input data folds into context, and output format keeps its name. Same anatomy, relabeled for the field.
03 — Field techniques

Five ways to phrase a request

Wording alone can change how a model reasons through a problem. These techniques control how much guidance you give and how visible the model's thinking becomes.

Shot protocol

How many worked examples you include before asking for the real thing. More examples usually means a more predictable format — though, oddly, whether those examples are factually correct rarely changes the result. The model copies the pattern, not the facts.

Describe ten popular movies using only emoji.
Field note — Zero-shot trusts the model to infer the format. One-shot gives it a single anchor. Few-shot locks the pattern down — useful when format matters more than creative freedom.

Chain of thought

Ask the model to narrate its reasoning before landing on an answer. The output becomes easier to follow and easier to check — you can see exactly where the logic might have gone wrong.

A bakery sells 3 cookies for $2. How much for 12 cookies? Explain your reasoning step by step. 12 cookies is 4 groups of 3 cookies. Each group of 3 costs $2. 4 groups × $2 = $8.
Field note — Most current reasoning models already do this by default — the instruction just makes the process visible instead of hidden.

Self-consistency

Run the identical prompt several times and compare the answers instead of trusting the first one. The response that turns up most often is treated as the most likely to be correct — strength in numbers, not in any single attempt.

Run 1Answer: $8
Run 2Answer: $8
Run 3Answer: $9
Field note — Builds directly on chain-of-thought: more reasoning paths means more chances to catch a wrong turn. Here, $8 wins on majority.

Tree of thought

Push chain-of-thought one step further: instead of one line of reasoning, the model develops several independent perspectives in parallel — like a panel discussion — then merges them into one recommendation.

Imagine three experts — a sustainability manager, a financial analyst, and a marketing strategist — discussing whether to launch a Green Office initiative. Let each share their reasoning, then give a joint recommendation.
Field note — Borrows from how decisions work on real teams: a mix of viewpoints tends to beat a single train of thought.

Prompt chaining

Split a large task into a sequence of smaller prompts, where each response becomes the input for the next one. Better suited to long or multi-stage work than a single oversized instruction.

Step 1Summarize the 10-page report.
Step 2Turn the summary into 5 talking points.
Step 3Write a 30-second script from those points.
Field note — Treat it like relay communication: each leg only has to carry the signal to the next station, not all the way to the destination.
04 — Transmission builder

Assemble a working prompt

Flip the switches to add or remove parts of a request and watch the transmission take shape. Task stays live — everything else is what turns it from noise into signal.

Scenario: requesting a product-launch email
[Role]Tell it who it's acting as.
[Context]Give the background a stranger would need.
[Task]The actual ask — always on the air.locked · core signal
[Format]Length, structure, and tone of the output.
[Example]Show, don't just tell, when format is unusual.
[Constraints]What to avoid, as clearly as what to include.
Readable signal
05 — Modality playbook

Six channels, one discipline

Role, task, context, and format hold steady whether you're typing plain text, dropping in a screenshot, generating an image, transcribing a call, talking out loud, or pasting code. What changes is which details matter most on each channel.

Text & vision

Two closely related channels: plain text in and text out, or an image, screenshot, chart, or scanned document in with text out. Both lean on the same discipline — name the role, the task, and the audience before asking for output.

  • Define the role and state the task plainly
  • Give context and supply the source material
  • For images, say what to focus on and how much detail you need
  • Separate observation from interpretation, especially with charts
  • Specify the output format and ask for assumptions or risks
Customer feedback analysis
Act as a customer insights analyst. Find the recurring themes in the feedback below, rank them by frequency and impact, and pull out a representative quote for each. Flag anything urgent. Return a table: Theme, Evidence, Frequency, Impact, Recommended action, Owner, Urgency.
UX screenshot review — vision-to-text
Act as a senior UX consultant reviewing this screenshot. Describe what's on screen, then separately list usability issues, confusing labels, and missing calls to action. Rank each fix by expected impact on users. Return a table: Issue, Evidence from screenshot, Impact, Recommendation, Priority.
Field note — Vision-to-text breaks the same way text prompting does when the role or audience is missing — the model can describe a screen, but it can't guess what "better" means for your product without being told.

Image & video

Written description in, a visual or motion asset out. The same descriptive ingredients — subject, setting, style, lighting, mood — apply whether you're asking for a still image or a short clip.

  • Describe the subject and environment clearly
  • Set style, mood, lighting, camera angle, and format
  • Say what should not appear in frame
  • For video, describe sequence, pacing, camera movement, and duration
  • Don't stack too many competing ideas into one prompt — sketch the concept, then refine
Image prompt skeleton
Create an image of [subject] in [setting], doing [action], in the style of [style]. Use [composition], [lighting], and [mood]. Format: [aspect ratio]. Avoid [elements to exclude].
Video prompt skeleton
Create a [duration] video showing [subject] in [scene]. The subject [action]. Camera [movement]. Lighting is [lighting]. Mood is [mood]. Style is [style]. Avoid [elements to exclude].
Field note — Treat the first draft as a sketch, not a final cut — lock the concept first, then go back and tighten lighting, mood, and framing in a second pass.

Audio-to-text

Spoken input in, written output out — transcripts, summaries, sentiment, or extracted action items.

  • Say whether you want a verbatim transcript or cleaned-up notes
  • Ask for speaker identification when it matters
  • Request timestamps for key moments
  • Decide whether filler words should survive the cleanup
  • For business calls, ask for decisions, objections, risks, and next steps
Sales call analysis
Analyze this sales call. Summarize the customer's situation, list explicit needs and implied pain points, and pull out any objections. Rate buying intent High, Medium, or Low and recommend the next move. Keep what the customer actually said separate from your read on it, with short quotes as evidence.
Field note — The split between verbatim and interpretation matters most here — a call summary that quietly blends the two is much harder to trust later.

Audio-to-audio

Speaking with a model and getting a spoken response back — coaching, rehearsal, role-play, language practice.

  • Set the interaction style up front: interrupt, wait, coach, or role-play
  • Specify how long responses should run
  • Define turn-taking rules
  • For coaching, ask for feedback after every turn
  • For role-play, name the persona and how difficult it should be
Skeptical client role-play
You're a skeptical SME managing director. I'm pitching you a discovery workshop. Push back on cost, timeline, data privacy, and unclear ROI — don't make it easy for me. After each of my answers, score it 1–10 with one improvement note. Keep going until I ask you to stop, then summarize my strongest and weakest moments.
Field note — The scoring loop is what makes this useful — without a structured response after each turn, the role-play just becomes conversation, not practice.

Code-to-code

Code in, code out — generating, debugging, refactoring, translating, or testing.

  • Paste the full relevant code, not just the error
  • Name the language and version
  • State expected behavior versus actual behavior
  • Include the exact error message
  • Ask for test cases
  • Never paste secrets, API keys, or production data
Debug a Python function
Act as a senior Python engineer. Here's the function: [paste]. Expected: it should total revenue by customer. Actual: it throws a KeyError when an order is missing customer_id. Explain the bug, fix it, handle the missing field safely, and add two test cases. Keep the fix readable for a junior developer.
Field note — "Expected vs. actual" does most of the work here — without it, the model is debugging blind and has to guess what counts as correct.

Business consulting

For consulting work, prompting stops being a productivity trick and becomes part of the method — diagnosing client processes, mapping workflows, sizing automation opportunities, drafting policy.

  • Treat the model as an interviewer, not just an answer machine
  • Ask for a prioritization framework, not just a list of ideas
  • Request a 30-day pilot, not just a long-term roadmap
  • Have it flag risks and data-privacy concerns unprompted
Automation opportunity interview
Act as an automation consultant for SMEs. Interview me one question at a time across admin, customer communication, sales, finance, reporting, HR, operations, and compliance. When we're done, hand back the top 10 opportunities with estimated value, complexity, risk, a suggested pilot, and a 30-day plan.
Priority matrix
Act as a business automation strategist. Take this list of AI use cases and score each on business value, complexity, data availability, risk, time to impact, scalability, and stakeholder adoption. Return a prioritization matrix, the top three pilots, the ones to avoid for now, key risks, and a first 30-day action plan.
AI usage policy
Act as an AI governance advisor for a 50-person company. Draft a plain-language usage policy covering approved and prohibited use cases, confidential and client data rules, human review requirements, tool approval, employee responsibilities, escalation, and training. It needs to make sense to sales, ops, finance, and support — not just engineering.
Field note — This is the one place the model is asked to interview you instead of the other way around — useful when the client, or you, doesn't yet know what to automate.
06 — Practical tips

Field-tested tips

Small adjustments that consistently improve results. Expand any tip for the reasoning behind it.

Tip 01Assign a role+
Give the model a persona or area of expertise before the task. A model told it's "a senior copy editor" tends to apply more domain-specific judgment than one given no role at all.
Tip 02Avoid negation+
Models follow positive instructions more reliably than negative ones. "Write in plain English" lands better than "don't use jargon" — the model has to picture the thing you don't want before it can avoid it.
Tip 03Mind capitalization+
Casing can carry meaning. ALL CAPS can read as emphasis or urgency to a model, much like it would to a person — reserve it for instructions that genuinely need extra weight.
Tip 04Mind the cut-off date+
Every model has a training cutoff. For anything time-sensitive, state today's date in the prompt or ask the model to flag where it might be relying on outdated information.
Tip 05Ask for an output preview first+
On longer or unfamiliar tasks, ask the model to sketch the structure or outline before producing the full result. It's cheaper to redirect a one-line outline than to rewrite a finished draft.
Tip 06Define the audience+
Few prompts state it, but who's reading matters as much as what's being said. "Explain this to a board member" and "explain this to a new intern" shouldn't produce the same paragraph.
Tip 07Vary the order of the building blocks+
Instruction, context, input data, and output format don't have to arrive in a fixed sequence. If a prompt isn't landing, try reordering the same pieces before rewriting them from scratch.
Tip 08Save proven, complex prompts for reuse+
A prompt that took five attempts to get right is worth keeping. Treat it as a template and swap in new details rather than starting from a blank page every time.
Tip 09Experiment with emotional framing+
Phrasing a request with stakes attached — "this matters to my team," "take your time and be thorough" — can shift the tone and effort of the response. Worth testing rather than assuming it does nothing.
Tip 10Format longer prompts as Markdown+
Headings, bullet points, and bold text help a model parse a long prompt the same way they help a person skim one. Structure is information, even inside the instruction itself.
07 — Hazards

When the signal gets hijacked

Because language models respond to whatever text they're given, that openness can be turned against them. Prompt injection is the umbrella term for any attempt to steer a system outside its intended behavior using crafted input.

HazardPrompt leaking+
Coaxing a system into revealing instructions or configuration meant to stay hidden. A support bot that auto-replies to certain keywords can sometimes be tricked into exposing the exact rules it was given. Even when the leak looks harmless, it can expose confidential business logic, internal workflows, proprietary strategy, or trade secrets — and the discovery itself can erode trust in whatever it's running.
HazardJailbreaking+
Manipulating a system into setting aside its own safety rules entirely. A successful jailbreak can push a system to produce discriminatory content, misinformation, or other material it would normally refuse. Beyond the immediate harm, incidents like this are corrosive to public trust in whatever brand deployed the system.
DefenseRed teams+
The countermeasure most providers build in: a dedicated team paid to break the system on purpose. Red teams test systems the way a penetration tester probes a network — systematically searching for and exploiting weaknesses before an outside attacker can. Catching a failure mode early means it can be patched before it ever reaches a real user.

Why it matters

  • Reputational damage
  • Exposure of confidential information
  • Spread of misleading content
  • Unplanned operational costs
08 — Cheat sheet

Pre-transmission checklist

Run any draft prompt through this list before sending it. Most well-formed prompts touch at least five of these.

0 / 8 confirmed
09 — Glossary

Field terms

Prompt+
The natural-language instruction used to direct an AI system.
Prompt design+
The user-facing craft of wording instructions effectively.
Prompt engineering+
The technical work of connecting data, APIs, and parameters behind a prompt.
Zero / one / few-shot+
Prompting with zero, one, or several worked examples included.
Chain-of-thought (CoT)+
Prompting that asks for visible, step-by-step reasoning.
Self-consistency+
Running a prompt multiple times and taking the most frequent answer.
Tree-of-thought (ToT)+
Prompting that develops multiple reasoning paths in parallel before merging them.
Prompt chaining+
Breaking a task into a sequence of linked prompts.
Prompt injection+
Any attempt to manipulate a model's behavior through crafted input.
Prompt leaking+
A form of injection that exposes hidden system instructions.
Jailbreaking+
A form of injection that bypasses a model's safety constraints.
Red team+
A security team that proactively tests a system for weaknesses.