40 Best Claude Prompts You Can Copy and Use in 2026

Act as a senior B2B marketing strategist.
Create a practical 90-day marketing strategy for [COMPANY], which sells [PRODUCT] to [AUDIENCE] in [MARKET].
Business goal: [GOAL]
Monthly budget: [BUDGET]
Current channels and performance: [PASTE DATA]
Constraints: [TEAM, SALES CYCLE, REGULATORY OR TECHNICAL LIMITS]
Organise the response into positioning, priority segments, channel strategy, weekly roadmap, campaign ideas, lead nurture, KPIs, risks and assumptions.
Prioritise each activity by impact and effort. Explain why it belongs in the plan. Do not invent performance data. Flag missing information that could materially change the recommendation.

Act as a B2B go-to-market strategist.
Build an ideal customer profile for [PRODUCT].
Current customers: [CUSTOMERS]
Best won deals and why they closed: [WON DEALS]
Lost deals and stated reasons: [LOST DEALS]
Primary region: [REGION]
Average contract value: [VALUE]
Typical sales cycle: [DURATION]
Return firmographic criteria, operational signals, trigger events, urgent problems, buying committee roles, objections, disqualifiers and three ICP tiers.
Separate evidence from assumptions. Mark every assumption clearly and list the customer data needed to validate it.

Act as a product marketing lead.
Develop positioning and messaging for [PRODUCT].
Target audience: [AUDIENCE]
Competitors or alternatives: [COMPETITORS]
Key features: [FEATURES]
Customer evidence: [EVIDENCE]
Current copy: [CURRENT COPY]
Create a positioning statement, category, three differentiated value propositions, homepage message hierarchy, pain-to-outcome messaging for three buyer roles, required proof points, five headlines and a short sales pitch.
Avoid generic phrases such as “best-in-class” or “all-in-one” unless the supplied evidence supports them.

Act as a qualitative research analyst.
Analyse the customer interviews below for [PRODUCT].
Research question: [RESEARCH QUESTION]
<interviews>
[TRANSCRIPTS]
</interviews>
Identify repeated problems, desired outcomes, buying triggers, exact customer language, alternatives considered, decision criteria, objections, urgency and differences by segment.
Return a table with theme, evidence, frequency and marketing implication. Do not generalise from a single interview without labelling it a weak signal.

Act as an integrated campaign strategist.
Create a multi-channel campaign brief for [OFFER] aimed at [AUDIENCE].
Goal: [GOAL]
Channels: [CHANNELS]
Budget: [BUDGET]
Proof or differentiators: [PROOF]
Campaign period: [DATES]
Include audience insight, campaign promise, message hierarchy, offer, channel roles, creative concepts, landing page structure, retargeting, nurture, measurement, tracking requirements and a testing roadmap.
Show how execution changes by channel while preserving one central campaign idea.

Act as an experienced SEO content strategist.
Create a content brief targeting [PRIMARY KEYWORD] for [AUDIENCE].
Secondary keywords and questions: [SECONDARY KEYWORDS]
Business context: [BUSINESS]
Current SERP observations: [SERP NOTES]
Existing pages that may overlap: [URLS]
Include search intent, recommended angle, title, H1, meta description, H2/H3 structure, questions to answer, entities to explain, evidence required, internal links, original visuals, FAQs and cannibalisation risks.
Do not create fake statistics or sources.

Act as a subject-matter editor and writer.
Write an article about [TOPIC] for [AUDIENCE].
Goal: [GOAL]
<sources>
[SOURCES]
</sources>
<voice>
[VOICE]
</voice>
Lead with the direct answer, use a logical heading structure, explain technical ideas plainly, attribute factual claims, distinguish fact from interpretation, include examples and finish with a practical checklist.
Do not invent data. Identify unsupported claims before drafting and omit or qualify them.

Act as an SEO editor.
Refresh the article below for [TARGET KEYWORDS].
<current_article>
[ARTICLE]
</current_article>
Performance data: [PERFORMANCE]
Competitor observations: [COMPETITORS]
Audit intent mismatch, outdated sections, unsupported claims, missing subtopics, repetition, internal links and formatting.
Then provide a revised title, H1, meta description, recommended structure, full revised article, internal links, visuals to add and sections removed with reasons.
Preserve strong original material where it remains accurate.

