For Claude

Claude Prompts

Prompts that suit Claude’s strengths: long documents, careful tone, and nuanced analysis. Each is copy-ready and shown with an example output.

Claude handles long, dense text unusually well, so the prompts here lean into it: paste a 30-page report and get a structured analysis, drop in a contract for a plain-English read, or feed a long meeting transcript and get clean action items. Its careful handling of tone makes it strong for writing work too — matching your voice from samples, line-editing for clarity without flattening, or softening a sensitive email so it stays firm but kind.

Below the Claude-specific set are general prompts that also work well here. They run in ChatGPT and Gemini too, but Claude is the one to reach for when the input is long or the wording has to be exactly right. Copy any prompt and add your own material.

14 prompts · free to copy · example output on each

Claude

Analyze a long document or report

Paste a long report and get a structured analysis Claude's context window handles well.

The prompt

You are a senior analyst. I will paste a long document below. Read it in full before responding.

Produce a structured analysis with these sections:
1. Core argument or purpose (2–3 sentences)
2. Key findings (bullets, with page or section references where possible)
3. Assumptions or gaps worth questioning
4. What a decision-maker should act on

Be direct. Flag anything that seems inconsistent with what the document claims elsewhere.

Document: [PASTE FULL DOCUMENT]

Example output

Core argument: The report argues that distributed warehouse inventory reduces last-mile delivery time by 23%, but the supporting data comes entirely from two pilot markets (Phoenix and Austin) that share unusual suburban density patterns. Key findings: - Average delivery time dropped from 3.2 to 2.5 days in pilot markets. - Cost per fulfillment rose 11% — buried in appendix B, not in the executive summary. - Customer satisfaction scores improved only in segments ordering over 3 items per order. Gaps: The model assumes flat fuel costs; current price trends would compress the margin. Act on: Expand the pilot to a dense urban market before committing to the full rollout budget.

TipClaude can hold 200,000 tokens in one pass, so you can paste the entire document rather than summarizing it yourself first — the analysis is sharper when Claude reads the footnotes, not just the executive summary.

Claude

Explain a contract in plain English

Get a clause-by-clause plain-language read (not legal advice).

The prompt

I am not a lawyer and this is not a request for legal advice. Please help me understand a contract by explaining each clause in plain English.

For each clause:
- State what it means in one or two sentences.
- Flag it as Routine, Worth Discussing, or Review with Counsel.
- Note any deadline, automatic renewal, or penalty buried in the language.

If a clause is genuinely standard boilerplate, say so briefly and move on.

Contract: [PASTE CONTRACT TEXT]

Example output

Clause 3 — Term and Renewal Means: The contract runs 12 months and renews automatically unless either party cancels in writing 60 days before the end date. Worth Discussing. The 60-day window is tighter than usual (90 days is common). If you miss it, you're locked in for another year. Clause 7 — Limitation of Liability Means: If something goes wrong, the vendor's total liability is capped at the fees you paid in the prior 3 months. Review with Counsel. This cap is very low for a mission-critical service — something to negotiate. Clause 12 — Governing Law Means: Any dispute is settled under Delaware law. Routine.

TipThe "Review with Counsel" flag is what makes this useful — Claude is distinguishing routine boilerplate from clauses that actually affect your risk, which is the work a first read requires.

Claude

Rewrite text in your own voice

Give Claude writing samples and have it match your tone.

The prompt

Study the writing samples I paste below and identify my voice: sentence length, how I handle transitions, level of formality, any signature habits.

Then rewrite the draft text in that same voice. Do not change the meaning. Do not polish it into something more "professional" — match me, not a generic house style.

After the rewrite, note in one line what you identified as the strongest markers of my voice.

My writing samples: [PASTE 2–3 SAMPLES]
Draft to rewrite: [PASTE DRAFT]

Example output

Rewrite: Honestly, the pricing page is doing too much. Every feature we've ever shipped is listed there, which means the one thing the customer actually needs to see — what they get for 49 dollars a month — is buried. We should cut it to three bullets and one number. Voice notes: Short declarative sentences with a brief aside before the main point; you use em-dashes to hold a thought rather than commas; informal tone that stops just short of casual.

