Beyond the Four Components

Advanced structural moves that go past role, instructions, context, and constraints

You’ve mastered the basics. Now what?

Role, instructions, context, constraints — that four-part structure gets you 80% of the way to a good prompt. But at the top end of prompt engineering, the remaining 20% is where the real leverage lives. This lesson covers four structural techniques that separate a competent prompt from one that reliably produces expert-level output: output examples, negative examples, explicit reasoning scaffolds, and deliberate component ordering.

Output examples: show, don’t just tell

Describing the output you want in prose is weaker than showing it. Claude is extremely good at pattern-matching to a concrete example, and a single well-chosen example often does more work than three paragraphs of instructions.

Write a subject line for this product update email.

Match this style exactly:
"Your Q3 report is ready (3 things changed)"
"We fixed the bug you reported — here's what's new"

Not this style:
"Important Update Regarding Your Account"
"Q3 Product Release Notes"

Topic: we added dark mode and fixed the export timeout bug.

Notice the example doesn’t just show format — it shows voice, specificity, and length in one shot. That’s more precise than “write a casual, specific subject line.”

Negative examples: showing what to avoid

Positive examples show the target. Negative examples fence off the failure modes you’ve actually seen Claude produce. This is especially powerful once you’ve run a prompt a few times and noticed a recurring bad pattern — feed that pattern back in as a “don’t do this.”

Explicit reasoning scaffolds

“Think step by step” is a blunt instrument. A reasoning scaffold gives Claude the actual steps to work through, in order, which produces more consistent reasoning than a generic instruction to think carefully.

Evaluate this vendor contract clause for risk. Work through it in this exact order:

1. Identify the specific obligation this clause creates for us
2. Identify the specific obligation it creates for the vendor
3. Note any asymmetry between the two
4. Flag any undefined terms that could be interpreted broadly
5. Rate the overall risk: Low / Medium / High, with one sentence of reasoning

Clause: [paste clause]

This isn’t the same as chain-of-thought prompting in general (covered in depth later in this course) — it’s about giving Claude a specific checklist rather than an open-ended “think about it” instruction. The checklist constrains the reasoning path, which makes output far more consistent across repeated runs.

Component ordering matters more than you think

Claude weighs information based on where it sits in the prompt, and recency matters. As a rule of thumb: stable, identity-level information (role, persona, standing rules) goes first; the specific task and its immediate constraints go last, closest to where Claude starts generating. If a critical constraint keeps getting dropped, try moving it from the top of the prompt to the very bottom, restated right before the request.

Putting it together

A prompt that uses all four techniques looks like layered scaffolding, not a wall of text: role and standing rules up top, reference context in the middle, then — right before the actual ask — a positive example, a negative example, and an explicit reasoning order. Each layer narrows the space of possible outputs a little further.