Instructing a model to work through a problem in the open, laying out intermediate steps before it commits to an answer, is one of the highest-leverage prompt changes available and one of the most casually overapplied. The leverage is real: on problems that decompose into steps, where an early mistake corrupts everything after it, making the model generate those steps first…

A few-shot prompt is often treated as a writing task: draft a couple of examples that look right, paste them in, move on. That framing hides what is actually happening. A set of examples is a miniature training set, curated by hand and injected fresh on every call, and the model generalizes from it the same way it generalizes from anything it…

A written instruction and a worked example can ask for the same output, and the example will get it more reliably almost every time. This is not a matter of the example being longer or more emphatic. It is a matter of what each one asks the model to do. An instruction describes the output you want and leaves…

Most discussions of controlling a model’s output collapse into a single move. For one team it is prefilling the first token; for another it is a longer, more emphatic instruction; for a third it is a schema bolted onto the response. Each of those is a real technique, and each is being asked to carry work it was never shaped to…

Two of the cheapest and most reliable ways to steer a model are to tell it who it is and to tell it what it knows. The first is identity: a role assignment, optionally extended into a full persona. The second is grounding: placing the specific facts a response should reason over directly into the prompt. Both are levers you pull…

Every prompt you send a model is really two documents fused into one. There is the part that is identical on every request in a session, and the part that is different every time. The single most consequential decision in prompt architecture is where you draw the line between them, because that line determines what the model treats as…

Most quality standards live in your head. You know the answer should be short, or written for a non-specialist, or structured so a downstream step can parse it, and you assume that because you know these things the model will honor them. It will not, because it cannot see them. A standard you hold silently has exactly zero effect on the output. It…

The largest single lever over the quality of a model’s output is not the model, the sampling settings, or the length of the prompt. It is how completely the instruction defines what a good answer would be. An instruction that leaves a decision open does not leave it unmade. The model makes it, silently, on your behalf, and you find out which way…