Best Claude Prompts: 50 Examples That Actually Work (2026)

Claude Haiku 5.5 meeting summary from our test, flagging two action items as Owner: Unassigned and Deadline: Missing

Updated October 30, 2026

Fifty copy-ready prompts for Claude, from emails and SWOT analyses to code reviews and meal plans, with the reason each one works.

The short version: These are 50 ready-to-paste prompts for Claude, grouped into writing (10), business (10), research (10), coding (10), learning (5) and creative or personal use (5). Each comes in a copy box with what it does, why it works and how to adapt it. They work on any Claude plan, including Free, and follow Anthropic’s own advice: be clear and direct, give context, and say exactly what format you want. We tested two of them on Claude Haiku 5.5, the fastest and lowest-cost model in the Claude app, on October 30, 2026.

Table of Contents

What’s the bottom line on Claude prompting?

Claude does its best work when you treat it like a capable new colleague who doesn’t know your situation yet. Anthropic’s own advice puts it this way: “Think of Claude as a brilliant but new employee who lacks context on your norms and workflows” (Anthropic). Tell it who the work is for, what “good” looks like, how long it should be and what format you want, and the first draft gets much closer to usable. The 50 prompts below are built that way. Fill in the brackets, paste, and adjust.

What are the key takeaways?

  • 50 copy-paste prompts in six groups: writing, business, research, coding, learning, and creative or personal use.
  • Every prompt sets a role or audience, a clear task, a format and limits; that structure does most of the work.
  • They run on any Claude plan. Free includes Claude Sonnet 5.5 and Haiku 5.5; Opus 5.5 needs Pro or higher.
  • Paste the real material (the email thread, the report, the code). Claude’s current models can read up to 1 million tokens at once, about 2,500 pages of text (Anthropic help).
  • Check what comes back, especially dates, numbers and sources. Our own test caught a wrong weekday.

Why are Claude prompts different from ChatGPT or Gemini prompts?

Mostly, they aren’t: a clear, specific prompt works well in any assistant. What changes is the detail, and Anthropic publishes its own guide to prompting Claude (prompting best practices). The habits it recommends, and that these prompts use:

Anthropic's Claude Platform Docs page Prompting best practices, open at the section Be clear and direct
Anthropic’s own advice. The “Be clear and direct” section of Anthropic’s prompting best practices. Image: Beginners in AI screenshot of platform.claude.com, October 30, 2026.
  • Be clear and direct. Say exactly what you want, including format and limits. Anthropic’s test: if a colleague with no context would be confused by your prompt, Claude will be too.
  • Give the reason. Explaining why you want something (who it’s for, what it’s for) helps Claude make better choices.
  • Show an example. A sample or two of the style you want beats a paragraph describing it; Anthropic suggests 3 to 5 for best results.
  • Use labels or tags for long input. Wrap pasted material in simple tags such as <email> and </email> so Claude knows what is instruction and what is source.
  • Give it a role when expertise matters: “act as a careful editor” or “as a senior data analyst.”
  • Put long documents first and your question after them.

New to Claude? Start with our guide to using Claude, then come back here. For prompting habits that work in every assistant, see how to write AI prompts.

How did 2026 connectors change what a good Claude prompt looks like?

The prompts below are written for a plain chat: you paste your material in and get an answer back. They still work that way. But Claude can now read directly from your email, drive, calendar, Notion, GitHub, Slack and many other apps through connectors, available on every plan (Anthropic). Many use the open Model Context Protocol. Once a connector is on, you stop pasting context and start pointing to it.

The shift in one example

Old prompt (paste everything in):

Paste-in version
Here’s an email thread between me and a client about a contract issue. [paste the thread] Help me write a response that’s professional but firmly rejects their proposed change to section 7.

Connector-aware prompt:

Connector version
Read the most recent thread in my Gmail with [client name] about [project], pull the current contract from my Google Drive folder [folder name], and draft a reply that firmly rejects their proposed change to section 7. Match my tone from my last five sent emails.

No copying and pasting, and no worrying that the version in your chat is out of date. Claude drafts; you review and send it yourself.

What this means for the 50 prompts below

  • No connectors yet (or a workplace that doesn’t allow them): use the prompts as written and paste in your material.
  • Connectors on: treat each prompt as a template. Replace “[paste content here]” with “Pull X from [Gmail, Drive, Notion]”.

Save your best prompts as Skills

Claude Skills are saved instruction packs: write a winning prompt once, give it a name, and Claude uses it whenever it fits. Skills work on every plan, Free included, once code execution is switched on in Settings (Anthropic help). Any prompt below that you’d ship as-is is a Skill candidate. Name it with a verb and an object, such as “summarize-meeting” or “draft-investor-update”. Our Skills vs Connectors vs Plugins guide explains the difference.

What happened when we tested these prompts?

We ran two of the prompts on October 30, 2026, on Claude Haiku 5.5, the fastest and lowest-cost model in the Claude app, to see how far the prompt alone gets you.

Claude Haiku 5.5's meeting summary with numbered sections; two action items are marked Owner: Unassigned and Deadline: Missing with warning signs
Prompt 7, tested. Claude Haiku 5.5 followed the six-part format and flagged both tasks that had no owner or deadline. Image: Beginners in AI test, October 30, 2026.

For prompt 7 (Meeting Summary) we pasted a short, messy transcript in which two tasks had no clear owner. Haiku used all six sections in order and marked both tasks “Owner: Unassigned” and “Deadline: Missing,” exactly what the prompt’s last line asks for.

Claude Haiku 5.5's short, friendly email to a neighbor about trimming tree branches, with a subject line and a proposed Saturday walk-over
Prompt 2, tested. Subject line, one clear ask and a concrete next step, in about 110 words. The one slip: the date it suggested was the wrong weekday. Image: Beginners in AI test, October 30, 2026.

For prompt 2 (Email Drafter) we asked for a friendly note to a neighbor about overhanging branches. It came back well under the 200-word limit, with a subject line, one clear ask and a concrete next step. One slip: it suggested meeting on “Saturday, November 1,” but November 1, 2026 is a Sunday.

From our testTwo prompts, two good results, and one small error that a quick read would catch. Both held up on the fastest, cheapest model. Whatever Claude writes, check the dates, numbers and names before you send it.

What are the best Claude prompts for writing?

These ten cover the writing most people do every week: posts, emails, captions, bios and summaries. Each sets a length, a tone and a structure, which is most of what separates a usable first draft from a generic one.

1. Blog Post Writer

Prompt 1
Write a 1,500-word blog post about [TOPIC]. Target audience: [AUDIENCE]. Tone: conversational but authoritative. Structure it with an introduction that hooks the reader with a specific statistic or surprising fact, 4-5 H2 subheadings that each cover one distinct subtopic, bullet points for scannable takeaways, and a conclusion with a clear call to action. Include at least 3 specific data points or examples. Do not use filler phrases like "in today's fast-paced world" or "it's no secret that."

What it does: Generates a complete blog post with a clear structure, a set length and at least three concrete data points or examples.

Why it works: Word count, audience and tone are set up front, so there is no guessing. Listing banned openers like “in today’s fast-paced world” removes the stock phrases readers spot fastest, and the 3-data-point minimum pushes for substance over padding.

Customization tip: Replace [TOPIC] and [AUDIENCE] with specifics. Add “Write in first person” or “Write in third person” to control voice. For longer posts, increase the word count and add more H2 sections proportionally.

2. Email Drafter

Prompt 2
Draft a professional email for the following situation: [DESCRIBE THE SITUATION, THE RECIPIENT, AND YOUR GOAL]. The email should be no longer than 200 words. Use a [formal/friendly/direct] tone. Include a clear subject line, one specific ask or call to action, and close with a concrete next step (not a vague "let me know"). If there are any sensitive or potentially awkward aspects to handle, handle them diplomatically.

What it does: Creates a concise, purposeful email that gets straight to the point with a specific call to action.

Why it works: A 200-word cap and a single ask keep the email short enough to get read. Asking for a concrete next step instead of “let me know” gives the reader something specific to reply to.

Customization tip: Paste the previous email thread into the prompt for reply drafting. Even a long email chain fits in one go.