TipThree samples from different contexts (a Slack message, a blog post, a client email) give Claude a wide enough range to separate your actual habits from the conventions of any single format.

Claude

Line-edit a draft for clarity

Get a careful edit that tightens prose without flattening it.

The prompt

Line-edit this draft for clarity and concision. Rules:
- Cut filler words and redundant phrases.
- Break up sentences over 35 words.
- Keep the author's tone intact — do not rewrite into a generic corporate voice.
- Do not add new ideas or change any factual claims.

After the edited version, provide a short list of the patterns you cut most often so I can watch for them next time.

Draft: [PASTE DRAFT]

Example output

Edited version: Deploying the new system will take four weeks. The main risk is data migration: two legacy databases use incompatible date formats and will need manual cleanup before the import. Plan for a one-week buffer. Patterns cut: - "It is important to note that" — deleted 3 times (just state the point) - "In order to" → "to" — 4 instances - Passive voice in risk statements ("it has been identified that") → active throughout

TipAsking for the pattern list turns a one-time edit into a coaching session — you learn your own tics rather than just getting a cleaner draft.

Claude

Explain a code snippet

Understand unfamiliar code step by step.

The prompt

You are a patient senior developer. Explain the code I paste below to someone who can read basic syntax but does not yet know this language or pattern deeply.

Structure your explanation:
1. What this code does in one plain sentence.
2. Walk through each logical section in order, explaining what it does and why.
3. Identify one concept a beginner is most likely to misread, and explain it clearly.
4. Note any side effects or failure modes worth knowing.

Do not assume I know the library or framework. Spell out abbreviations on first use.

Code: [PASTE CODE]

Example output

What it does: This function fetches a list of users from an API and returns only the ones whose accounts are active. Walk-through: Section 1 — the async keyword means this function pauses at each await line rather than blocking the entire program. It waits for the network response before continuing. Section 2 — response.json() converts the raw HTTP response body into a JavaScript object. Without this step, you'd have a stream of bytes, not usable data. Section 3 — the filter call loops over every user and keeps only those where the "active" property is true. Common misread: beginners often think await means "wait forever if the server is slow." It does not — if the server takes too long and you have no timeout set, the promise may hang indefinitely. Side effects: if the API returns an error status, response.json() may still succeed but return an error object — check response.ok before parsing.

TipThe "common misread" instruction is the most useful part: Claude flags the exact conceptual trap that causes bugs rather than just restating what each line does.

Claude

Turn a long transcript into action items

Process a long meeting transcript into a clean summary and tasks.

The prompt

I will paste a long meeting transcript. Read the full transcript before responding.

Produce:
1. A three-sentence meeting summary (topic, main decision, open question).
2. Action items in table form: Owner | Task | Due date (use "TBD" if no date was mentioned).
3. Any commitments that were made but no owner was assigned — flag these as "Unowned."
4. One thing that was debated but not resolved.

Do not pad. Do not invent owners or dates.

Transcript: [PASTE FULL TRANSCRIPT]

Example output

Summary: The team reviewed Q3 rollout timelines for the new billing module and agreed to delay the public launch by two weeks to allow for load testing. The main open question is whether customer support will be ready to handle billing queries by the new date. Action items: | Owner | Task | Due | | ----------- | --------------------------------- | -------- | | Priya | Complete load test scenario list | Jun 20 | | Marcus | Confirm CS training schedule | Jun 18 | | Engineering | Fix pagination bug in invoice view | Jun 17 | Unowned: Someone said "we should update the status page before launch" — no owner assigned. Unresolved: Whether to soft-launch to 10% of accounts first or go full release from day one.

TipPaste the raw, unedited transcript — Claude handles crosstalk, filler words, and speaker labels. Cleaning the transcript yourself first just adds work with no accuracy gain.

Claude

Soften a sensitive email's tone

Rewrite a tense message to be firm but kind.

The prompt

Rewrite this email so it is firm but genuinely kind. Keep all the factual content and the core ask. Do not soften the message into vagueness or bury the key point.

Tone targets:
- Direct, not blunt.
- Empathetic, not apologetic.
- Clear about what happens next.

After the rewrite, note any phrases in the original that risked landing badly, and explain why.