Act as a content distribution strategist.
Turn the article below into a campaign for [AUDIENCE].
<article>
[ARTICLE]
</article>
Channels: [CHANNELS]
Primary CTA: [CTA]
Create one LinkedIn post, one founder post, one newsletter, one five-slide carousel, three short video scripts, five community questions, ten insight cards and a two-week distribution schedule.
Adapt the tone to each channel. Do not repeat the same opening or copy across every asset.

Act as a rigorous human editor.
Edit this draft for [AUDIENCE].
<draft>
[DRAFT]
</draft>
<voice_sample>
[VOICE SAMPLE]
</voice_sample>
Avoid: [WORDS TO AVOID]
Remove generic openings, vague claims, unnecessary adjectives, repetition and stiff transitions. Preserve useful nuance and the writer’s point of view. Flag unsupported claims.
Return the revised draft first, followed by the most important edits and facts that still need verification.

Act as a sceptical but constructive business reviewer.
Evaluate this business plan for [MARKET].
<business_plan>
[BUSINESS PLAN]
</business_plan>
Constraints: [CONSTRAINTS]
Assess customer urgency, target market, differentiation, revenue model, acquisition, operations, financial assumptions, dependencies, competition and execution risk.
Create a table with claim, evidence, missing evidence, risk and recommended action. Identify the five assumptions most likely to invalidate the plan. Do not invent market or financial data.

Act as a competitive intelligence analyst.
Compare [YOUR COMPANY] with [COMPETITORS] for [SEGMENT].
<research>
[RESEARCH]
</research>
Analyse target users, use cases, positioning, pricing approach, strengths, limitations, proof, distribution and buying objections.
Return a comparison table, competitor battlecards, positioning gaps, claims requiring verification and three defensible differentiation opportunities.
Do not declare a universal winner without defining the customer scenario.

Act as an operations manager.
Turn these notes into a standard operating procedure.
<process_notes>
[PROCESS NOTES]
</process_notes>
Owner: [OWNER]
Tools: [TOOLS]
Quality standard: [QUALITY STANDARD]
Include purpose, scope, prerequisites, roles, numbered procedure, decision points, quality checks, failure modes, escalation, completion criteria, records and review cadence.
Flag ambiguous, unsafe or undocumented steps. Do not invent missing process details.

Act as a strategy lead writing for an executive team.
Prepare a decision memo about [DECISION].
Options: [OPTIONS]
Data: [DATA]
Constraints: [CONSTRAINTS]
Deadline: [DEADLINE]
Use this structure: decision required, summary, context, criteria, option analysis, implications, risks, recommendation, conditions that would change it and immediate next steps.
Be explicit about trade-offs. Distinguish evidence from judgement and identify missing data.

Act as a customer insights analyst.
Analyse this feedback for [PRODUCT AREA].
<feedback>
[FEEDBACK]
</feedback>
Segments: [SEGMENTS]
Identify repeated problems, desired outcomes, feature requests, usability issues, emotional language, churn or expansion signals, segment differences and high-severity issues.
Return a prioritised table with theme, frequency, severity, segment, evidence and recommended owner. Separate product problems from education, support and expectation-setting problems.

Act as a senior engineer joining an unfamiliar codebase.
Repository context: [CONTEXT]
Task: [TASK]
<codebase>
[FILES OR TREE]
</codebase>
Explain the architecture, execution flow, relevant files, dependencies, data flows, conventions and tests. Flag missing files or uncertainties.
Then propose a minimal implementation plan. Do not write code until you explain which files will change, why and how the result will be verified.

Act as a senior debugging partner.
Expected: [EXPECTED]
Actual: [ACTUAL]
Error or logs: [ERROR]
Environment: [ENVIRONMENT]
<code>
[CODE]
</code>
List the likely failure path, competing hypotheses, evidence, smallest diagnostic checks, supported root cause, minimal fix, regression risks and tests.
Do not rewrite unrelated code. If evidence is insufficient, request only the exact information needed to distinguish the leading hypotheses.

Act as a careful pull request reviewer.
Goal: [PR GOAL]
Project conventions: [CONVENTIONS]
<diff>
[DIFF]
</diff>
Review correctness, edge cases, security, performance, data integrity, error handling, compatibility, maintainability and tests.
Group findings as blocking, important and optional. Cite the relevant file or fragment, explain the impact and suggest a concrete change. State clearly when the change appears sound.