3. Social Media Caption

Prompt 3
Write 5 social media captions for [PLATFORM] about [TOPIC/PRODUCT]. Each caption should: be under [CHARACTER LIMIT] characters, include a hook in the first line that stops scrolling, use [BRAND VOICE, e.g., witty, inspiring, educational], end with a clear CTA, and include 3-5 relevant hashtags. Format: number each caption and put the hashtags on a separate line below each one.

What it does: Generates multiple caption options with platform-appropriate formatting, hooks, and engagement elements.

Why it works: Five versions give you options to pick from, while the shared rules (character limit, hook, CTA, 3-5 hashtags) keep every one usable. A fixed format, numbered with hashtags on their own line, makes them easy to copy.

Customization tip: Specify the platform character limits (X/Twitter: 280, LinkedIn: 3,000, Instagram: 2,200). Claude aims to stay under them, but run a quick character count before posting.

4. Product Description

Prompt 4
Write a product description for [PRODUCT NAME]. Details: [LIST KEY FEATURES, SPECS, PRICE, TARGET CUSTOMER]. The description should be 150-200 words, lead with the primary benefit (not a feature), include 3 specific features that map to customer pain points, use sensory or emotional language where appropriate, and end with a reason to buy now. Avoid superlatives like "best" or "revolutionary" unless you can back them up with data I provide.

What it does: Creates benefit-driven product copy that sells by connecting features to customer needs.

Why it works: Leading with a benefit tells Claude to start from what the buyer gets, not the spec sheet. Banning “best” and “revolutionary” unless you supply data stops empty hype, and the 150-200 word range keeps it tight.

Customization tip: Paste customer reviews or testimonials into the prompt. Claude will extract the language your customers use and mirror it in the description.

5. Resume Bullet Points

Prompt 5
Rewrite the following job responsibilities into strong resume bullet points using the XYZ formula (Accomplished [X] as measured by [Y] by doing [Z]). Current responsibilities: [PASTE YOUR CURRENT JOB DUTIES]. For each bullet: start with a strong action verb, include a quantifiable result (estimate reasonable metrics if I haven't provided them, flag these as estimates), and keep each bullet to one line (under 120 characters). Generate 6-8 bullets and rank them by impact.

What it does: Turns bland job descriptions into quantified, achievement-focused resume bullets that are easy for recruiters and screening software to scan.

Why it works: The XYZ formula gives each bullet the same familiar shape: result, measure, method. Telling Claude to flag estimated numbers keeps invented metrics from slipping onto your resume unnoticed, and ranking by impact shows you which bullets to lead with.

Customization tip: Add “Target role: [JOB TITLE]” to tailor the language to your desired position’s keywords.

6. Cover Letter

Prompt 6
Write a cover letter for the following job posting: [PASTE FULL JOB DESCRIPTION]. My background: [PASTE RESUME OR KEY QUALIFICATIONS]. The letter should be 300-400 words, open with a specific reason I'm excited about THIS company (not generic enthusiasm), connect exactly 3 of my qualifications to their stated requirements, include one brief story or specific example that demonstrates a relevant skill, and close with confidence without being arrogant. Do not start with "I am writing to apply for."

What it does: Creates a personalized, compelling cover letter that directly maps your qualifications to the job requirements.

Why it works: You paste the real job posting, so Claude can match your skills to the employer’s own wording. Capping it at exactly 3 qualifications forces focus, and banning “I am writing to apply for” removes the most common, forgettable opener.

Customization tip: Add the company’s “About Us” page text so Claude can reference specific company values and initiatives.

7. Meeting Summary

Prompt 7
Summarize the following meeting transcript into a structured meeting summary. Transcript: [PASTE TRANSCRIPT]. Format the summary as: 1) Meeting title, date, and attendees, 2) Three-sentence executive summary, 3) Key decisions made (bulleted list), 4) Action items with owner and deadline for each, 5) Open questions or unresolved issues, 6) Next meeting date/agenda items if mentioned. If any action items are missing a clear owner or deadline, flag them explicitly.

What it does: Converts raw meeting transcripts into structured, actionable summaries with tracked action items.

Why it works: Working from the full transcript means Claude summarizes what was said, not what it guesses. The numbered six-part format gives every summary the same shape, and flagging tasks with no owner or deadline catches what would otherwise slip.

Customization tip: Use this with Zoom, Otter.ai, or Fireflies transcripts pasted directly. Add “Also note any off-topic tangents that consumed more than 2 minutes” to improve future meeting efficiency.

8. Press Release

Prompt 8
Write a press release for the following announcement: [DESCRIBE THE NEWS]. Company details: [NAME, LOCATION, WHAT YOU DO]. Follow AP style and standard press release format: headline (under 80 characters), dateline, lead paragraph answering who/what/when/where/why, 2-3 body paragraphs with supporting details and context, one direct quote from [SPOKESPERSON NAME AND TITLE], boilerplate "About [COMPANY]" paragraph, and media contact information placeholder. Keep the total length under 500 words.

What it does: Produces a properly formatted, AP-style press release ready for you to review and send.

Why it works: Spelling out every required part in order (headline under 80 characters, dateline, a who/what/when/where/why lead, quote, boilerplate) works like a checklist. Claude fills each slot, and the 500-word ceiling keeps it the length editors expect.

Customization tip: Add “Include a statistic or data point in the lead paragraph” to make the release more newsworthy and quotable.

9. Newsletter

Prompt 9
Write a weekly newsletter edition about [TOPIC/THEME]. Newsletter name: [NAME]. Audience: [DESCRIBE SUBSCRIBERS]. Structure: 1) Subject line (under 50 characters, curiosity-driven), 2) Opening hook, a surprising stat, question, or observation (2-3 sentences), 3) Main story (300 words) with a clear insight or lesson, 4) 3 curated links with one-sentence descriptions of why each matters, 5) One actionable tip readers can implement today, 6) Sign-off with a question to encourage replies. Total length: under 600 words. Tone: [SPECIFY].

What it does: Creates a complete newsletter edition with engagement-optimized structure and curated content.

Why it works: Each section comes with its own job and length, from a sub-50-character subject line to a 300-word main story. With a 600-word cap on top, the issue stays balanced instead of turning into one long essay.

Customization tip: Paste your last 2-3 newsletter editions into the prompt so Claude can match your established voice and format.

10. Speech Outline

Prompt 10
Create a detailed outline for a [LENGTH]-minute speech about [TOPIC]. Audience: [DESCRIBE]. The outline should include: an opening hook (story, question, or startling fact, give me 2 options), a clear thesis statement, 3 main points with 2 supporting sub-points each, transition sentences between main points, one audience interaction moment (question, show of hands, or brief exercise), a memorable closing that calls back to the opening hook, and estimated time allocation per section. Mark places where I should pause, use visuals, or shift tone.

What it does: Generates a detailed, time-allocated speech outline with delivery cues and audience engagement moments.

Why it works: Two hook options give you a choice before you commit. Requesting timings plus pause and visual cues makes Claude write for speaking out loud, not just for reading, and the callback ending ties the talk together.

Customization tip: Specify whether the speech is for a conference, team meeting, classroom, or toast. Claude will adjust formality and interaction style accordingly.

What are the best Claude prompts for business and strategy?

These ten turn Claude into a planning partner: SWOT analyses, plans, personas, pricing and hiring documents. Give each one real numbers and names from your business; Claude can only be as specific as what you paste in.

11. SWOT Analysis

Prompt 11
Conduct a SWOT analysis for [COMPANY/PRODUCT/IDEA]. Context: [PROVIDE RELEVANT DETAILS, industry, size, stage, competitors]. For each quadrant (Strengths, Weaknesses, Opportunities, Threats), provide exactly 5 items. Each item should be: one specific sentence (not vague), grounded in the context I provided, and actionable, meaning I can either build on it (S/O) or reduce it (W/T). After the four quadrants, add a "Strategic Implications" section with 3 prioritized recommendations that connect specific strengths to specific opportunities.

What it does: Produces a structured SWOT analysis with actionable strategic recommendations grounded in your specific context.

Why it works: “Exactly 5 items” per quadrant stops thin sections from being padded and strong ones from running long. Requiring each item to be one specific sentence tied to your context blocks generic filler, and the final section links strengths to opportunities.

