Modern models are far more forgiving of sloppy prompts than they were even a year ago, but a well-structured prompt still reliably produces better results than a vague one, especially for anything longer or more specific than a quick question. Here’s what actually moves the needle.
Give it a role and a goal, not just a task
“Summarize this” and “Summarize this for a busy executive who needs to decide whether to approve the budget in it” produce genuinely different outputs. Stating who the output is for and what decision or action it needs to support gives the model a target to write toward, instead of a generic middle-of-the-road default.
Be specific about format before you ask for content
If you need bullet points, a specific word count, a table, or a particular structure, say so upfront rather than asking for a rewrite afterward. “Give me five bullet points, each under 15 words” is a completely different, and more useful, instruction than “tell me about X” followed by manually trimming a paragraph.
Show, don’t just describe, when style matters
If tone or style is important, a short example does more work than a paragraph of adjectives. Pasting in two sentences of writing you like and saying “match this tone” outperforms describing the tone as “professional but friendly” almost every time, because the model can pattern-match to a concrete example far more reliably than to a subjective description.
Ask it to think before it answers, for anything multi-step
For genuinely complex requests, math, multi-step logic, anything with several interacting constraints, explicitly asking the model to reason through the problem step by step before giving a final answer tends to catch errors that a straight-to-the-answer response would miss. Many current reasoning models do this automatically, but it still helps to ask explicitly with older or faster model variants tuned for speed over depth. Anthropic’s own prompt engineering documentation covers this technique in more technical depth for developers.
Break big tasks into stages instead of one giant prompt
A single sprawling prompt asking for research, an outline, a draft, and a polish all at once tends to produce a mediocre version of all four. Splitting it into stages, first the outline, then a review of the outline, then the draft based on the approved outline, gives you a checkpoint to correct course before errors compound into the final output.
Treat the first response as round one
The highest-leverage prompting skill isn’t crafting the perfect first message, it’s giving good, specific feedback on the first response: “the second paragraph is too long,” “this misses the point about pricing,” “make this sound less formal.” Iterating inside the same conversation, where the model has the full context of what it already tried, consistently beats starting over with a longer, more elaborate prompt from scratch.
A template worth reusing
For anything beyond a quick question, this structure covers most of what matters: Context (who you are, what this is for) → Task (exactly what you want) → Format (structure, length, style) → Constraints (what to avoid, what must be included) → Example (if tone or style matters). You don’t need all five every time, but reaching for this checklist on anything important will consistently outperform writing whatever comes to mind first.
Key takeaway
Specificity beats cleverness. A plainly worded prompt that states who it’s for, what format you need, and what to avoid will outperform an elaborately worded one that’s actually vague about what success looks like. If you only take one habit from this, make it giving real feedback on the first draft instead of accepting or discarding it outright.
