A saved prompt can do a lot of quiet work. One person pastes a request into Claude and gets back three tight paragraphs they can drop straight into a client email. Another types roughly the same thing and gets a page of throat-clearing that says nothing useful. The difference is almost never a magic phrase. It’s how much context, structure and constraint went into the request.
Claude rewards that detail. It reads long documents properly, follows formatting rules closely and takes instructions literally. A well-built prompt produces noticeably usable output; a lazy one produces noticeably bland output. If you’re still working out the interface itself, this walkthrough of how to use Claude AI with prompts that actually work covers the mechanics before you start fussing over wording.
The five slots a strong prompt fills
Most disappointing prompts are missing something specific rather than something clever. Run this checklist before you hit enter:
- Role and situation. Not “you are an expert marketer” but “you’re writing for a B2B procurement manager who has already rejected two vendors.”
- The task, in one sentence. If it takes two sentences, you probably have two tasks.
- Source material. Paste the notes, the transcript, the draft. Claude cannot read the email sitting in your head.
- Constraints. Word count, tone, what to leave out, which claims need a source.
- Output shape. Prose, bullets, a table, a 60-word summary at the top.
It feels like overkill the first few times. Then you notice that adding one line about length saves three rounds of revision, and the habit sticks.
Wrap your source material in tags Claude can see
Anthropic trained Claude to pay attention to XML-style tags, and they fix a real problem: keeping your instructions separate from your content. Without them, a long pasted document blurs into the request and Claude starts summarising the wrong layer of it.
A skeleton that holds up looks like this: a <context> block saying who you are and what you’ve already tried, a <source> block containing the pasted material, and an <instructions> block saying what to do with it. You don’t need a library of tags. Three or four used consistently are enough. Name them after the content itself: <contract>, <customer_reviews>, <draft_post>.
Show one good example instead of describing it
Describing a style gets you a decent approximation. Supplying 150 words of it gets you a match. If you want copy that sounds like your team, paste a paragraph you’ve already published and say “match this register, not this subject.” The same applies to structure: two example bullets teach more than the instruction “use a scannable format.”
Two examples is the sweet spot. One reads as an anecdote, and three starts eating the context you need for the actual document.
Ask for the reasoning before the answer
For anything involving judgement, order matters. “Recommend a vendor” gets you a confident pick. “List what the three vendors do differently, then recommend one and tell me what would change your mind” gets you something you can actually check. Giving Claude room to think works because the reasoning becomes visible, which means it becomes correctable.
There’s a mechanical trick too: start the reply for it. Open the assistant turn with “Working through the numbers first:” and Claude continues in that mode instead of jumping to a conclusion. Small intervention, real effect on long analysis.
Prompts that quietly fail
- Three jobs in one prompt. “Summarise this, then rewrite it, then suggest a title” usually delivers a rushed version of all three.
- No audience. Without a named reader, Claude defaults to a neutral explainer voice that suits nobody.
- No length. Unspecified means “as long as it feels like,” which is rarely what you wanted.
- Asking for “better.” Better how? Tighter, warmer, more specific, less hedged. Pick one and say it.
- Assuming it remembers. A new chat starts clean. Claude holds substantial context inside a conversation and none across them.
Four patterns worth saving
Editing your own draft
“Here’s a draft. Cut 20% without losing any argument, flag every sentence where I hedge, and leave the pricing paragraphs alone.” Specific edits get specific results. “Make this better” gets you a rewrite in a voice that isn’t yours.
Reading a stack of research
Supply the papers, ask for claims it can support with a direct quote, and request a separate list of points where the sources contradict each other. That separation is the difference between a summary and something you can cite. The broader approach in using Claude AI for research without getting burned by a confident wrong answer is worth reading before you trust any citation you haven’t checked yourself.
Code review
Paste the function, the failing test and the full error. Ask for the two most likely causes, ranked, with the evidence for each. Claude is strong at tracing logic and weak at knowing what the rest of your codebase does, which is why where Claude genuinely helps with coding is a narrower patch of ground than the marketing suggests.
Business analysis
Feed it the real numbers and ask for the three questions a sceptical finance director would raise. That framing surfaces gaps a “summarise this spreadsheet” prompt hides completely. The same pattern applies to team workflows, as this look at where Claude AI saves time for businesses and where it doesn’t makes clear.
Output format deserves its own instruction rather than a hope. If you want something you can use rather than read, ask plainly: a table with these five columns, a checklist, a working calculator. Claude will often build those as an interactive artifact in the side panel that turns answers into working things, which beats a written description of the spreadsheet you asked for.
Chain prompts instead of stacking them
Long prompts fall apart around the fourth instruction. Rather than writing a 400-word monster, run three short exchanges: extract, then analyse, then write. Each step gives you a checkpoint, so you catch a bad assumption after step one instead of after the final draft.
Keep the thread open while you do this. Claude carries the earlier output forward, so there’s nothing to re-paste, and a single sentence is enough to correct course.
When the answer is still wrong, change one thing
Three moves fix most bad outputs, and they’re worth trying in this order. Add an example of what you want. Narrow the scope from the whole document down to one section. Ask Claude to critique its own draft against your stated constraints, then rewrite it. Doing all three at once makes it impossible to tell which one helped.
Save the prompts that survive that process. A plain text file with a dozen named patterns beats re-deriving them from memory every month, and it compounds: a prompt that produced a decent competitive analysis in March will produce a sharper one in June, once you’ve folded in the constraints you learned the hard way.