Customization tip: Paste your company’s latest annual report or investor deck for deeper, more data-grounded analysis.

12. Business Plan Section

Prompt 12
Write the [SPECIFIC SECTION, e.g., "Market Analysis" or "Financial Projections"] section of a business plan for [BUSINESS DESCRIPTION]. Industry: [INDUSTRY]. Target market: [DESCRIBE]. Stage: [idea/startup/growth/mature]. The section should be 800-1,000 words, include at least 3 cited data points (use recent industry reports, cite the source), present information in a format an investor or loan officer would expect, and flag any assumptions I should validate with my own research. If I haven't provided enough information for a credible section, tell me exactly what data points you need.

What it does: Drafts an investor-style business plan section with cited data and clearly flagged assumptions for you to verify.

Why it works: Asking Claude to flag assumptions and say what data it still needs turns gaps into a to-do list rather than hidden guesses. Check every cited report yourself, because AI tools can produce sources that look real but are not.

Customization tip: Run this prompt for each section sequentially, pasting the previous sections into each new prompt so Claude maintains consistency across the full plan.

13. Competitive Analysis

Prompt 13
Create a competitive analysis comparing [YOUR PRODUCT/SERVICE] against these competitors: [LIST 3-5 COMPETITORS]. Analyze each competitor across these dimensions: 1) Core value proposition, 2) Pricing model and price points, 3) Target customer segment, 4) Key strengths, 5) Key weaknesses, 6) Market positioning. Present this as a comparison table, then write a 200-word "Competitive Advantage Summary" identifying the gaps in the market that [YOUR PRODUCT] can exploit. Be blunt about where competitors are stronger, I need real intelligence, not validation.

What it does: Delivers a candid side-by-side look at your competitors, with a table for quick scanning and a summary of gaps in the market.

Why it works: Six fixed comparison points and a table keep every competitor judged on the same terms. The line “I need real intelligence, not validation” gives Claude permission to say where rivals beat you, which AI assistants tend to soften unless asked.

Customization tip: Paste the text of competitor pricing and product pages into the prompt, or turn on web search, so Claude works from current details instead of memory.

14. Customer Persona

Prompt 14
Create a detailed customer persona for [PRODUCT/SERVICE]. What I know about my customers: [SHARE ANY DATA, demographics, behaviors, feedback, purchase patterns]. Build the persona with: Name and demographic snapshot, Job title and daily responsibilities, 3 primary goals related to my product category, 3 frustrations/pain points with current solutions, Buying behavior (how they research, who influences them, what triggers a purchase), Preferred communication channels, A direct quote that captures their mindset (written as if from a real interview), and One "surprising insight", something about this persona that's counterintuitive but strategically valuable.

What it does: Builds a rich, actionable customer persona that goes beyond demographics into motivations and decision-making patterns.

Why it works: Handing over your own customer data grounds the persona in facts instead of stereotypes. The “surprising insight” slot asks for one non-obvious angle, and the interview-style quote makes the persona easier for a team to remember.

Customization tip: Paste real customer support tickets, survey responses, or reviews to give Claude real voice-of-customer data to work from.

15. Marketing Strategy

Prompt 15
Develop a 90-day marketing strategy for [PRODUCT/SERVICE]. Budget: [AMOUNT or "limited/moderate/substantial"]. Current situation: [DESCRIBE, new launch, growth stage, rebrand, etc.]. Target audience: [DESCRIBE]. The strategy should include: 3 specific, measurable goals with KPIs, channel recommendations (ranked by expected ROI for my budget level), a week-by-week timeline for the first 30 days with specific deliverables, content themes for each month, 2 quick wins I can execute this week, and 1 experimental tactic to test. For each channel, estimate the time commitment required so I can assess feasibility.

What it does: Creates a time-bound, budget-aware marketing plan with measurable goals and a concrete execution timeline.

Why it works: A 90-day window, a stated budget and measurable KPIs (the numbers you track to judge success) give the plan hard edges. A week-by-week first month, two quick wins and time estimates per channel turn strategy into tasks you can schedule.

Customization tip: Add “My team consists of [X people] with these skills: [LIST]” to get feasibility-adjusted recommendations.

16. Pricing Strategy

Prompt 16
Help me develop a pricing strategy for [PRODUCT/SERVICE]. Current pricing: [IF ANY]. Costs: [YOUR COSTS/MARGINS]. Competitor pricing: [LIST WHAT YOU KNOW]. Target market: [DESCRIBE]. Analyze 3 viable pricing models for my situation (e.g., freemium, tiered, usage-based, flat-rate, per-seat). For each model: explain the pros and cons for MY specific situation, recommend specific price points with reasoning, project the impact on customer acquisition vs. revenue per customer, and identify the key metric I should track to know if it's working. End with your top recommendation and why.

What it does: Evaluates multiple pricing models against your specific business context and recommends the best approach, with the reasoning behind it.

Why it works: Your costs and competitor prices give Claude real numbers to reason from. Comparing exactly 3 pricing models against the same four questions keeps the comparison fair, and asking for a top recommendation means you get a decision, not just a list.

Customization tip: Include your current conversion rate and customer lifetime value if known. Claude will factor these into its ROI projections.

17. Job Description

Prompt 17
Write a job description for a [JOB TITLE] role at [COMPANY TYPE/SIZE]. This role is responsible for: [KEY RESPONSIBILITIES]. Reports to: [ROLE]. Team size: [X]. Structure the description with: a 2-3 sentence role summary that sells the opportunity (not just lists duties), "What You'll Do" section with 6-8 specific responsibilities (action-verb format), "What You'll Bring" section split into "Required" (5-6 real requirements) and "Nice to Have" (3-4 real preferences), salary range: [RANGE or "competitive"], and one section on culture/benefits that feels authentic, not corporate-generic. Avoid exclusionary language and unnecessary requirements that could limit the candidate pool.

What it does: Produces an inclusive, compelling job description that attracts qualified candidates by balancing requirements with appeal.

Why it works: Separate “Required” and “Nice to Have” lists with set counts stop wish lists from posing as must-haves. The explicit request to avoid exclusionary language and needless requirements keeps qualified people from ruling themselves out.

Customization tip: Paste a top performer’s real work output or achievements, and Claude will reverse-engineer the skills and traits that matter most for the role.

18. Performance Review

Prompt 18
Help me write a performance review for [EMPLOYEE NAME/ROLE]. Review period: [TIMEFRAME]. Key accomplishments: [LIST]. Areas for development: [LIST]. Overall rating: [EXCEEDS/MEETS/BELOW EXPECTATIONS]. Write the review with: an opening summary paragraph that sets a constructive tone, 3-4 specific achievement paragraphs (each tied to a business outcome, not just activity), 2 development areas framed as growth opportunities with specific, actionable suggestions, 2-3 goals for the next review period that are SMART (Specific, Measurable, Achievable, Relevant, Time-bound), and a closing paragraph. The tone should be candid, specific, and growth-oriented, not corporate fluff. Every piece of feedback should include a specific example.

What it does: Creates a thorough, balanced performance review with specific examples and actionable development goals.

Why it works: You supply the accomplishments and rating, so the review rests on facts you know. Requiring a specific example for every point and SMART goals (specific, measurable, achievable, relevant, time-bound) keeps the feedback concrete and fair.

Customization tip: Run a second prompt: “Now write a self-review from the employee’s perspective based on the same facts” to prepare for a two-way conversation.

19. Project Brief

