Assistant Prompt Library

Best Claude Prompts: Curated Examples for Analysis, Writing & Long Documents

Claude is particularly well-suited for tasks involving long documents, nuanced analysis, careful writing, and situations where a thoughtful, detailed response matters more than a fast one. These prompts are designed around the types of work where Claude's context capacity and careful reasoning add the most value.

What makes Claude prompting different

Claude handles large amounts of input text — long documents, research papers, extended transcripts — without losing coherence across the context. This makes it especially useful for analysis tasks where you need an AI to hold a large amount of information in mind before drawing conclusions.

Claude also tends to produce longer, more structured responses by default and responds well to explicit instructions about the format, length, and level of detail you want. It is particularly useful for tasks that require careful judgment rather than just fast pattern-matching — evaluating the quality of an argument, identifying subtle contradictions in a document, or writing copy that requires tone sensitivity.

When working with Claude, being explicit about what you want it to prioritize — accuracy over completeness, brevity over depth, a specific audience — produces noticeably better output than open-ended requests.

Who these prompts are for

Researchers, analysts, writers, legal professionals, educators, consultants, and anyone handling long-form content, complex analysis, or writing tasks that require careful attention to nuance and accuracy.

Best use cases for Claude

Analyzing long reports, contracts, research papers, or transcripts
Writing that requires a specific, controlled tone or careful word choice
Synthesizing information across multiple sources into a coherent summary
Structured reasoning tasks: evaluating arguments, identifying assumptions, stress-testing plans
Document editing: improving clarity, consistency, and logic in long-form documents
Research support: literature synthesis, gap identification, methodology review

Prompt examples

Long document analysis

I am sharing a [report / contract / research paper / transcript]. Please read it carefully and provide: 1) the main argument or finding in 3 sentences, 2) the 5 most important specific points, 3) two significant limitations or caveats, 4) one thing that is implied but not stated explicitly, 5) your assessment of the strength of the overall reasoning. Document: [paste].

Claude handles very long pastes well. For documents over 20,000 words, break into sections and ask Claude to maintain a running summary.

Careful tone rewrite

Rewrite the following [email / passage / feedback / rejection letter] so that it is: [tone goal — e.g. direct without being harsh / empathetic without being dismissive / confident without being arrogant]. Keep the factual content unchanged. After the rewrite, note the 3 most significant tone changes you made and why each was necessary. Original: [paste].

Claude is particularly good at this because it distinguishes between content changes and tone changes more reliably than many assistants.

Argument evaluation

Evaluate the following argument: [paste the argument]. Analyze: the main claim, the evidence offered in support, the logical structure (is the conclusion supported by the premises?), any hidden assumptions, the strongest counter-argument, and an overall assessment of whether the argument is convincing and why or why not. Be specific — reference the actual content of the argument rather than giving a generic evaluation.

Contract or document review

Review the following [contract / agreement / policy document / terms of service] and identify: 1) any clauses that are unusually favorable or unfavorable to [one party], 2) any ambiguous language that could be interpreted in more than one way, 3) anything that appears to be missing that would normally be in this type of document, 4) the 3 highest-risk provisions. Note: this is for informational purposes only, not legal advice. Document: [paste].

Always note this is not legal advice. Claude can identify structural issues and flag language for professional review — not replace a lawyer.

Research synthesis

I have read the following sources on [topic]: [briefly describe 3–5 sources and their main findings]. Synthesize them into: what these sources agree on, where they disagree or contradict each other, what gap none of them fully addresses, and a one-paragraph synthesis of the current state of knowledge on this topic. Be specific — reference the actual sources rather than speaking in generalities.

Structured writing with editorial constraints

Write a [format — e.g. 800-word essay / executive memo / analytical report section] on [topic] for [audience]. Constraints: [list specific constraints — e.g. 'no passive voice,' 'cite a specific example in every other paragraph,' 'begin and end with the same central image,' 'avoid jargon — define any technical term you use']. Purpose: [what this piece needs to accomplish].

Claude responds well to multiple writing constraints simultaneously and tracks them across a long piece more reliably than a short prompt would.

Identify contradictions

Read the following [document / plan / policy / argument] carefully. Identify: any internal contradictions (places where the document says two things that are incompatible), any statements that contradict information commonly understood about [topic], and any places where the tone or implied assumptions shift unexpectedly. For each issue, quote the relevant passage and explain the contradiction. Document: [paste].

Editing for logic and clarity

Edit the following [report / proposal / essay / email] for logic and clarity — not style. Specifically: flag any places where the reasoning jumps without sufficient support, any sentences that are ambiguous or could be misread, any conclusions that are not clearly supported by the evidence presented, and any sections where the order of information is confusing. Show your edits inline using [brackets] for suggested changes. Original: [paste].

Multi-perspective analysis

Analyze [topic / decision / plan] from three perspectives: 1) [Perspective A — e.g. a risk-averse CFO], 2) [Perspective B — e.g. an impatient growth-focused founder], 3) [Perspective C — e.g. a long-term customer advocate]. For each perspective: what they would find most concerning, what they would find most promising, and what they would prioritize next. Keep each perspective distinct — do not let them blend together.

This prompt is useful for decisions where different stakeholders would genuinely disagree.

Document comparison

Compare the following two [documents / versions / proposals / arguments]: [paste Document A] and [paste Document B]. Identify: the 3 most significant differences in content, any differences in underlying assumptions or priorities, which document makes a stronger case for [specific claim], and what each document includes that the other lacks. Be specific — quote relevant passages.

Common mistakes with Claude prompts

Open-ended requests on long documents: Asking Claude to "summarize this document" without specifying format, length, and what to prioritize produces variable output. Be explicit about what you need from the analysis.
Not using the full context window: Claude is designed to handle long inputs. If you are summarizing a document you can paste in full, paste it — do not paraphrase it yourself first.
Treating Claude's caveats as filler: When Claude qualifies a statement or notes a limitation, it is usually doing so because the point is genuinely uncertain. These caveats are often the most analytically useful part of the response.
Not specifying length: Claude defaults to thorough, longer responses. If you need something brief, specify a word or sentence count explicitly.

How to customize these prompts

For document analysis prompts, paste the actual document rather than describing it. Claude's analysis is most useful when it can reference specific passages rather than working from a summary. For writing prompts, be explicit about your constraints — Claude tracks multiple requirements across a long piece more reliably when they are clearly stated upfront.

Related resources

Explore the Claude Prompt Framework

See how to structure prompts specifically for Claude's strengths — context, constraints, and careful reasoning.

View Claude Prompt Framework