Situation: [ONE SENTENCE CONTEXT, e.g. "declining a candidate after a final-round interview"]
Original email: [PASTE EMAIL]

Example output

Rewrite: Hi Jordan, Thank you for the time you put into the process — the final-round conversation was genuinely strong. We've decided to move forward with another candidate whose background maps more closely to where we're taking the role in the next 12 months. This was a close call. I'll keep your details on file and will reach out directly if a more fitting role opens. I hope our paths cross again. Best, [Name] Phrases that risked landing badly: - "Unfortunately we won't be moving forward" — the word "unfortunately" often reads as performative; the rewrite names the decision plainly instead. - "We had many strong candidates" — implies the candidate was one of a crowd; removed.

TipClaude is especially careful with tone in rejection contexts because the stakes are asymmetric: a careless phrase costs a candidate more than it costs you.

Claude

Compare two versions of a document

Get a clear diff of what changed and why it matters.

The prompt

I will paste two versions of a document. Read both in full before responding.

Produce:
1. A plain-English summary of what changed (not a line-by-line list — synthesize the pattern of changes).
2. A table of specific changes: Section | What changed | Significance (Low / Medium / High).
3. Any language that was removed that I should know about — deletions are often more important than additions.
4. Your read on the overall direction of the revision (e.g., scope narrowed, liability shifted, terms tightened).

Version A: [PASTE VERSION A]
Version B: [PASTE VERSION B]

Example output

Summary of changes: Version B narrows the scope of the vendor's service commitment and removes the SLA penalty clause that was in Version A. Most additions are definitions that tighten what counts as "downtime," which limits when penalties would have applied anyway. Changes: | Section | What changed | Significance | | -------------- | ----------------------------------------- | ------------ | | Section 2.1 | Uptime guarantee reduced from 99.9% to 99.5% | High | | Section 4 | SLA penalty clause removed entirely | High | | Definitions | "Downtime" now excludes scheduled maintenance windows | Medium | | Section 8 | Governing jurisdiction changed from NY to DE | Low | Removed language to note: The original Section 4 gave you a service credit of 10% of monthly fees for each hour of downtime exceeding the SLA. That language is gone in Version B with no replacement. Overall direction: Version B shifts risk toward the customer. The vendor has narrowed its commitments and eliminated financial consequences for missing them.

TipLoading both full versions lets Claude catch removed language, which is almost always what matters most in contract redlines and is easy to miss in a manual read.

ChatGPTGeminiClaude

Write landing page copy

Draft conversion-focused landing page copy from a simple brief.

The prompt

Write conversion-focused landing page copy for [PRODUCT / OFFER].

Brief:
- Target visitor: [WHO THEY ARE, HOW THEY ARRIVED]
- Their primary problem: [PAIN POINT]
- What the product does: [ONE-LINE DESCRIPTION]
- Key proof points: [STAT, TESTIMONIAL, OR CUSTOMER LOGO]
- Primary CTA: [ACTION + OFFER, e.g., "Start free trial"]

Sections to write: Hero (headline + subhead + CTA), Problem block (2–3 sentences), Solution block (3 benefit bullets), Social proof (use my proof points), and a closing CTA. Plain language, no filler phrases.

Example output

HERO Headline: Stop losing 40 hours a month to manual client reporting. Subhead: Databox pulls your clients' metrics into one dashboard and writes the report for you — automatically, every week. CTA: Start your free 14-day trial → PROBLEM Agency reporting eats time you don't have. Pulling numbers from five tools, formatting slides, chasing missing data — it's two days of work that should take 20 minutes. SOLUTION - Connect any source in minutes: Google Analytics, HubSpot, Meta Ads, and 70+ more - Auto-generated reports your clients can open without a login - Custom white-label branding on every dashboard SOCIAL PROOF "We reclaimed 38 hours a month on reporting alone." — Jordan M., Head of Growth, Trellis Agency Trusted by 1,400+ marketing teams. CLOSING CTA See your clients' data in one place today. No credit card required.

TipSpecifying how the visitor arrived (paid ad, organic search, email) lets the model calibrate how much context to establish in the hero — a cold paid-ad visitor needs more orientation than a warm email click.