Prompt 19
Create a project brief for [PROJECT NAME]. Objective: [WHAT WE'RE TRYING TO ACHIEVE]. People involved: [LIST]. Timeline: [DURATION]. Budget: [AMOUNT/RANGE]. The brief should include: Problem statement (what's broken or missing today, 2-3 sentences), Project objectives (3-5 SMART goals), Scope (what's included AND what's explicitly excluded), Key deliverables with target dates, Success metrics (how we'll know this worked), Risks (top 3) with mitigation strategies for each, Resource requirements, and Decision rights (who approves what). Keep it under 2 pages. Use a professional but readable tone, this will be shared with both executives and the implementation team.

What it does: Produces a complete project brief that gets everyone involved to agree on scope, success criteria, and decision-making before work begins.

Why it works: Most briefs skip the out-of-scope list, so requesting it heads off scope creep later. Naming both audiences (executives and the delivery team) tells Claude who has to follow it, and the two-page limit means busy readers will finish it.

Customization tip: Add “The main source of disagreement among the people involved is [X]” and Claude will address that tension directly in the brief.

20. Sales Email Sequence

Prompt 20
Write a 5-email sales sequence for [PRODUCT/SERVICE]. Target buyer: [DESCRIBE, role, company size, pain points]. Sequence structure: Email 1 (Day 1): Cold intro, lead with a pain point, not your product. Under 100 words. Email 2 (Day 3): Value-add, share a useful insight or resource. No hard sell. Email 3 (Day 7): Social proof, case study or specific result. Include one number. Email 4 (Day 10): Direct offer with clear CTA and deadline/urgency element. Email 5 (Day 14): Breakup email, final touch, respectful close, leave the door open. For each email: write the subject line, body, and CTA. Subject lines should be under 40 characters and avoid spam trigger words. All emails should feel like they come from a real person, not a marketing system.

What it does: Creates a complete 5-email outbound sales sequence with strategic escalation from value-first to direct offer.

Why it works: Every email has a set day, job and word limit, so the sequence builds instead of repeating itself. Asking that each one feel like it comes from a real person, with no spam trigger words, pushes toward plain language over marketing-speak.

Customization tip: After generating, ask: “Now write 3 alternative subject lines for each email, optimized for open rate” to A/B test.

What are the best Claude prompts for research and analysis?

These ten help you read, compare and check information. Turn on web search for anything recent, and check any source Claude cites before you rely on it; AI can produce references that look real but aren’t.

21. Literature Review

Prompt 21
I'm researching [TOPIC] for a [paper/report/presentation]. Here are [X] sources I've gathered: [PASTE ABSTRACTS, EXCERPTS, OR FULL TEXTS]. Create a literature review that: groups the sources thematically (not chronologically), identifies 3-4 key themes or debates in the literature, notes where sources agree and where they contradict each other, identifies gaps in the current research that future work could address, and maintains an objective academic tone. Use in-text citations in [APA/MLA/Chicago] format. End with a synthesis paragraph that connects the themes to my research question: [STATE YOUR QUESTION].

What it does: Synthesizes multiple sources into a cohesive, thematically organized literature review with proper academic formatting.

Why it works: Claude works from the sources you paste, not from memory, so its citations point to texts you can check. Grouping by theme, not date, surfaces agreements, contradictions and gaps.

Customization tip: For systematic reviews, add: “Also create a table summarizing each source’s methodology, sample size, key finding, and limitation.”

22. Data Analysis Prompt

Prompt 22
Analyze the following dataset: [PASTE DATA OR DESCRIBE THE DATASET]. I want to understand: [STATE YOUR SPECIFIC QUESTIONS, e.g., "What factors most strongly predict customer churn?"]. Please: 1) Describe the dataset (size, variables, data types, any obvious quality issues), 2) Identify the 3 most important patterns or trends, 3) Note any outliers or anomalies that warrant investigation, 4) Suggest 2-3 statistical tests or analyses that would answer my questions (explain why each is appropriate), 5) Summarize findings in plain English, as if presenting to a non-technical colleague, 6) List 3 follow-up questions the data raises. If the data is insufficient to draw reliable conclusions, say so explicitly.

What it does: Provides a structured data analysis with statistical recommendations, plain-language findings, and a frank look at the data’s limits.

Why it works: Six numbered steps, from describing the data to follow-up questions, keep the analysis orderly. The plain-English summary makes results usable for non-experts, and permission to call the data insufficient discourages finding patterns that are not there.

Customization tip: Paste CSV data directly into the prompt, or upload the file. For large spreadsheets, uploading works better, and Claude can run analysis code on the file when its code tool is turned on.

23. Market Research

Prompt 23
Conduct market research analysis for [PRODUCT/SERVICE/INDUSTRY]. What I need to understand: market size and growth trajectory, key customer segments and their needs, competitor overview (major players and market share distribution), barriers to entry, current trends shaping the market, and regulatory factors if applicable. Structure the output as a market research brief that I could present to investors or leadership. Include specific numbers and cite sources where possible. Where you're uncertain about a data point, give your best estimate and mark it clearly as "[ESTIMATE]" so I know what to verify independently. End with 3 strategic implications for my business.

What it does: Creates an investor-ready market research brief with data, competitive analysis, and strategic implications.

Why it works: Marking uncertain figures as “[ESTIMATE]” shows you exactly which numbers to verify before they reach investors. A fixed list of topics, from market size to regulation, keeps the brief complete, and the closing implications tie it back to your business.

Customization tip: Provide your target geography (“US only” or “Global excluding China”) for more focused market sizing.

24. Pros/Cons Analysis

Prompt 24
I need to decide between these options: [LIST 2-4 OPTIONS WITH BRIEF DESCRIPTIONS]. My priorities are (ranked): [LIST WHAT MATTERS MOST TO YOU]. My constraints are: [BUDGET, TIMELINE, TEAM SIZE, etc.]. For each option, provide: 5 specific pros (tied to my stated priorities), 5 specific cons (including hidden costs or risks I might not have considered), a suitability score from 1-10 for my specific situation, and one "deal-breaker" scenario, a situation where this option would clearly be the wrong choice. Then provide your recommendation with reasoning. Be direct, I need a clear recommendation, not "it depends."

What it does: Delivers a structured decision-analysis framework with weighted evaluation against your specific priorities and constraints.

Why it works: Ranking your priorities and naming constraints gives Claude a yardstick for every option. The deal-breaker scenario exposes when each choice fails, and “not ‘it depends’” pushes past the hedging AI assistants often fall back on.

Customization tip: Add “My risk tolerance is [low/medium/high]” to shift the analysis toward safer or more aggressive options accordingly.

25. Executive Summary

Prompt 25
Write an executive summary of the following document: [PASTE FULL DOCUMENT]. The summary should be [250/500/750] words and structured for [AUDIENCE, e.g., C-suite, board of directors, team leads]. Include: the core problem or opportunity (1-2 sentences), key findings or recommendations (bulleted, no more than 5), financial impact or resource implications if applicable, recommended next steps with timeline, and the single most important thing the reader should remember. Write it so that someone who reads ONLY this summary can make an informed decision without reading the full document.

What it does: Condenses lengthy documents into decision-ready executive summaries tailored to specific audience levels.

Why it works: Giving Claude the full document, not a summary of it, means nothing important is lost before the work starts. Setting the word count, the audience and the single thing to remember makes it decision-ready for someone who reads nothing else.

Customization tip: For board decks, add: “Include a risk section and frame recommendations as decision points with clear options.”

26. Fact-Checking

Prompt 26
Fact-check the following text: [PASTE CONTENT TO CHECK]. For each factual claim in the text: 1) Identify the claim, 2) Rate your confidence in its accuracy: CONFIRMED (you're very confident it's correct), LIKELY (probably correct but you have some uncertainty), UNVERIFIABLE (you can't confirm or deny), LIKELY INCORRECT (probably wrong), or INCORRECT (you're confident it's wrong), 3) Provide the correct information if the claim is wrong, 4) Note the basis for your assessment. Also flag any misleading framing, claims that are technically true but presented in a way that could lead to wrong conclusions. Summarize: how many claims total, how many confirmed, how many flagged.

What it does: Systematically evaluates factual claims with a confidence-rated framework that distinguishes between certainty levels.

Why it works: Five confidence labels, from CONFIRMED to INCORRECT, are more useful than a yes/no verdict because they show where doubt sits. Asking for the basis of each rating and a final tally tells you which claims still need checking against a real source.

Customization tip: For scientific or medical claims, add: “Apply a higher evidence standard, require peer-reviewed sources for CONFIRMED rating.”

27. Trend Analysis

Prompt 27
Analyze the current trends in [INDUSTRY/TOPIC] as of [MONTH YEAR]. Structure your analysis as: 1) Top 5 trends, ranked by likely impact over the next 12 months, for each trend, provide evidence it's real (not just hype), who's affected most, and what it means practically for [MY ROLE/BUSINESS], 2) One "contrarian take", a widely discussed trend that you think is overblown, with reasoning, 3) One "under-the-radar" trend that isn't getting enough attention, 4) A 3-sentence "so what" summary I could share with my team. Base this on publicly available information up to your training cutoff. Be specific, I want named companies, real products, and real developments, not generic trend labels.

