Most AI prompts are written for ChatGPT and ported over with a "this works on Claude too" assumption. They don't. Claude has a distinct training profile — it responds exceptionally well to XML-tagged structure, explicit output format instructions, and role + context + task layering. Generic prompts leave a lot of performance on the table.
These 50 prompts for Claude are built for Claude specifically. Each one uses patterns that actually work: clear delimiters, explicit format constraints, and enough context that the model knows exactly what good output looks like. Copy them, swap the [PLACEHOLDERS], and you'll get results that are actually useful.
Before you dive in: the system prompts explained post covers how system prompts interact with these user-turn prompts. And for the underlying mechanics of why XML tags improve output on Claude, the XML tags and delimiters lesson is worth 10 minutes.
Why Claude responds differently
Claude was trained with Constitutional AI and on a corpus that rewards structured, precise responses. A few things consistently improve output quality:
XML tags signal structure. Wrapping context, task, and format in separate tags (<context>, <task>, <format>) lets Claude allocate attention correctly. It treats each block as a distinct instruction rather than blending them.
Explicit format instructions reduce guessing. Claude won't always pick the format you want. Say "Return a JSON array" or "Use a numbered list with bold headers" and you'll get that format reliably.
Role + context + task. The most reliable prompt structure on Claude is: who you are (role), what's true about the situation (context), what you need (task). You don't need all three every time, but when tasks are complex, this structure prevents drift.
For a deeper look at how to build these patterns from scratch, the few-shot prompting lesson is useful — especially if you're adding examples to calibrate output.
Coding prompts (10)
1. Code review
When to use: Before merging a PR or reviewing someone else's code.
<context>
Language: [Python/TypeScript/Go/etc.]
Codebase context: [brief description of what this code does in the broader system]
</context>
<task>
Review the following code for: correctness bugs, security vulnerabilities,
performance issues, and readability problems. Be specific — cite line numbers
and explain why each issue matters.
</task>
<code>
[paste code here]
</code>
<format>
Numbered list. For each issue: severity (critical/major/minor), line reference,
problem description, and suggested fix. End with a one-paragraph overall assessment.
</format>
2. Debugging
When to use: You have an error message and can't figure out why.
<context>
Language: [language]
Environment: [Node 20 / Python 3.11 / etc.]
What I was trying to do: [one sentence]
</context>
<error>
[paste full error message and stack trace]
</error>
<code>
[paste relevant code]
</code>
<task>
Diagnose the root cause of this error. Then give me the fix with an explanation
of why the original code failed.
</task>
3. Refactoring
When to use: You have working code that's hard to read or maintain.
Refactor the following [language] code. Goals:
1. Improve readability — cleaner variable names, smaller functions
2. Reduce duplication — extract repeated logic
3. Improve error handling — don't swallow exceptions silently
4. Preserve all existing behavior exactly
Show me a diff-style output: original function on the left, refactored on the right.
Then explain each change in a bullet list.
[paste code]
4. Writing tests
When to use: You need test coverage for existing code.
Write comprehensive [Jest/pytest/Go test] tests for the following function.
Include:
- Happy path tests (2-3 cases)
- Edge cases: empty input, null/undefined, boundary values
- Error cases: invalid types, out-of-range values
- Any async behavior if relevant
Use the [describe/it / class-based] pattern. Add a comment above each test
explaining what it's testing and why.
[paste function]
5. Explaining code
When to use: You've inherited code and need to understand it before touching it.
Explain the following code to me. I'm a [senior/mid/junior] engineer who
[is/isn't] familiar with [framework/pattern].
Structure your explanation:
1. What this code does at a high level (2-3 sentences)
2. How it works step by step (walk through the logic)
3. Key design decisions and why they were probably made that way
4. Any gotchas, edge cases, or non-obvious behavior I should know about
[paste code]
6. SQL query generation
When to use: You know what data you want but struggle with SQL syntax.
Write a SQL query for [PostgreSQL/MySQL/SQLite/BigQuery].
Tables:
[describe your tables, column names, and types — or paste CREATE TABLE statements]
What I need:
[describe in plain English what data you want to retrieve, filtered how, sorted how]
Requirements:
- Use CTEs if the logic is complex
- Add a comment above each CTE explaining what it does
- Optimize for readability first, performance second
- Return no more than [N] rows
7. Regex generation
When to use: You need a regex pattern and don't want to write it by hand.
Write a regex pattern that matches: [describe what you want to match]
Language/flavor: [Python re / JavaScript / PCRE / etc.]
Also provide:
- A plain English explanation of what the pattern does
- 5 example strings that should match
- 3 example strings that should NOT match
- Code snippet showing how to use it in [language]
8. API design
When to use: You're designing a REST or GraphQL API and want a second opinion.
<context>
I'm building a [REST/GraphQL] API for [describe the product/feature].
Users of this API: [internal services / mobile app / third-party developers]
Tech stack: [language + framework]
</context>
<task>
Design the API endpoints/schema for [specific feature].
For each endpoint include: HTTP method, path, request body (JSON schema),
response body (JSON schema), error responses, and one sentence on when a
client would call it.
</task>
<constraints>
Follow RESTful conventions. Use plural nouns for resources.
Return consistent error shapes with a `code` and `message` field.
</constraints>
9. Inline documentation
When to use: You need docstrings or JSDoc comments for a function.
Add documentation to the following [Python/TypeScript/Go] code.
For each function/method, add:
- A docstring describing what it does (not how)
- Parameter descriptions with types
- Return value description
- Any exceptions that can be raised
- A usage example if the function signature isn't obvious
Follow [Google style / JSDoc / Go doc] conventions. Don't document obvious things.
[paste code]
10. Security audit
When to use: Before shipping code that handles auth, user input, or sensitive data.
<context>
This code handles [authentication / user input / payment data / file uploads / etc.].
Language: [language]
Framework: [framework if relevant]
</context>
<task>
Perform a security audit. Look specifically for:
- Injection vulnerabilities (SQL, command, LDAP)
- Authentication and authorization flaws
- Sensitive data exposure
- Insecure deserialization
- Missing input validation
- Hardcoded secrets or credentials
- Improper error handling that leaks stack traces
</task>
<code>
[paste code]
</code>
<format>
For each vulnerability: severity (critical/high/medium/low), OWASP category,
description, and remediation steps with a code example.
</format>
Writing prompts (10)
11. Blog post outline
When to use: You know the topic but need structure before you start writing.
Create a detailed outline for a blog post titled "[title]".
Audience: [describe who will read this — their job, expertise level, and why they care]
Goal: [what should the reader be able to do or know after reading this?]
Word count target: [1,500 / 2,500 / 3,000+]
For each section include:
- H2 header (sentence case)
- 3-5 bullet points on what to cover
- One sentence on why this section belongs in the post
End with 5 potential meta description options (under 160 characters each).
12. Email rewrite
When to use: You have a draft that's too long, too vague, or the wrong tone.
Rewrite the following email.
Target tone: [direct and brief / warm but professional / formal / casual]
Goal of the email: [what action or response do you want?]
Reader: [who is this going to?]
Problems with my current draft: [too long / too passive / unclear ask / etc.]
My draft:
[paste draft]
Give me:
1. The rewritten email
2. A brief explanation of the main changes you made and why
13. Tone adjustment
When to use: You have content that needs to match a specific voice or style.
Rewrite the following content to match this tone: [describe the target tone
— e.g., "confident and direct, like a Y Combinator founder talking to other founders"
or "warm and accessible, like a teacher explaining to a curious non-expert"].
Keep the substance identical. Change only the voice, sentence structure,
and word choices.
Original:
[paste content]
After the rewrite, list 5 specific changes you made and why.
14. Headline variants
When to use: You need multiple headline options to A/B test.
Write 10 headline variants for: [describe the content — article, landing page, ad, etc.]
Audience: [describe who will see this]
Primary keyword: [keyword if SEO matters]
Goal: [clicks / signups / reads / shares]
Use these formats (2 headlines each):
- How-to (outcome-focused)
- Number list ("X ways to…")
- Question (creates curiosity)
- Contrarian (challenges a common belief)
- Direct benefit statement
Mark your top 3 picks and explain why.
15. Case study
When to use: You need to turn a customer win into structured content.
Write a case study based on the following raw notes.
Structure:
1. Challenge (what problem did the customer have?)
2. Solution (what did they implement and how?)
3. Results (specific numbers — if I haven't provided them, flag where they should go)
4. Quote (pull or suggest a plausible customer quote based on the results)
Tone: professional but not dry. Read like a story, not a brochure.
Length: 400-600 words.
Raw notes:
[paste your notes, bullet points, interview transcript, or Slack messages]
16. Executive summary
When to use: You have a long document that needs a short summary for leadership.
Write an executive summary of the following document.
Reader: [C-suite / board / department head / etc. — describe their priorities]
Length: [250 / 500] words maximum
Format:
- One opening paragraph (what this document is and why it matters)
- 3-5 bullet points (key findings or decisions required)
- One closing paragraph (recommended next steps or the ask)
Document:
[paste document or key sections]
17. Cold outreach
When to use: You're writing a sales or partnership email to someone who doesn't know you.
Write a cold outreach email for the following situation.
Sender: [your name, role, company]
Recipient: [their role, company, what they care about — be specific]
Goal: [get a 20-minute call / get feedback on a proposal / explore partnership]
Hook: [one specific thing about their company or work that you can reference —
not generic flattery, something specific]
Value proposition: [what's in it for them in one sentence]
Constraints:
- Under 150 words
- No corporate buzzwords
- End with one clear, low-friction call to action
- Don't open with "I hope this email finds you well"
18. Product description
When to use: You're writing copy for a product page, app store listing, or catalog.
Write a product description for [product name].
Product: [what it is, what it does]
Audience: [who buys this and why]
Key benefits (prioritized): [list 3-5 benefits — lead with the most important]
Tone: [professional / playful / technical / conversational]
Length: [50 / 150 / 300] words
Include:
- A one-sentence hook (leading benefit, no "introducing" or "we're excited")
- Body copy expanding on the top 3 benefits
- A closing sentence with implicit CTA
Avoid: passive voice, vague superlatives ("best-in-class", "revolutionary"),
and feature lists disguised as benefits.
19. Meeting notes to action items
When to use: You have rough meeting notes and need a clean output to share.
Turn the following raw meeting notes into a clean summary.
Output format:
**Meeting summary** (2-3 sentences on what was discussed and decided)
**Decisions made**
- [decision 1]
- [decision 2]
**Action items**
| Owner | Task | Due date |
|---|---|---|
| [name] | [task] | [date or "TBD"] |
**Open questions**
- [question that wasn't resolved]
If information is missing (like due dates or owners), write "[TBD]" rather
than guessing.
Raw notes:
[paste notes]
20. Press release
When to use: You're announcing a product launch, funding round, or company news.
Write a press release for [announcement].
Format (AP style):
- Headline: factual, under 10 words
- Dateline: [City, Date]
- Lead paragraph: who, what, when, where, why — in 1-2 sentences
- Body: 2-3 paragraphs with supporting detail and context
- Quote: one quote from [name, title] that sounds like a human said it
- Boilerplate: 3-sentence "About [Company]" section
- Contact: [name, email, phone placeholder]
Details:
[paste announcement details, key facts, and any quotes you want to include]
Tone: factual. No hype language ("game-changing", "disrupting", "thrilled to announce").
Research and analysis prompts (10)
21. Literature summary
When to use: You need to quickly understand a research paper or set of papers.
Summarize the following research paper for a [technical / non-technical] audience.
Include:
1. Research question (what problem were they solving?)
2. Methodology (how did they investigate it?)
3. Key findings (the actual results — be specific with numbers)
4. Limitations (what the authors acknowledge the study doesn't prove)
5. Implications (what this means for [your field/use case])
Don't editorialize about quality. Report what the paper says.
Paper:
[paste abstract + key sections, or the full paper]
22. Competitor analysis
When to use: You're preparing for a product decision, sales conversation, or strategy review.
Analyze the competitive landscape for [product/company] vs [competitor 1],
[competitor 2], [competitor 3].
For each competitor, cover:
- Core product positioning (how they describe themselves)
- Target customer (who they're actually built for)
- Pricing model (if public)
- Key differentiators (what they're genuinely better at)
- Weaknesses (where they're vulnerable)
Then:
- A comparison table (rows = criteria, columns = companies)
- 3 strategic implications for [our company/product]
Base this on: [paste any source material you have — their website copy,
G2 reviews, press coverage, etc.]
23. Pros and cons framework
When to use: You need to structure a decision before presenting it.
Evaluate the following decision using a structured pros/cons framework.
Decision: [describe the decision and the options]
Context: [what's the goal, what are the constraints, who's affected]
My current leaning: [which option I'm leaning toward, if any]
For each option:
- Pros (with reasoning — not just a list)
- Cons (same)
- Key assumptions this option depends on
- Risks if those assumptions are wrong
End with a recommendation, clearly labeled as your assessment based on the
information I've given you.
24. Market sizing
When to use: You need a TAM/SAM/SOM estimate for a pitch or strategy doc.
Help me estimate the market size for [product/service].
Use a bottoms-up approach:
1. Define the target customer (who specifically buys this?)
2. Estimate the number of potential customers (show your reasoning)
3. Estimate average revenue per customer per year
4. Calculate TAM, SAM, SOM with clear assumptions for each
Be explicit about every assumption. Where you don't have data, say so and
give a range rather than a false-precision number.
Context I have:
[paste any relevant data — industry reports, comparable products, customer
research, etc.]
25. Data interpretation
When to use: You have a dataset or chart and need help making sense of it.
Interpret the following data and tell me what it actually means.
Context: [what this data is measuring, over what time period, for what entity]
My hypothesis going in: [what I expected to see]
Data:
[paste the data — CSV, table, or describe the chart]
I want:
1. The 3 most important patterns or findings
2. What's surprising or counter-intuitive
3. What the data does NOT tell me (and what I'd need to know)
4. Recommended next steps based on these findings
26. Interview question design
When to use: You're preparing to interview candidates and need questions that reveal real signal.
Design an interview question set for [role title] at [company type/stage].
For each question, include:
- The question itself
- What you're trying to assess (be specific — not just "communication skills")
- What a strong answer looks like
- What a weak answer looks like
- One follow-up question
Question types to include:
- 2 behavioral (past behavior predicts future behavior)
- 2 situational (hypothetical scenarios)
- 1 technical/domain-specific
- 1 values/culture question
Total: 6 questions. Quality over quantity.
27. Survey design
When to use: You're building a customer survey and want questions that give you usable data.
Design a survey for [goal — e.g., "understanding why users churn in the first 30 days"].
Audience: [who will fill this out]
Distribution: [email / in-app / SMS]
Target completion time: [under 5 minutes]
For each question:
- The question text (write exactly as it should appear)
- Question type (multiple choice / scale / open text)
- Why this question is included (what decision will it inform?)
Include a question order that flows naturally and doesn't prime respondents.
Limit the survey to [8-12] questions maximum.
28. Hypothesis generation
When to use: You have a business problem and need structured hypotheses to test.
I'm trying to understand why [problem or metric change — e.g., "our 30-day
retention dropped 12% last quarter"].
Generate 8-10 hypotheses that could explain this. For each:
- The hypothesis (stated as "If X, then Y")
- What data or signal would confirm it
- What data or signal would rule it out
- How hard it is to test (easy/medium/hard)
Group them by theme. Prioritize toward hypotheses that are both plausible
and easy to test.
Context I have:
[paste any relevant data, customer feedback, or recent changes]
29. SWOT analysis
When to use: You're preparing a strategy review or board presentation.
Conduct a SWOT analysis for [company / product / initiative].
Context:
[paste any relevant background — what the company does, current situation,
competitive environment]
For each quadrant (Strengths, Weaknesses, Opportunities, Threats):
- 4-6 specific points (not generic)
- One sentence of supporting reasoning for each
After the SWOT, add:
- Top 3 strategic priorities that emerge from the analysis
- One key risk that cuts across multiple quadrants
30. Scenario planning
When to use: You're making a decision with high uncertainty about external factors.
Help me think through scenario planning for [decision or situation].
Key uncertainties: [list 2-3 factors you can't control but that will heavily
influence the outcome]
Build 3 scenarios:
1. Base case (most likely)
2. Upside case (things go better than expected)
3. Downside case (things go worse)
For each scenario:
- What has to be true for this to happen
- How it affects [the key metric or outcome you care about]
- What you'd do differently in this scenario vs the others
End with: which early signals would tell me which scenario is materializing?
Productivity prompts (10)
31. Meeting agenda
When to use: You're running a meeting and want it to not be a waste of time.
Create a meeting agenda for: [meeting name and goal]
Attendees: [list names or roles]
Duration: [30 / 45 / 60 minutes]
Meeting goal: [one sentence — what decision gets made or what gets aligned?]
Format:
- Pre-read (optional — what should attendees review beforehand?)
- Agenda items with time allocations
- Owner for each item
- Discussion vs. decision vs. information share (label each item)
- Time for questions at the end
Flag any agenda items that are information-share only and suggest whether
those could be an email instead.
32. Project plan
When to use: You need to scope a project and identify dependencies.
Create a project plan for: [project name and goal]
Context:
- Team: [roles available, not names]
- Timeline: [hard deadline or target date]
- Constraints: [budget, team size, technical dependencies, etc.]
Output:
1. Project phases with goals for each phase
2. Key milestones and dates
3. Task breakdown per phase (owner role, estimated effort, dependencies)
4. Risks and mitigations
5. Open questions that need to be resolved before work can start
Format as a structured document, not a table (prose + bullets).
33. Task prioritization
When to use: You have more to do than time to do it and need a framework.
Help me prioritize the following tasks using an impact/effort matrix.
My goal this [week/quarter]: [one sentence on what you're optimizing for]
Tasks:
[list your tasks — one per line, as much detail as you have]
For each task, score:
- Impact (1-5): how much does completing this advance my goal?
- Effort (1-5): how long will it take?
- Urgency (1-5): how time-sensitive is it?
Group tasks into quadrants: do now / schedule / delegate / drop.
Recommend an order for the "do now" tasks.
Explain any tasks you'd recommend dropping or delegating and why.
34. Standard operating procedure
When to use: You need to document a repeatable process so someone else can do it.
Write an SOP for: [process name]
Audience: [who will follow this — their role and experience level]
Frequency: [how often this process runs]
Structure:
1. Purpose (one sentence — why does this process exist?)
2. When to use this SOP (what triggers it?)
3. Prerequisites (what needs to be true / ready before starting?)
4. Step-by-step instructions (numbered, specific enough that someone
doing it for the first time won't get stuck)
5. What to do if something goes wrong (common failure modes + fixes)
6. Definition of done (how do you know the process completed successfully?)
Input from me:
[describe the process in rough terms — bullet points or a brain dump is fine]
35. OKR drafting
When to use: It's planning season and you need to write your team's OKRs.
Help me draft OKRs for [team name] for [quarter/year].
Context:
- Company-level goal these OKRs should support: [describe]
- Team's function: [what this team does]
- Biggest challenges this period: [what are you trying to fix or accelerate?]
Write 2-3 Objectives. For each Objective:
- Write the Objective (ambitious, qualitative, inspiring)
- Write 3-4 Key Results (measurable, binary or with a clear metric,
achievable by the team without external dependencies)
Flag any Key Results that depend heavily on another team and suggest
how to reframe them as within-team control.
36. Decision memo
When to use: You need to get buy-in from leadership on a decision.
Write a decision memo for the following situation.
Decision to make: [describe the decision]
Audience: [who this memo goes to — their role and what they care about]
Structure:
1. Executive summary (the recommendation in 2 sentences — lead with it)
2. Context (why this decision matters, what happens if we don't decide)
3. Options considered (2-3 alternatives with brief pros/cons)
4. Recommended option (with reasoning)
5. Assumptions and risks
6. What we need from you (the specific ask or approval)
Length: 1 page max. Be direct. Don't bury the recommendation.
Details:
[paste your raw thinking, notes, or relevant context]
37. Stakeholder update
When to use: You need to write a project update email or Slack post.
Write a stakeholder update for [project name].
Audience: [who's receiving this — their role and how much context they have]
Cadence: [weekly / bi-weekly / milestone-based]
Current status: [on track / at risk / blocked]
Structure:
- Status (one line: on track / at risk / blocked + why)
- What got done this period (bullet points — accomplishments, not activities)
- What's next (top 3 priorities for next period)
- Blockers (if any — with what you need to unblock)
- Key decisions needed (if any)
Tone: direct and confident. No defensive language. Under 250 words.
Raw update:
[paste your notes or bullet points]
38. Feedback delivery
When to use: You need to give difficult feedback and want to get the framing right.
Help me structure feedback I need to deliver to [colleague's role].
Situation: [describe what happened — be specific]
My relationship to this person: [peer / direct report / manager]
Goal of the feedback: [what change do you want to see?]
Tone I'm going for: [direct / constructive / supportive]
Draft the feedback using this structure:
1. Observation (what I saw, not my interpretation)
2. Impact (the actual effect it had — on the team, project, or relationship)
3. Question (invite their perspective before jumping to solutions)
4. Request (what I'm specifically asking them to do differently)
Then flag: any parts where my framing sounds judgmental rather than observational.
39. Onboarding document
When to use: Someone new is joining your team and you need to get them up to speed.
Write an onboarding document for a new [role] joining [team name].
The new hire's background: [relevant experience, what they'll know and won't know]
First 30 days goal: [what should they be able to do independently by day 30?]
Sections to include:
1. Welcome and context (what this team does, who we serve, why it matters)
2. How we work (meetings, async norms, tools, where to find things)
3. Priority learning (what to read, watch, or do in week 1)
4. First tasks (concrete, low-stakes tasks to start contributing quickly)
5. Key people (who to meet and why — by role, not name)
6. How to get help (where to ask questions, what's expected in terms of self-sufficiency)
Write in second person ("you will…"). Friendly but efficient.
40. Performance review
When to use: It's review season and you need to write a self-assessment or manager review.
Help me write a [self-assessment / manager review] for [role].
Review period: [time range]
Company competencies or criteria: [paste the rubric or describe the evaluation areas]
For each competency:
- Evidence (specific examples from this review period — use numbers where possible)
- Assessment (honest rating against the bar)
- Growth area (what to develop next period)
Then:
- Overall narrative (2-3 sentences on the person's/your contribution this period)
- Top strength to amplify
- Top development area to prioritize
Raw input:
[paste accomplishments, projects, feedback received, or your notes]
Creative prompts (10)
41. Brainstorming variants
When to use: You have one idea and want more options before committing.
I have this starting idea: [describe your idea]
Generate 15 variations. For each:
- One sentence describing the variant
- What makes it different from the original
- Who it's best suited for
Group variants into 3 buckets:
- Conservative (low risk, close to the original)
- Creative (meaningfully different but still plausible)
- Wild (stretch ideas that might sound crazy but could work)
Don't self-censor. Include the wild ones.
42. Story premise
When to use: You're starting a creative writing project and need a strong foundation.
Generate 5 story premises for a [genre] story.
Constraints:
- Setting: [time period and/or place, or leave open]
- Themes to explore: [list 1-3 themes]
- Tone: [dark / hopeful / satirical / etc.]
- Length target (if relevant): [short story / novella / novel]
For each premise:
- One-paragraph summary (setup, central conflict, what makes it interesting)
- The core dramatic question (what the story is really asking)
- The biggest risk or challenge in executing this premise well
Mark your top recommendation and explain why.
43. Character backstory
When to use: You have a character concept but need depth before you write them.
Develop a backstory for this character: [name, role in the story, genre]
What I know about them: [list any details you've already decided]
Generate:
1. Formative experiences (3 events that shaped who they are — be specific)
2. Core wound (the thing they're still unconsciously trying to resolve)
3. Public persona vs. private self (who they pretend to be vs. who they are)
4. Contradiction (one thing about them that seems inconsistent but isn't)
5. Voice notes (how they speak — vocabulary, rhythm, what they avoid saying)
Don't make them tragic without reason. Make them specific enough to feel real.
44. Product naming
When to use: You're naming a product, feature, or company and need options.
Generate 20 name options for [describe the product — what it does, who uses it,
what feeling it should evoke].
Constraints:
- [Available as .com / not important]
- [Max X characters]
- [Avoid: [any words or sounds to stay away from]]
- [Target vibe: technical / friendly / premium / playful / etc.]
Name categories to include:
- Literal descriptors (4)
- Abstract/evocative (4)
- Portmanteaus or invented words (4)
- Metaphor-based (4)
- Single word, simple (4)
For your top 5 picks: explain the name's logic and any risks (hard to spell,
negative connotations in other languages, etc.).
45. Tagline generation
When to use: You need a one-liner that captures what your product does.
Write 10 tagline options for [company or product name].
Product: [what it does]
Audience: [who it's for]
Core benefit: [the most important thing it does for customers]
Competitors' positioning: [how they describe themselves — so you can differentiate]
For each tagline:
- The tagline itself
- The emotional or rational hook it's using
- Who it resonates most with
Mark your top 3. For each, note: what you lose by choosing this one.
46. Pitch deck narrative
When to use: You have the data for a pitch but need the story structure.
Help me build the narrative for a [investor / customer / internal] pitch deck.
Context:
- What we're pitching: [product/idea]
- Audience: [who's in the room and what they care about]
- The ask: [funding / deal / approval]
- Key proof points I have: [list your strongest evidence]
Slide-by-slide narrative outline:
For each slide (8-12 total), give:
- Slide title
- The one thing this slide must communicate
- Key visual or data point
- The emotional or logical hook
Make the problem slide feel urgent without being hyperbolic.
Make the solution slide feel inevitable, not just good.
47. Social media campaign concept
When to use: You're planning a content campaign and need a concept that holds together.
Develop a social media campaign concept for [brand/product launch/event].
Platform(s): [LinkedIn / Instagram / X / TikTok]
Campaign duration: [X weeks]
Goal: [awareness / engagement / signups / followers]
Audience: [describe]
Deliverables:
1. Campaign theme (the big idea in one sentence)
2. Content pillars (3 recurring content types with rationale)
3. Week 1 content plan (5-7 specific post ideas with copy hooks)
4. Hashtag strategy (if relevant)
5. One "hero" piece of content that anchors the campaign
For each post idea: format (image/video/text), hook, and the core message.
48. Metaphor generation
When to use: You're explaining a complex concept and need an analogy that sticks.
Generate 8 metaphors or analogies for explaining [concept] to [audience].
The concept in plain terms: [describe it]
What the audience already knows: [what reference points they have]
What confuses people most about this concept: [the usual sticking point]
For each metaphor:
- The metaphor itself (one sentence)
- How far it extends (what the analogy covers well)
- Where it breaks down (what the analogy gets wrong — so you know when to stop)
Mark the 2 you'd actually use in a presentation and explain why.
49. Analogy explanation
When to use: You need to explain a technical concept to a non-technical audience.
Explain [technical concept] to [audience — e.g., "a VP of Sales with no engineering background"].
Use at least one concrete analogy drawn from [their world — e.g., "sales, pipeline management,
or everyday life"].
Structure:
1. The one-sentence version (if they remember nothing else)
2. The analogy (develop it enough that it actually explains the concept)
3. Why it matters to them specifically (not why it's interesting, why they should care)
4. One question they can ask their engineering team to sound informed
Avoid: jargon without explanation, "basically it's like…" as a cop-out,
and making it sound simpler than it is.
50. Thought leadership angle
When to use: You have an opinion and want to turn it into a compelling piece.
I want to write a thought leadership piece with this core argument: [state your argument]
My evidence for it: [list what you've observed, measured, or experienced]
My audience: [who reads this and what they believe now]
The conventional wisdom I'm challenging: [what most people in this space believe]
Develop:
1. A contrarian angle (the sharpest version of my argument)
2. A compelling opening hook (not a question, not a statistic — a scene or observation)
3. Three supporting arguments, each with a specific example or data point
4. The strongest objection to my argument (and how to address it honestly)
5. A memorable closing line
Then: suggest 3 angles I could take that are even more provocative than my original framing.
Making any prompt work better
Three adjustments that improve any prompt on Claude:
Add an output format instruction. "Return a JSON array" or "Use a numbered list with bold section headers" removes ambiguity. Claude won't guess wrong at a format it's been told explicitly.
Add one example. Even a single example of what good output looks like dramatically reduces format drift. Paste an example of a similar output you liked, or write a short synthetic one.
Add a constraint. "Under 200 words", "no more than 5 bullet points", "don't use passive voice" — constraints force specificity. Claude responds to them well because they're unambiguous.
These 50 prompts are a starting point. The prompt library has copy-paste versions organized by category with additional variations. And if you want to understand the underlying mechanics — why certain structures outperform others on Claude specifically — the Claude Sonnet 4.6 guide covers the model's training profile and prompting patterns in depth.
