The Claude Prompt Library: 20+ Prompts That Work (2026)

How to use this library: Copy the prompt, fill in the bracketed sections with your specifics, and run it. Each prompt is written for Claude specifically — the phrasing and structure take advantage of how Claude handles instructions. Many will also work with other models but are optimized here for Claude Sonnet or Opus — see the Claude model comparison if you’re deciding which model to use.

EDIT FOR VOICE

You are editing a piece of writing to match a specific voice. The target voice is: [describe voice — direct, conversational, no jargon, uses short sentences, never sounds like marketing copy].

Here is the draft:
<draft>
[paste draft]
</draft>

Edit the draft to match the target voice. Do not change the meaning or structure — only the language. Return the edited version only, no commentary.

HEADLINE VARIANTS

Write 10 headline variants for this article. The article is about: [topic in one sentence].

Target audience: [who will read this]
Tone: [direct / curious / urgent / informational]
Primary keyword to include in at least 3 variants: [keyword]

Format: numbered list, headlines only, no explanations.

MAKE IT SHORTER

Reduce this to [target word count] words without losing any key information. Cut filler, redundancy, and anything that doesn't add to the argument. Do not add new ideas. Return only the shortened version.

<text>
[paste text]
</text>

META DESCRIPTION BATCH

Write meta descriptions for the following pages. Each must be 150-160 characters, include the primary keyword naturally, describe what the visitor gets, and end with a soft call to action.

Pages:
1. [Page title] | Keyword: [keyword]
2. [Page title] | Keyword: [keyword]
3. [Page title] | Keyword: [keyword]

Format: numbered list matching the pages above. Return descriptions only.

FAQ SCHEMA GENERATOR

Generate 5 FAQ questions and answers optimized for Google's FAQ rich results. The topic is: [topic].

Rules:
- Questions must match how someone would actually search (conversational phrasing)
- Answers must be 40-60 words, direct, and answer the question in the first sentence
- Include the primary keyword [keyword] in at least 2 of the questions
- Do not start any answer with "Yes" or "No" — lead with the substance

Format: Q: / A: pairs, no additional text.

CONTENT BRIEF FROM URL

I want to write a better version of this article: [URL or paste content]

Analyze it and produce a content brief for an improved version. Include:
1. Gaps — what important questions does this article not answer?
2. Structure — suggested H2/H3 outline for the improved version
3. Differentiation — one angle or section that would make this article clearly better than the original
4. Target keyword and 3-5 supporting keywords to weave in naturally

Be specific. Generic advice is not useful.

DOCUMENT SUMMARY WITH DECISIONS

Read this document and produce a structured summary for an executive who has 3 minutes.

<document>
[paste document]
</document>

Format your response as:
- WHAT IT IS (1 sentence)
- KEY FINDINGS (3-5 bullets, most important first)
- DECISIONS REQUIRED (if any — be specific about who needs to decide what)
- WHAT HAPPENS IF WE DO NOTHING (1-2 sentences)

No preamble. Start directly with WHAT IT IS.

STEELMAN THE OPPOSITION

I am going to share my position on [topic]. Your job is to steelman the strongest possible counterargument — not a strawman, but the most rigorous case against my position that a smart, informed person could make.

My position: [state your position clearly]

Present the counterargument as if you believe it. Do not include any caveats about why my position might still be right. Make the opposing case as strong as possible.

CODE REVIEW

Review this code for: (1) bugs, (2) security issues, (3) performance problems, (4) readability. Be direct — flag real issues only, not style preferences unless they're genuinely problematic.

Language: [Python / JavaScript / etc.]
Context: [what this code does and where it runs]

<code>
[paste code]
</code>

Format: numbered findings with severity (CRITICAL / HIGH / LOW) and a suggested fix for each. No preamble.

WRITE THE FUNCTION

Write a [language] function that does the following:

Input: [describe input — type, format, examples]
Output: [describe output — type, format, examples]
Constraints: [edge cases to handle, things to avoid, libraries not to use]
Context: [where this runs — browser, server, CLI, etc.]

Include inline comments for any non-obvious logic. Return only the function and any necessary imports. No test code unless I ask for it.

COMPETITIVE DIFFERENTIATION

I run [describe your business in 2-3 sentences]. My main competitors are [list 2-3 competitors and what they're known for].

Identify 3 genuine differentiation angles I could own — not marketing spin, but actual strategic positions that would be hard for competitors to copy given their current positioning. For each, explain: (1) what the position is, (2) why competitors can't easily take it, (3) what I'd need to do to own it credibly.

Be specific to my situation. Generic "focus on service quality" advice is not useful.

EMAIL THAT GETS READ

Write an email that accomplishes this goal: [state what you need the recipient to do or understand].

Recipient: [their role, relationship to you, what they care about]
Context: [why you're reaching out now, any relevant history]
Tone: [formal / direct / warm / urgent]
Length: [under 150 words / under 200 words]

Rules: No throat-clearing opener. First sentence must contain the point of the email. End with one clear ask, not multiple options. No "I hope this email finds you well."

JOB SCOPE SUMMARY

Convert these restoration job notes into a professional scope-of-work summary for an adjuster or property manager.

Job type: [water / fire / mold / etc.]
Loss details: [what happened, when, affected areas]
Raw notes: [paste field notes]

Format as: affected areas → documented damage → scope of remediation → timeline estimate. Use professional restoration terminology. Write in third person. One paragraph per area affected. No bullet points.