What it does: Delivers a ranked, evidence-based trend analysis with both consensus and contrarian perspectives.

Why it works: Requiring evidence that each trend is real, plus one contrarian and one overlooked pick, pushes past the usual buzzword list. Named companies and products make vague claims easy to spot. Treat very recent events with care, since Claude’s knowledge stops at a training cutoff.

Customization tip: Add “My company is in [SECTOR] with [SIZE] employees” so Claude can filter trends through your specific relevance lens.

28. Survey Question Generator

Prompt 28
Generate a survey to measure [WHAT YOU WANT TO LEARN] from [TARGET RESPONDENTS]. Create 15 questions following these rules: Mix of question types (Likert scale, multiple choice, open-ended, ranking), Start with easy/non-threatening questions and progress to more sensitive ones, Include 1 attention-check question to filter low-quality responses, No double-barreled questions (one concept per question), No leading questions (neutral wording), Include skip logic recommendations (e.g., "If Q3 = No, skip to Q7"). For each question, note what insight it provides and how I'd use the response data. Estimate completion time. End with 3 questions I should NOT ask (and why), common mistakes for surveys on this topic.

What it does: Creates a methodologically sound survey with proper question design, flow logic, and quality controls.

Why it works: Ruling out double-barreled questions (two questions in one) and leading wording builds standard survey rules into the request. Noting what each question measures keeps every item earning its place, and the “3 questions NOT to ask” section flags common traps.

Customization tip: Specify your survey tool (Google Forms, Typeform, SurveyMonkey) and ask Claude to stick to question types that tool supports. Confirm skip logic in the tool itself, since features vary by plan.

29. Report Outline

Prompt 29
Create a detailed outline for a report on [TOPIC]. Report type: [annual report/research report/audit report/white paper/internal memo]. Target audience: [DESCRIBE]. Expected length: [PAGES/WORDS]. The outline should include: section titles and sub-sections (3 levels deep), a 1-2 sentence description of what each section should contain, suggested data visualizations or tables for each section (describe what the chart would show), the key question each section should answer, and recommended sources or data I'll need to gather. Organize the sections in a logical flow that builds an argument toward [THE MAIN CONCLUSION OR RECOMMENDATION].

What it does: Produces a full report blueprint with section descriptions, data visualization suggestions, and research requirements.

Why it works: Three levels of headings, a key question per section and a stated end conclusion give the outline a spine. Suggested charts and a list of data to gather turn the outline into a research plan too.

Customization tip: Add “The report needs to convince [SKEPTICAL AUDIENCE] of [CONCLUSION]” to sharpen the argumentative structure.

30. Source Evaluation

Prompt 30
Evaluate the following source for credibility and usefulness for my research on [TOPIC]: [PASTE THE SOURCE TEXT OR DESCRIBE IT WITH PUBLICATION, AUTHOR, DATE]. Assess the source on: 1) Authority, author credentials and publication reputation, 2) Accuracy, are claims verifiable? Any obvious errors?, 3) Objectivity, signs of bias, funding sources, or conflicts of interest, 4) Currency, is the information current enough for my purpose?, 5) Coverage, how thoroughly does it address the topic?, 6) Methodology, if it's research, is the methodology sound? Give an overall rating: PRIMARY SOURCE (build arguments on this), SUPPORTING SOURCE (use to supplement), BACKGROUND ONLY (provides context but don't cite directly), or UNRELIABLE (don't use). Explain your rating in 2-3 sentences.

What it does: Provides a structured credibility assessment of research sources using established evaluation criteria.

Why it works: Six named criteria (authority, accuracy, objectivity, currency, coverage, methodology) make the review systematic instead of a gut call. The four-level rating tells you exactly how to use the source, from building arguments on it to leaving it out.

Customization tip: Batch multiple sources in one prompt: “Evaluate these 5 sources and rank them by reliability for my specific research question.”

What are the best Claude prompts for coding?

These ten work in a normal chat for reviewing, fixing and explaining code. For bigger jobs across many files, Claude Code (on paid plans) does the same work directly in your project.

31. Code Review

Prompt 31
Review the following code for quality, bugs, and improvements: [PASTE CODE]. Language: [LANGUAGE]. Context: [WHAT THE CODE DOES]. Review for: 1) Bugs or logical errors (critical, flag these first), 2) Security vulnerabilities (SQL injection, XSS, etc.), 3) Performance issues (O(n²) loops, unnecessary database calls, memory leaks), 4) Code style and readability (naming, structure, comments), 5) Edge cases not handled, 6) Suggestions for improvement (explain why, not just what). Rate each finding as CRITICAL, IMPORTANT, or NICE-TO-HAVE. Show corrected code for any CRITICAL findings. Don't just say "looks good", find at least 3 concrete suggestions even if the code is solid.

What it does: Performs a thorough code review with severity-rated findings, security checks, and corrected code for critical issues.

Why it works: Severity labels (CRITICAL, IMPORTANT, NICE-TO-HAVE) and a fixed checklist tell you what to fix first. Requiring at least 3 suggestions even for solid code stops a lazy “looks good” reply, and corrected code for critical issues saves a round trip.

Customization tip: Add your team’s style guide or linting rules, and Claude will review against your specific standards, not generic best practices.

32. Bug Fix

Prompt 32
I have a bug in my code. Here's the code: [PASTE CODE]. Expected behavior: [WHAT SHOULD HAPPEN]. Current behavior: [WHAT'S HAPPENING INSTEAD]. Error message (if any): [PASTE ERROR]. What I've already tried: [LIST DEBUGGING STEPS]. Please: 1) Identify the root cause (not just the symptom), 2) Explain WHY the bug occurs (help me understand, not just fix), 3) Provide the corrected code, 4) Show me how to verify the fix works, 5) Suggest a test case that would have caught this bug, 6) Note if this bug pattern could exist elsewhere in similar code. If you need more context (e.g., other files, configuration, dependencies), tell me exactly what you need.

What it does: Diagnoses and fixes bugs with root-cause analysis, educational explanation, and preventive testing recommendations.

Why it works: Listing expected behavior, what happens instead, the error and what you have tried gives Claude the full picture and rules out repeat suggestions. Asking for the root cause and a test that would have caught it helps you learn, not just patch.

Customization tip: Include your stack details (framework versions, OS, runtime). Bugs that only show up in one version are common, and these details help Claude find them.

33. Refactor

Prompt 33
Refactor the following code to improve [readability/performance/maintainability/testability, pick one primary goal]: [PASTE CODE]. Language: [LANGUAGE]. Context: [WHAT IT DOES AND WHERE IT FITS IN THE CODEBASE]. Constraints: [ANY REQUIREMENTS, e.g., "must maintain backward compatibility," "can't add new dependencies," "must keep the public API unchanged"]. Please: 1) Show the refactored code, 2) Explain each change and why it improves the code, 3) List any trade-offs introduced by the refactoring, 4) Explain how I can check that the refactored version produces the same outputs, 5) If the refactoring is large, show it in stages so I can apply incrementally. Do NOT refactor just to make the code "look different." Every change should have a clear benefit.

What it does: Produces a principled code refactoring with clear rationale, trade-off analysis, and incremental implementation guidance.

Why it works: A refactor restructures code without changing what it does, and naming one main goal for it keeps the changes focused. The rule against refactoring just to look different means every change must justify itself, and staged changes let you apply and test one piece at a time.

Customization tip: Paste your team’s coding standards document and ask Claude to refactor toward those specific standards.

34. Write Tests