Act as a senior engineer performing a behaviour-preserving refactor.
Goal: [GOAL]
Constraints: [CONSTRAINTS]
<code>
[CODE]
</code>
<tests>
[TESTS]
</tests>
Identify behaviour to preserve, hidden coupling, side effects and missing tests. Then provide a step-by-step plan, revised code, updated tests and any behaviour that could not be proven equivalent.
Prefer small changes. Do not introduce a new framework unless it clearly reduces complexity.

Act as a staff software engineer.
Plan [FEATURE].
Requirements: [REQUIREMENTS]
Codebase context: [CODEBASE]
Non-functional requirements: [NON-FUNCTIONAL REQUIREMENTS]
Produce clarified requirements, architecture, data or API changes, affected files, compatibility, failure modes, observability, tests, rollout, rollback and implementation sequence.
After the plan, provide only the first minimal implementation step so it can be reviewed before continuing.

Act as a research analyst.
Answer this question using only the supplied sources:
[QUESTION]
<sources>
[SOURCES]
</sources>
Provide a concise answer, source summaries, areas of agreement, disagreements, methodological differences, evidence limitations, claims supported by multiple sources and unanswered questions.
Do not combine conflicting findings into false consensus. Attribute each important conclusion.

Act as an evidence auditor.
Extract every material [CLAIM TYPE] claim from this document.
<document>
[DOCUMENT]
</document>
Return a table with claim, type, evidence cited, whether the evidence directly supports it, caveats, confidence and verification needed.
Flag causal claims based only on correlation, numbers without sources, outdated evidence and conclusions that extend beyond the data.

Act as a survey research analyst.
Research goal: [GOAL]
Segments: [SEGMENTS]
<survey_data>
[SURVEY DATA]
</survey_data>
Provide sample description, data-quality issues, response distributions, segment differences, non-causal correlations, open-text themes, outliers, implications and follow-up questions.
Show the denominator for percentages. Do not overstate findings from small samples.

Act as an impartial decision analyst.
Options: [OPTIONS]
Criteria: [CRITERIA]
Weights: [WEIGHTS]
Evidence: [EVIDENCE]
Define each criterion, check that weights total 100%, score only where evidence exists, explain scores, mark unknowns, run sensitivity analysis and show which assumptions drive the result.
Provide a conditional recommendation rather than a universal winner.

Act as a research-methods reviewer.
Objective: [OBJECTIVE]
Constraints: [CONSTRAINTS]
<research_plan>
[PLAN]
</research_plan>
Assess method fit, sampling, measurement validity, bias, confounding variables, comparison groups, ethics, privacy, analysis, reproducibility and feasibility.
Return the most serious issues first. Explain why each matters and propose the smallest viable improvement.

Act as an experienced resume editor.
<resume>
[RESUME]
</resume>
<job_description>
[JOB DESCRIPTION]
</job_description>
Identify the role’s main requirements, evidence already in my resume, underemphasised experience, a revised summary, revised bullets, truthful keywords and gaps to address honestly.
Do not invent skills, results, titles, employers or dates.

Act as a resume writer.
Rewrite these experience notes for a [TARGET ROLE] position.
<notes>
[NOTES]
</notes>
Verified metrics: [METRICS]
Use precise action verbs, show scope and outcome, keep bullets concise and prioritise relevance. Do not invent numbers. Mark where a real metric would strengthen a bullet.
Return the revised bullets and the questions needed to make them more specific.

Act as an interview coach.
<job_description>
[JOB DESCRIPTION]
</job_description>
<resume>
[RESUME]
</resume>
Company information: [COMPANY INFO]
Create likely themes, ten role questions, five behavioural questions, answer outlines based only on my experience, weak areas, questions to ask, a 60-second introduction and a final checklist.
Flag requirements for which my resume shows no evidence.

Act as a professional cover-letter editor.
Use my resume and the job description below.
<resume>
[RESUME]
</resume>
<job_description>
[JOB DESCRIPTION]
</job_description>
Motivation: [MOTIVATION]
Company detail: [COMPANY DETAIL]
Write under 350 words. Open specifically, connect two or three relevant achievements, show company understanding, avoid repeating the resume and use only supplied facts.

Act as a LinkedIn profile strategist.
Target role: [TARGET ROLE]
Current profile: [PROFILE]
Experience: [EXPERIENCE]
Verified proof: [PROOF]
Create five headline options, a first-person About section, improved experience bullets, a Featured section plan, skills to prioritise, proof gaps, ten natural keywords and three post ideas.
Do not add credentials, clients or results I did not provide.

