How to write better prompts for Claude

Practical patterns for getting consistent, high-quality output from Claude — what it excels at, how to structure requests, and where it needs explicit guidance.

← Back to guides

Where Claude stands out

Long, nuanced tasks: Claude handles long-context documents (200k token window) better than most models. Paste the full contract, code file, or research paper and ask precise questions about it.
Following complex instructions: Claude is particularly good at applying a long set of rules simultaneously — a style guide, a review rubric, or a multi-part format constraint — without dropping items from the middle.
Calibrated uncertainty: Claude is more likely than other models to say 'I'm not sure' or flag a confidence limitation rather than confidently hallucinating a fact. Useful for research tasks where knowing what is uncertain matters.
Reasoning through ambiguity: when you say 'think through this carefully before answering', Claude tends to produce genuine reasoning steps rather than superficial filler.
Safe text editing: preserving the author's voice, not adding unsolicited opinions, staying in the requested format — Claude respects editorial boundaries well.

How to structure requests for Claude

State the goal before the context: Claude is trained to consider early instructions carefully. Put 'your task is X' before pasting a long document, not after.
Be explicit about format: Claude defaults to well-structured prose with headers. If you want bullets only, no prose, or a specific schema, say so directly.
Use 'think step by step' for reasoning tasks: for analysis, comparisons, or multi-step decisions, this phrase reliably produces more reasoned output.
Tell Claude what to skip: 'Do not add caveats about AI limitations', 'Do not start with a restatement of my request', 'Do not offer alternatives I didn't ask for' — Claude respects these constraints.
For very long inputs, anchor the task at the end too: after pasting a 50-page document, repeat the core instruction in 1 sentence. Claude reads the whole context but the final instruction carries recency weight.

Templates

Structured analysis with Claude

Your task: analyze the document below and answer the specific questions listed.

Think through the document carefully before answering. If a question cannot be answered from the document alone, say so explicitly rather than guessing.

Questions to answer:
1. [Your first specific question]
2. [Your second specific question]
3. [Your third specific question]

Format: answer each question with a label (Q1:, Q2:, Q3:), followed by 2–4 sentences. Use a bullet for evidence when citing a specific part of the document.

Do not include an introduction or conclusion. Start directly with Q1.

Document:
"""
[paste document here]
"""

Opens on home with the prompt prefilled.

Open in Promptea

Claude as a writing editor

Edit the following text for clarity and concision.

Rules:
- Preserve my voice and phrasing wherever possible — only change what genuinely obscures the meaning
- Do not add information, opinions, or examples I did not include
- Do not convert my sentence structure to yours — if I use short sentences, keep them short
- Flag any sentence you are unsure about rather than silently rewriting it
- Do not add caveats or qualifications I did not write

Output format:
1. The edited text (full version)
2. A brief note on what you changed and why (3–5 bullets max)

Text to edit:
"""
[paste your draft here]
"""

Opens on home with the prompt prefilled.

Open in Promptea

FAQ

Does Claude need a system prompt?

Not necessarily, but a clear role and ruleset at the top of your prompt acts like one. Claude respects early instructions carefully, so opening with 'You are a concise editor. Rules: preserve the author's voice, flag uncertainty, no added opinions.' shapes the entire response. For chat interfaces where you can't set a true system prompt, this pattern is the practical equivalent.

When should I use Claude versus GPT or Gemini?

Claude tends to perform better for tasks requiring careful instruction-following, long-document analysis, preserving an author's voice during editing, and nuanced reasoning where getting things wrong has real costs (legal, medical, financial). GPT and Gemini have their own strengths — GPT has deep tool-use and plugin ecosystems, Gemini integrates tightly with Google Workspace. For general tasks, the best model is often whichever one you have access to and have already tested with your specific prompts.