Prompt 34
Write thorough tests for the following code: [PASTE CODE]. Language: [LANGUAGE]. Testing framework: [Jest/pytest/JUnit/etc.]. The test suite should include: happy path tests (expected inputs → expected outputs), edge case tests (empty inputs, boundary values, maximum sizes), error case tests (invalid inputs, network failures, permission errors), at least one integration test if the code interacts with external services, and clear test names that describe the expected behavior (not "test1", "test2"). Aim for [X]% code coverage. For each test, add a one-line comment explaining what scenario it covers. If the code is hard to test, suggest refactoring changes that would improve testability.

What it does: Generates a thorough test suite with edge cases, error handling, and clear documentation of test purpose.

Why it works: Listing test categories (normal inputs, edge cases, error cases) makes coverage deliberate. Descriptive test names and one-line comments mean anyone can read the suite months later, and asking for testability tips flags code that is hard to check.

Customization tip: Add “My CI pipeline runs [TOOL], ensure test output format is compatible” for immediate integration.

35. Explain Code

Prompt 35
Explain the following code to me as if I'm a [beginner/intermediate/senior] developer: [PASTE CODE]. I want to understand: 1) What does this code do overall? (2-3 sentence summary), 2) Walk through the code line-by-line (or section-by-section for longer code), explaining the purpose and logic, 3) What design patterns or techniques does it use? (name them), 4) What are the inputs and outputs?, 5) Where could this code fail, and how does it handle (or not handle) failures?, 6) If you were explaining this to my team, what's the one thing you'd emphasize? Use analogies where they help, but don't oversimplify technical concepts, I want to learn it properly.

What it does: Provides a multi-level code explanation from high-level summary through line-by-line walkthrough to design pattern identification.

Why it works: Stating your skill level sets the vocabulary and depth. The numbered questions move from a short summary to a section-by-section walkthrough, and the request not to oversimplify keeps analogies as helpers, not replacements for the real explanation.

Customization tip: Specify your background: “I know Python well but I’m new to Go”. Claude will bridge from familiar concepts to unfamiliar ones.

36. API Integration

Prompt 36
Write code to integrate with [API NAME, e.g., Stripe, Twilio, SendGrid]. Language: [LANGUAGE]. Framework: [IF APPLICABLE]. I need to: [DESCRIBE WHAT YOU WANT TO DO, e.g., "process payments," "send SMS notifications," "manage email lists"]. Include: 1) Environment setup (dependencies, API key configuration, never hardcode secrets), 2) Authentication setup, 3) The main integration code with error handling, 4) Retry logic for transient failures (with exponential backoff), 5) Logging for debugging, 6) A simple test to verify the integration works (using the API's test/sandbox mode if available), 7) Rate limiting considerations. Add comments explaining any non-obvious API quirks or gotchas you know about.

What it does: Produces API integration code with security basics, error handling, retries and a test, ready for you to review before it goes live.

Why it works: Breaking the job into seven parts, from setup to retries with exponential backoff (waiting longer before each new attempt), stops Claude from handing back a bare snippet. “Never hardcode secrets” keeps API keys out of your code. Check the result against the API’s current docs.

Customization tip: Paste the API’s rate limit documentation and ask Claude to build the rate limiter to match exactly.

37. Database Query

Prompt 37
Write a [SQL/MongoDB/etc.] query for the following: [DESCRIBE WHAT DATA YOU NEED]. Database structure: [DESCRIBE YOUR TABLES/COLLECTIONS, or paste your schema]. Requirements: The query should be optimized for performance on a table with [APPROXIMATE ROW COUNT] rows. Include appropriate indexes if needed (suggest CREATE INDEX statements). Add comments explaining the logic of any complex joins, subqueries, or window functions. If there are multiple ways to write this query, show the most performant option and briefly explain why it's faster. Also show the execution plan analysis approach (EXPLAIN/EXPLAIN ANALYZE) so I can verify performance.

What it does: Creates performance-optimized database queries with indexing recommendations, inline documentation, and performance verification guidance.

Why it works: Pasting your schema (the list of your tables and columns) means the query uses your real names and data types. A row-count estimate guides the indexing advice, and asking for EXPLAIN steps lets you confirm the speed yourself.

Customization tip: Add “Database: [PostgreSQL 16/MySQL 8/etc.]”. SQL dialects differ, and Claude will use version-specific features and syntax.

38. Documentation

Prompt 38
Write documentation for the following code: [PASTE CODE]. Documentation type: [API docs/README/inline comments/user guide, pick one]. Audience: [developers on my team/open source contributors/non-technical users]. Include: 1) Overview, what this code does and why it exists (not just what, but why), 2) Setup/installation instructions (prerequisites, dependencies, environment variables), 3) Usage examples, at least 3, progressing from simple to advanced, 4) API reference, every public function/method with parameters, return values, and exceptions, 5) Common pitfalls or FAQ (at least 3 items), 6) Troubleshooting section for the most likely errors. Write for someone who's encountering this code for the first time. If the code has poor naming or structure that makes documentation difficult, note that as a suggestion.

What it does: Generates complete, audience-appropriate documentation with practical examples and troubleshooting guidance.

Why it works: Naming the audience and one documentation type tells Claude how much to explain. Asking for the “why” behind the code, three examples that grow from simple to advanced, and a troubleshooting section covers what newcomers most often need.

Customization tip: Specify your documentation tool (JSDoc, Sphinx, Swagger) and Claude will format output in that tool’s expected syntax.

39. Regex Generator

Prompt 39
Create a regular expression that matches [DESCRIBE THE PATTERN YOU NEED TO MATCH]. Here are example strings that SHOULD match: [LIST 3-5 EXAMPLES]. Here are example strings that should NOT match: [LIST 3-5 EXAMPLES]. Language/engine: [JavaScript/Python/PCRE/etc.]. Please: 1) Provide the regex pattern, 2) Explain each part of the pattern in plain English, 3) Show test cases proving it works (matches what it should, rejects what it shouldn't), 4) Note any edge cases that might cause unexpected matches or misses, 5) If the regex is complex, provide a simpler alternative that covers 90% of cases (with a note about what the 10% misses are). Performance note: will this pattern cause catastrophic backtracking on long strings?

What it does: Builds tested, documented regular expressions with plain-English explanations and edge case analysis.

Why it works: Matching and non-matching examples give Claude clear targets, and the test cases prove the pattern against them. The backtracking question checks whether the pattern can freeze on long text, a speed and security risk, and the simpler 90% version gives a safer fallback.

Customization tip: Always include the target engine, JavaScript and Python regex engines handle lookbehinds and Unicode differently.

40. Architecture Review

Prompt 40
Review the following system architecture for [PROJECT/APPLICATION]: [DESCRIBE OR PASTE DIAGRAM/DESCRIPTION, include components, data flows, technology choices, and scale requirements]. Evaluate: 1) Does the architecture meet the stated requirements? (identify any gaps), 2) Scalability, where are the bottlenecks as traffic grows 10x and 100x?, 3) Reliability, single points of failure?, 4) Security, data flow security, authentication/authorization design, 5) Cost efficiency, are there overengineered components for the current scale?, 6) Operational complexity, is this reasonable for a team of [SIZE]? Rate each area GREEN (solid) / YELLOW (workable but has risks) / RED (needs attention before production). Provide 3 prioritized recommendations.

What it does: Delivers an architecture review across six areas with traffic-light ratings and prioritized recommendations tailored to your team’s capacity.

Why it works: Concrete growth scenarios (10x and 100x traffic) turn vague scaling talk into specific bottlenecks. Six review areas with GREEN, YELLOW or RED ratings give a quick visual read, and tying advice to your team size keeps recommendations realistic.

Customization tip: Include your current monthly infrastructure cost. Claude can identify savings opportunities by comparing your architecture to more cost-efficient alternatives.

What are the best Claude prompts for learning?

These five make Claude a patient tutor: layered explanations, study guides, quizzes and lesson plans. Tell it what you already know, and ask it to quiz you before it explains more.

41. Explain Concept