ChatGPTGeminiClaude

Outline an SEO blog post

Build a search-intent-driven outline before writing a word.

The prompt

Create a detailed outline for a blog post targeting [PRIMARY KEYWORD]. The post should satisfy [SEARCH INTENT: informational / commercial / transactional].

Audience: [WHO THEY ARE AND WHAT THEY ALREADY KNOW]

Deliverables:
- H1 with the keyword placed naturally
- H2 sections with a one-sentence rationale for why each section serves the reader's intent
- One H3 under each H2 showing how to add depth without padding
- A conclusion that includes a soft CTA to [DESIRED NEXT STEP]
- Estimated word-count split per section

Example output

H1: How to Reduce Employee Onboarding Time Without Cutting Corners (~80 words) H2: Why onboarding still takes too long at most companies (rationale: names the problem so readers confirm they're in the right place) ~250 words H3: The three places time actually disappears H2: Five tactics that cut time-to-productivity in half (rationale: the payoff readers came for) ~700 words H3: Tactic 2 — async video walkthroughs instead of live shadowing H2: What not to cut — mistakes that create costly re-onboarding ~350 words H3: The one thing never to async Conclusion + CTA: summarize, link to onboarding checklist template ~150 words

TipAdding a rationale for each H2 forces you to justify every section against reader intent — it is the fastest way to spot padding before you write a single word.

ChatGPTGeminiClaude

Summarize options into a decision memo

Lay out choices, trade-offs, and a recommendation for a fast decision.

The prompt

Write a decision memo for [DECISION MAKER / AUDIENCE] on the question: [THE DECISION TO BE MADE].

Format:
1. **Context** — why this decision is needed now (2–3 sentences).
2. **Options** — a table: Option | Pros | Cons | Cost/Effort.
3. **Recommendation** — which option you recommend and the one-sentence reason.
4. **What we need from you** — the specific ask (approval, a call, a sign-off).

Be direct. State a recommendation even if the data is imperfect. Under 300 words.

Details: [PASTE OPTIONS, TRADE-OFFS, YOUR PREFERRED CHOICE AND WHY]

Example output

**Decision: Hire vs. Contract for Design Role** To: [Director] | Date: Jun 17 **Context** The onboarding project needs a designer by July 1 to hit the Aug 31 ship date. The role has been open for six weeks; the pipeline has two candidates but no offer-ready finalist. **Options** | Option | Pros | Cons | Cost | |---|---|---|---| | Extend contractor (Lena) | Available now, knows the product | 20% premium, not a long-term fix | $12,000 for 8 weeks | | Wait for hire | Right long-term | Delays project 3–6 weeks | $0 now, risk of Q3 miss | | Freelancer via agency | Fast, low overhead | Ramp time, no product context | $8,000–$14,000 | **Recommendation** Extend Lena's contract through August. She's already ramped, and missing the August date costs more than the premium. **What we need from you** Approval to extend Lena at the current rate through Aug 31. I need this by Monday to give her enough notice.

TipState your recommendation explicitly — "option B" is not a recommendation. Saying "I recommend X because Y" forces you to commit, and it's exactly what decision-makers need to move fast. A memo that hedges everything is a memo that gets no action.

ChatGPTGeminiClaude

Compare finalists side by side

Summarize two or three finalists into a clear comparison.

The prompt

Compare [NUMBER] final-round candidates for the role of [JOB TITLE] and give the hiring team a clear summary to inform their decision.

For each candidate, I'll give you notes. Produce:
- A comparison table with the key criteria as columns and candidates as rows.
- Under the table, a one-paragraph "case for" each candidate — genuine strengths only, no padding.
- A section on key tradeoffs the team should discuss.
- Do not make a hire recommendation — leave the decision to the team.

Evaluation criteria: [LIST CRITERIA]
Candidate notes: [PASTE NOTES FOR EACH CANDIDATE]

Example output

| Criterion | Candidate A (Sara) | Candidate B (Tom) | Candidate C (Lea) | |---|---|---|---| | Technical depth | High | Medium | High | | Leadership exp. | 3 direct reports | None | 6 direct reports | | Domain fit | Strong (SaaS) | Moderate | Weak (retail only) | | Communication | Clear, concise | Strong, verbose | Clear | | Culture signals | Collaborative | Independent | Collaborative | Case for Sara: Built and scaled a 3-person team in a similar product org. Strong on ambiguity; interview showed she works well without a playbook. Case for Tom: Highest technical ceiling in the group. Would need to grow into the leadership scope, but the raw thinking is there. Case for Lea: Most leadership experience by volume, though in a different industry. Strong communicator; the domain gap is the real question. Key tradeoffs: Do you need someone who can lead today, or someone you can develop? How much does the industry gap matter given your onboarding capacity?

TipEnding with "key tradeoffs" rather than a recommendation keeps the hiring team in the decision — they have context you don't, and the summary is most useful when it surfaces the real dilemma rather than resolving it.

ChatGPTGeminiClaude

Summarize a research paper

Get the key claims, method, and findings of a dense paper.

The prompt

Act as a research methods tutor. I will give you the abstract and any sections I paste from a research paper. Summarize it using this structure:
1. Research question (one sentence)
2. Method (what they did, how many participants or data points)
3. Key findings (bullets, with numbers if they appear)
4. Limitations the authors mention
5. One sentence on why this paper matters

Do not interpret or add analysis. Use plain language I can explain to a classmate.

Paper excerpt: [PASTE ABSTRACT + KEY SECTIONS]

Example output

1. Research question: Does spaced repetition improve long-term retention compared to massed practice in undergraduate vocabulary learning? 2. Method: Randomized experiment, 94 undergraduate psychology students over 8 weeks; one group used a spaced flashcard app, one group did blocked study sessions. 3. Key findings: - Spaced group retained 31% more words at the 4-week follow-up test. - No significant difference at the immediate post-test (p = .42). - Effect was strongest for low-frequency words. 4. Limitations: Self-selected study time; both groups used the same word list. 5. Why it matters: Confirms spacing benefit persists beyond the lab and applies to a practical student tool.

TipIf the paper is long, paste the abstract and the Results section first. Those two alone give you 80% of the structure; add the Discussion only if you need the "why it matters" layer.

ChatGPTGeminiClaude

Executive summary for a proposal

Condense a long proposal into a one-paragraph summary an exec will actually read.

The prompt

Write a one-paragraph executive summary to open a sales proposal. It should make a busy executive want to read on.

Cover, in plain language: the business problem, what we propose, the expected result (with a number if I give one), and the investment.

Details: [PASTE KEY PROPOSAL POINTS / PRICE / EXPECTED ROI]

Keep it under 120 words, confident but not hypey.

Example output

[Company] is spending roughly six weeks getting each new support rep to full productivity — time that costs both salary and senior-rep attention. This proposal outlines an answer layer trained on your existing documentation that gets new reps productive in under two weeks and keeps answers accurate as your docs change. Based on your current hiring pace, the expected payback is under one quarter. The investment is [PRICE] per year, including onboarding and your team's data setup. The sections below detail the rollout plan, security review, and success metrics we'd track together in the first 90 days.

TipPut the result and the payback period in the first three sentences — executives decide whether to keep reading there. Save features for the body.

Keep browsing

Gemini prompts ChatGPT prompt examples Prompts to summarize text ChatGPT for work

Frequently asked questions

What is Claude best at?

Working with long documents (it has a large context window), writing and editing with careful attention to tone, and nuanced analysis. The prompts here are chosen to play to those strengths — long-report analysis, contract explainers, voice matching, and tone fixes.

How much text can I give Claude at once?

Claude’s large context window lets you paste very long documents — long reports, multiple files, or full transcripts — in a single prompt. That’s why the analyze-document and compare-versions prompts here work where shorter-context tools struggle.

Can Claude match my writing voice?

Yes. The voice-matching prompt has you paste a few samples of your writing first, then asks Claude to mirror that tone and rhythm — more reliable than just asking it to “write in my style.”

Do these prompts work in ChatGPT or Gemini?

The general prompts do. The long-document and careful-editing prompts are written for Claude’s strengths, so they’re best there. For ChatGPT-specific examples, see our main library; for Google Workspace, see the Gemini prompts.