Act as a senior web strategist and design lead.
Company: [COMPANY]
Audience: [AUDIENCE]
Conversion goal: [GOAL]
Required pages: [PAGES]
Brand: [BRAND]
References: [REFERENCES]
Create a brief covering business context, user needs, message hierarchy, page goals, navigation, content, visual direction, interactions, accessibility, responsive behaviour, conversion elements, assets, success criteria and open questions.
Do not prescribe trends without connecting them to the audience or goal.

Act as a conversion-focused UX writer and designer.
Offer: [OFFER]
Audience: [AUDIENCE]
Primary pain: [PAIN]
Proof: [PROOF]
CTA: [CTA]
Objections: [OBJECTIONS]
For each section, provide purpose, headline, content, visual, CTA behaviour and proof required. Include hero, problem, solution, how it works, proof, objections, FAQ and final CTA.
Explain the order. Avoid fake urgency and unsupported claims.

Act as a senior product designer conducting a UX review.
Interface or flow: [INTERFACE]
User goal: [USER GOAL]
User type: [USER TYPE]
Constraints: [CONSTRAINTS]
Review hierarchy, labels, task flow, cognitive load, errors, empty states, mobile behaviour, accessibility, trust and conversion friction.
Group findings by severity. Explain the user impact and recommend a concrete change. Mark assumptions when no usability data is available.

Act as a design systems lead.
Product: [PRODUCT]
Platforms: [PLATFORMS]
Brand direction: [BRAND]
Current components: [COMPONENTS]
Define principles, colour roles, typography, spacing, grid, breakpoints, buttons, forms, navigation, cards, feedback states, data display, accessibility, naming, documentation and governance.
Focus on reusable tokens and rules. Flag choices that require accessibility testing.

Act as an accessibility specialist.
Page or component: [PAGE]
Critical flows: [FLOWS]
Technology stack: [TECH STACK]
Review semantics, keyboard navigation, focus, forms, contrast, resizing, images, motion, tables, screen-reader announcements, touch targets and responsive reflow.
Provide manual tests, automated checks and pass criteria. Do not claim compliance without real testing using assistive technologies.

Act as a practical planning assistant.
Tasks: [TASKS]
Deadlines: [DEADLINES]
Available time: [TIME]
Top priorities: [PRIORITIES]
Fixed meetings and constraints: [CONSTRAINTS]
Create a prioritised list, day-by-day schedule, focus blocks, admin blocks, dependencies, tasks to defer or delegate, buffer time and a Friday review.
Do not schedule more work than the available time. Explain unrealistic trade-offs.

Act as a project coordinator.
Project: [PROJECT]
Attendees: [ATTENDEES]
<meeting_notes>
[NOTES]
</meeting_notes>
Return an executive summary, decisions, open questions, action items with owners and deadlines, risks, blockers, dependencies, unconfirmed items and the next agenda.
Do not assign an owner or date unless the notes support it. Mark unclear items “Unconfirmed.”

Act as a project planning lead.
Project goal: [GOAL]
Deadline: [DEADLINE]
Team: [TEAM]
Constraints: [CONSTRAINTS]
Create success criteria, assumptions, workstreams, milestones, tasks, dependencies, owners by role, risks, decisions, review cadence and definition of done.
Identify the critical path and smallest useful first release. Avoid work that does not contribute to the stated outcome.

Act as an expert learning designer.
Skill: [SKILL]
Current level: [LEVEL]
Practical goal: [GOAL]
Weekly time: [TIME]
Resources: [RESOURCES]
Build a skills map, modules, one practical project per stage, exercises, knowledge checks, misconceptions, progression criteria, a capstone and retention schedule.
Prioritise deliberate practice over passive reading. Keep the workload within the stated time.

Act as a thoughtful communications editor.
Recipient: [RECIPIENT]
Situation: [SITUATION]
Desired outcome: [OUTCOME]
Sensitive details: [SENSITIVE DETAILS]
<draft>
[DRAFT]
</draft>
Rewrite the email so it states the purpose early, remains calm, preserves facts, avoids blame, makes the requested action clear and stays concise.
Include a deadline only if supplied. Return the revised email followed by one sentence explaining the tone.