Prompt 41
Explain [CONCEPT] to me. My current understanding: [DESCRIBE WHAT YOU ALREADY KNOW, EVEN IF IT'S "NOTHING"]. My background: [RELEVANT CONTEXT, e.g., "I'm a marketing manager," "I have a biology degree," "I'm 16"]. Explain it in 3 layers: 1) The 30-second version, one paragraph I could repeat to someone at dinner, 2) The 5-minute version, enough to understand how it works and why it matters, with an analogy from everyday life, 3) The deep dive, technical details, nuances, common misconceptions, and how experts think about this concept. After all three layers, give me 3 questions I should be able to answer if I truly understand this concept. If my stated current understanding contains any misconceptions, correct them gently but directly.

What it does: Provides a layered explanation at three depth levels, corrects existing misconceptions, and tests understanding with verification questions.

Why it works: Three set layers (30-second, 5-minute, deep dive) stop the answer from landing too simple or too technical. Describing what you already know lets Claude correct misconceptions directly, and the three check questions let you test whether it stuck.

Customization tip: Add “I learn best through [visual descriptions/step-by-step processes/real-world examples/mathematical formulas]” to match your learning style.

42. Study Guide

Prompt 42
Create a study guide for [SUBJECT/EXAM/TOPIC]. My current knowledge level: [BEGINNER/INTERMEDIATE/ADVANCED]. Time available: [HOW LONG UNTIL THE EXAM OR DEADLINE]. The study guide should include: 1) The 10 most important concepts I must understand (ranked by exam importance/real-world relevance), 2) For each concept: a 2-3 sentence summary, one memory aid (mnemonic, analogy, or visual), and one practice question, 3) A study schedule that fits my timeframe, which topics to study first and how much time per topic, 4) 5 common mistakes students make on this material, 5) 3 "If you only have 1 hour" priorities, 6) Recommended study techniques for this specific type of material (not generic study tips). If this material is cumulative (Topic B requires understanding Topic A), note the prerequisites clearly.

What it does: Builds a prioritized, time-aware study plan with memory aids, practice questions, and study technique recommendations.

Why it works: Your level and deadline shape the schedule, so the plan fits the time you have. Ranking the 10 key concepts, adding a memory aid and practice question for each, and noting prerequisites tells you what to study first.

Customization tip: Paste your syllabus or textbook table of contents for a study guide perfectly mapped to your course structure.

43. Quiz Generator

Prompt 43
Create a quiz on [TOPIC] to test my understanding. Difficulty: [EASY/MEDIUM/HARD/MIXED]. Generate 15 questions: 5 multiple choice (with 4 options each, make the wrong answers plausible, not obviously wrong), 5 true/false (include the reasoning for each answer), 3 short answer, 2 scenario-based application questions (present a situation and ask me to apply the concept). For each question: indicate the difficulty level and which sub-topic it tests. Provide all answers in a separate section at the end (not inline, I want to attempt the quiz first). Include a scoring guide: what score indicates mastery vs. what score means I need more study.

What it does: Creates a 15-question quiz with four question types, believable wrong answers and a scoring guide for self-assessment.

Why it works: “Make the wrong answers plausible” forces multiple-choice options that test understanding, not guesswork. A mix of question types, answers held to the end so you can try first, and a scoring guide turn it into a proper self-test.

Customization tip: After taking the quiz, paste your answers and ask: “Grade my quiz and explain every question I got wrong. What does my error pattern tell you about my understanding gaps?”

44. Lesson Plan

Prompt 44
Create a lesson plan for teaching [TOPIC] to [AUDIENCE, age group and knowledge level]. Duration: [LENGTH OF LESSON]. Learning objectives: by the end, students should be able to [LIST 2-3 SPECIFIC, MEASURABLE OUTCOMES]. Structure the plan with: 1) Hook/opening activity (5 min), something that creates curiosity, 2) Direct instruction (explain the concept, include the key points and teaching sequence), 3) Guided practice (an activity where students apply the concept with support), 4) Independent practice (an activity where students apply it alone), 5) Assessment, how to check if learning objectives were met, 6) Extension activity for fast finishers. Include specific questions to ask at each stage (not just "discuss"). Timing for each section. Note common student misconceptions about this topic and how to address them.

What it does: Produces a complete, classroom-ready lesson plan with engagement strategies, assessment tools, and misconception-aware teaching notes.

Why it works: A familiar teaching sequence (hook, instruction, guided practice, independent practice, assessment) builds in scaffolding, meaning support that fades as students gain skill. Asking for timings, specific questions and likely misconceptions makes the plan ready to teach.

Customization tip: Add “My classroom has [X] students and [LIST AVAILABLE RESOURCES, technology, manipulatives, etc.]” for logistically feasible activities.

45. ELI5 Explainer

Prompt 45
Explain [COMPLEX TOPIC] like I'm 5 years old. Rules: Use only words a 5-year-old would know (if you must use a big word, immediately define it in simple terms), use a concrete analogy from a child's world (playground, toys, food, family, animals), keep it under 200 words, make it accurate, don't sacrifice correctness for simplicity. After the ELI5 version, give me a "Now that you're 15" version (300 words, more nuance, some technical terms introduced gently). Then give me the "adult expert" version (300 words, full complexity, proper terminology). This should feel like zooming in on a map, same territory, increasing detail.

What it does: Provides three zoom levels of explanation from kindergarten-simple to expert-level, using the same core analogy thread.

Why it works: A child’s-world analogy and a 200-word cap force real simplicity, while “don’t sacrifice correctness” keeps it accurate. Building up to 15-year-old and expert versions, like zooming in on a map, shows how the pieces connect.

Customization tip: For social sharing, the ELI5 version often makes the best content. Ask Claude to convert it into a social media post or short video script.

What are the best Claude prompts for creative and personal use?

These five are for life outside work: stories, recipes, trips, gifts and meal plans. Double-check anything with real-world stakes, such as opening hours, prices and allergens.

46. Story Outline

Prompt 46
Create a detailed story outline for a [GENRE] [short story/novel/screenplay]. Premise: [YOUR BASIC IDEA, even if it's rough]. The outline should include: 1) One-sentence logline, 2) Three-act structure with major plot points for each act, 3) Main character profile, name, defining trait, internal conflict, external goal, and a specific flaw that drives the plot, 4) 2-3 supporting characters with their relationship to the protagonist and their own motivations, 5) The central conflict and its escalation beats (at least 4 stages of increasing stakes), 6) The climax, what choice does the protagonist face?, 7) The resolution, how has the character changed?, 8) 3 potential opening scenes (give me options). Theme: what is this story really about beneath the plot? If my premise has structural weaknesses, tell me, I'd rather fix them now than in draft 3.

What it does: Generates a full story outline with character arcs, escalating conflict and theme, plus frank feedback on weak spots in the structure.

Why it works: An eight-part checklist (logline, three acts, character flaw, escalation, climax, resolution, opening options) covers the bones of a story. Inviting Claude to name structural weaknesses gets you critique now, when fixing the premise costs least.

Customization tip: Specify “tone of [REFERENCE WORK, e.g., ‘tone of The Martian’ or ‘atmosphere of Blade Runner’]” for targeted creative direction.

47. Recipe Modification

Prompt 47
Modify this recipe to fit my dietary needs: [PASTE RECIPE OR DESCRIBE THE DISH]. My dietary requirements: [LIST, e.g., "gluten-free," "reduce sodium by 50%," "make it vegan," "under 500 calories per serving"]. Please: 1) List every substitution with the original ingredient → replacement, 2) Explain why each substitution works (chemistry/texture/flavor), 3) Note any technique changes needed (cooking time, temperature, method), 4) Flag if any substitution significantly changes the taste or texture, set my expectations, 5) Provide adjusted nutritional estimate per serving (calories, protein, key macros), 6) Suggest one optional addition that would elevate the modified version. If the dish fundamentally can't be made well with these restrictions (e.g., "make a soufflé without eggs"), say so plainly and suggest an alternative dish that achieves the same flavor profile.

What it does: Adapts recipes to dietary restrictions with the food science behind each swap and realistic expectations about the result.

Why it works: Asking Claude to explain every swap and flag taste or texture changes sets fair expectations before you cook. The escape clause, suggesting a different dish when a version can’t work, keeps you from wasting ingredients on a doomed recipe.

Customization tip: Add “I live in [LOCATION]”. Ingredient availability varies by region, and Claude will suggest locally available alternatives.

48. Travel Itinerary

Prompt 48
Plan a [NUMBER]-day trip to [DESTINATION]. Travel dates: [DATES OR SEASON]. Budget: [$ PER DAY or TOTAL]. Travel style: [budget backpacker/mid-range comfort/luxury]. Interests: [LIST, e.g., food, history, nature, nightlife, art]. Constraints: [ANY, mobility issues, traveling with kids, dietary restrictions]. Create a day-by-day itinerary with: specific locations and attractions (not generic "explore the city"), recommended restaurants with cuisine type and price range, transportation between locations with estimated time and cost, one off-the-beaten-path recommendation per day (something most tourists miss), daily budget breakdown, and one "rest moment" per day (you can't sprint for 12 hours). Also include: 3 things to book in advance, 3 local customs or etiquette tips, and packing essentials specific to this destination and season.

What it does: Creates a realistic, budget-tracked travel itinerary with specific venues, local tips, and practical logistics.

Why it works: Budget, travel style and constraints narrow the options from the start. Asking for specific places, transport times and a daily “rest moment” makes the plan something you can follow on the ground. Double-check opening hours and prices before booking, since details change.

Customization tip: After generating, ask: “Now create an alternative rainy-day plan for any outdoor-heavy days” for weather resilience.

49. Gift Ideas

Prompt 49
Suggest 10 gift ideas for [DESCRIBE THE PERSON, relationship, age, interests, personality]. Budget: [RANGE]. Occasion: [BIRTHDAY/HOLIDAY/THANK YOU/etc.]. For each suggestion: Name the specific product or experience (not generic "a book", which book?), explain why it fits this specific person (connect to their interests/personality), provide a price estimate, and rate the "thoughtfulness factor", will this feel generic (3/10) or deeply personal (10/10)? Include a mix of: 3 physical gifts, 3 experience gifts, 2 consumable gifts (food, drink, subscription), and 2 wildcard/creative gifts they would never think of themselves. Avoid: [LIST ANYTHING TO EXCLUDE, e.g., "they already have too many books," "no alcohol"]. End with your #1 recommendation and why.

What it does: Generates specific, thoughtful gift recommendations with personalization reasoning and a diverse gift category mix.

Why it works: Requiring a named product, a reason it fits and a “thoughtfulness” score for each idea stops generic suggestions. A fixed category mix and an avoid list shape the spread, and ending with one top pick saves you from choosing between ten.

Customization tip: Add their social media bio or a description of their home/office. Claude will pick up on personality cues and style preferences.

50. Meal Planning

Prompt 50
Create a 7-day meal plan. Dietary requirements: [LIST]. Weekly grocery budget: [AMOUNT]. Cooking skill: [beginner/intermediate/advanced]. Time available: [WEEKNIGHT COOKING TIME, e.g., "30 minutes max on weekdays, more time on weekends"]. Household size: [NUMBER OF PEOPLE]. For each day, provide: breakfast, lunch, dinner, and one snack. Each meal should include: the dish name, approximate prep+cook time, calorie estimate, and the recipe (ingredient list + brief instructions). Design the plan so that: ingredients overlap between meals (minimize waste), prep-ahead opportunities are noted ("cook extra rice on Monday for Wednesday's stir-fry"), the most complex meals are on weekends, and the grocery list is consolidated and organized by store section. End with the total weekly grocery list with estimated costs.

What it does: Produces a complete weekly meal plan with recipes, grocery list, prep-ahead strategies, and waste-minimizing ingredient overlap.

Why it works: Shared ingredients across meals, prep-ahead notes and harder recipes on weekends give Claude clear planning rules. Your budget, cooking time and skill level keep it realistic, and a grocery list organized by store section makes shopping quick.

Customization tip: Add “We eat [CUISINE PREFERENCES] and dislike [SPECIFIC FOODS]” for a plan you’ll enjoy following. After the first week, ask Claude to generate Week 2 that introduces variety while reusing any leftover ingredients.

Beginners in AI free community on Skool: learn AI in fourteen days, master it in 30, one small win a day, zero experience needed

How do you get the most from these Claude prompts?

These 50 are starting templates, not rigid scripts. More ready-made prompts live in our AI prompt library, and these habits help with any of them:

  • Fill in every bracket. “Write about marketing” gets generic advice. “Write about email marketing for a small bakery with 400 subscribers” gets something you can use.
  • Paste, don’t summarize. Claude can read whole documents and long email chains; give it the source instead of your summary of it. Our AI tokens explainer shows how much fits.
  • Keep going in the same chat. “Good, now make it more casual” or “expand section 3 and cut section 5” works better than starting over.
  • Say what you don’t want. “No jargon,” “don’t start with a question” and “no bullet points here” all help.
  • Ask for the format up front. A table, a numbered list, headings or plain paragraphs: say which.
  • Check before you use it. Read dates, numbers, names and any sources Claude cites. In our test, a wrong weekday slipped into an otherwise good email.

Frequently Asked Questions

What makes a good Claude prompt?

Four parts: context (who you are and who it’s for), a specific task, the format you want back, and limits (length, tone, what to avoid). Anthropic’s guidance adds two more: explain why you want it, and show an example when the style matters (Anthropic). Swap vague words like “good” or “detailed” for something checkable, such as “under 200 words” or “for a reader who has never used a spreadsheet.”

Are Claude prompts different from ChatGPT prompts?

Less than people think. A clear, specific prompt works in both, and most of the prompts on this page would work in ChatGPT too. Claude-specific touches are small: tags around pasted material, and pasting very long documents, since Claude can hold about 2,500 pages of text at once. Our ChatGPT vs Claude vs Gemini comparison covers the bigger differences.

How long should a Claude prompt be?

As long as it needs to be to remove guesswork. For everyday tasks, a few sentences to a short paragraph is plenty. When you paste long material, put it first and your instructions after it, as Anthropic recommends (Anthropic); research on long inputs found models use information at the start and end better than in the middle (Liu et al.). A one-line prompt usually gets a generic answer.

Can I save prompts in Claude?

Yes, in two ways. Projects keep instructions and files that apply to every chat inside them; Free includes up to five projects and paid plans more (Anthropic; Projects guide). Skills save a prompt as a named, reusable instruction that Claude uses when it fits, on every plan (Anthropic help). Many people also keep favorites in a notes app.

What is Claude’s system prompt?

A system prompt is a set of instructions loaded before a conversation that shapes how the AI behaves. Anthropic sets one for the Claude apps. You can add your own standing instructions through personal preferences, Projects or Skills, and developers using the Claude API write their own system prompts for their apps. That is why Claude can behave a little differently in other companies’ apps.

Start Using Better Prompts Today

Pick the three prompts closest to your week, fill in the brackets, and try them today. Keep the ones that work, adjust the ones that almost work, and save your favorites as Skills. Clear context, a specific task and a defined format will get you most of the way.

More Claude Guides from Beginners in AI

Which Claude model produces the best results for which prompt type?

What you’re doingClaude Haiku 5.5Claude Sonnet 5.5Claude Opus 5.5
Quick rewrites and short draftsYes: fastStrongMore than you need
Long-form writingFine for draftsYes: the everyday defaultFor final polish
Business analysis with many stepsLightStrongYes, on hard problems
Coding, one fileGood for routine fixesYes: everyday workhorseFor tricky refactors
Coding across a projectNot idealStrongYes, with Claude Code
Reading many long sourcesWorks, less depthGoodYes
Which plans have itAll, including FreeAll, including FreePro, Max, Ultra

Start with Sonnet 5.5 for daily work (it’s on every plan; paid users can default to Opus 5.5, which Anthropic recommends for most work), drop to Haiku 5.5 for quick, high-volume jobs, and switch to Opus 5.5 when a task needs deeper reasoning. Fable 5.1, which Anthropic calls its top model, is included on Max and Ultra (up to half of the weekly allowance) and available on Pro with usage credits (Anthropic pricing; models overview).

Made for regular people, by a real person

One AI tip or prompt a day, in plain English, including new ways to get more from Claude. Curated and edited by a human.

Free forever. Unsubscribe anytime.

Sources and official Anthropic documentation

For background, see AI tokens explained, our AI glossary and the Anthropic Academy courses.

Last reviewed: October 30, 2026.

You May Also Like