100+ Claude Prompt Examples for Every Use Case (2026): Copy & Paste Ready

Target audience: [DESCRIBE YOUR IDEAL CUSTOMER] Brand voice: [FORMAL/CASUAL/PROFESSIONAL/FRIENDLY] Main goal: [EDUCATE/SELL/BUILD RELATIONSHIP]

For each email, provide:

Product/Service: [WHAT YOU SELL] Average order value: [AMOUNT] Customer segment: [DESCRIBE THE INACTIVE CUSTOMERS]

Include:

• Compelling subject lines that create urgency
• Personalization placeholders
• A special offer or incentive
• Clear calls to action
• Appropriate spacing between emails

Key features:

• [FEATURE 1]
• [FEATURE 2]
• [FEATURE 3]

The email should:

Ad Copy

Target audience: [DEMOGRAPHICS AND PSYCHOGRAPHICS] Main benefit: [PRIMARY VALUE PROPOSITION] Price: [COST] Goal: [CONVERSIONS/LEADS/TRAFFIC]

For each variation, use a different approach:

Each ad should include:

• Headline (40 characters max)
• Primary text (125 characters for mobile optimization)
• Description (optional, 30 characters)
• Call to action suggestion

Landing page: [URL OR DESCRIBE THE PAGE] Unique selling proposition: [WHAT MAKES YOU DIFFERENT] Target location: [GEOGRAPHIC TARGET] Main competitor: [WHO YOU ARE COMPETING AGAINST]

Create 3 responsive search ad variations with:

• 15 headlines (30 characters each)
• 4 descriptions (90 characters each)

• Keyword variations
• Benefits
• Numbers/statistics
• Calls to action
• Trust signals

Campaign objective: [LEAD GEN/BRAND AWARENESS/CONVERSIONS] Content offer: [WHAT ARE YOU PROMOTING - WEBINAR/WHITEPAPER/DEMO]

Write 3 variations:

Each should include:

• Intro text (150 words max for best engagement)
• Headline for the image/card
• Call to action button text

Landing Pages

Target customer: [WHO THIS IS FOR] Main pain point: [PROBLEM YOU SOLVE] Key differentiator: [WHY YOU ARE DIFFERENT] Pricing: [PRICING STRUCTURE]

Structure the page as follows:

Target audience: [WHO WILL DOWNLOAD THIS] Problem it solves: [MAIN PAIN POINT] Value proposition: [WHAT THEY WILL LEARN/GET]

Include:

Social Media

Target audience: [WHO SHOULD ENGAGE] Goal: [THOUGHT LEADERSHIP/LEAD GEN/ENGAGEMENT] My expertise: [RELEVANT BACKGROUND]

For each post:

• Write in first person
• Use line breaks for readability
• Include a hook in the first line
• End with a question or call to engagement
• Suggest relevant hashtags (3-5)
• Keep each post between 150-300 words

Post themes:

My audience: [DESCRIBE YOUR FOLLOWERS] My perspective: [YOUR UNIQUE ANGLE] Goal: [EDUCATE/ENTERTAIN/PROMOTE]

Structure:

• Hook tweet (must stop the scroll)
• 8-12 content tweets
• Summary/conclusion tweet
• CTA tweet

• Each tweet must stand alone as valuable
• Use simple language (8th grade reading level)
• Include specific numbers and examples
• One clear idea per tweet
• Natural transitions between tweets
• End with something shareable or actionable

Target audience: [WHO FOLLOWS YOU] Content goal: [SAVES/SHARES/PROFILE VISITS]

Create content for 10 slides: Slide 1: Hook/title slide (bold statement or question) Slides 2-8: Main content (one key point per slide) Slide 9: Summary or key takeaway Slide 10: Call to action

For each slide provide:

• Headline text (5-7 words max, visible on small screens)
• Supporting text (1-2 short sentences)
• Visual suggestion

• Caption (encourage saves and shares)
• 20 relevant hashtags (mix of sizes)
• First comment text

Content Strategy

Industry: [YOUR INDUSTRY] Main topics we cover: [LIST 3-5 TOPIC AREAS] Business goals: [TRAFFIC/LEADS/SALES/AUTHORITY] Publishing frequency: [X POSTS PER WEEK]

For each post idea, provide:

• Working title (SEO-optimized)
• Target keyword
• Search intent (informational/commercial/transactional)
• Content type (how-to/listicle/comparison/guide)
• Funnel stage (awareness/consideration/decision)
• Word count target
• Brief outline (5-7 main sections)

• Quick wins (lower competition keywords)
• Authority builders (comprehensive guides)
• Commercial intent (product/service related)
• Trending topics (timely content)

Original content summary: [BRIEF DESCRIPTION] Key points covered:

Create a repurposing plan with actual content for:

About us: [BRIEF DESCRIPTION] Target audience: [WHO WE SERVE] Our values: [3-5 CORE VALUES] Competitors sound like: [DESCRIBE COMPETITOR TONE] We want to sound different by: [HOW YOU WANT TO STAND OUT]

Create comprehensive voice guidelines including:

Marketing Analysis

Their website: [URL] Their social channels: [LIST KNOWN CHANNELS] What they sell: [PRODUCTS/SERVICES] Our overlap: [HOW WE COMPETE]

Analyze and provide insights on:

What we sell: [DESCRIPTION] Current customers include: [ANY KNOWN DEMOGRAPHICS] Price point: [PRICING] Main benefit: [PRIMARY VALUE]

Create 3 distinct customer personas. For each persona include:

Product/Service: [WHAT WE ARE PROMOTING] Budget range: [APPROXIMATE BUDGET] Timeline: [CAMPAIGN DURATION] Primary goal: [MAIN OBJECTIVE] Secondary goal: [SECONDARY OBJECTIVE]

Develop a complete campaign brief including:

Direct Response

Product type: [DIGITAL PRODUCT/COURSE/SERVICE/SOFTWARE] Price: [AMOUNT] Target buyer: [WHO WILL BUY THIS] Main problem solved: [PRIMARY PAIN POINT] Main result delivered: [PRIMARY OUTCOME]

Structure the sales page with these sections:

Product: [NAME AND BRIEF DESCRIPTION] Price: [AMOUNT] Audience: [WHO IS WATCHING] Biggest pain point: [WHAT KEEPS THEM UP AT NIGHT] Unique mechanism: [WHAT MAKES YOUR SOLUTION DIFFERENT]

Follow this VSL framework:

Topic: [WHAT THE WEBINAR TEACHES] Audience: [WHO WILL ATTEND] Goal: [SELL PRODUCT/GENERATE LEADS/BUILD AUTHORITY] Product being sold (if any): [WHAT YOU ARE PITCHING]

Create:

Conversion Optimization

Current performance: [ANY METRICS YOU HAVE] Traffic level: [MONTHLY VISITORS] Current conversion rate: [IF KNOWN] Business context: [ANY RELEVANT CONTEXT]

For each hypothesis, provide:

Context: [WHERE THE BUTTON APPEARS] Audience: [WHO WILL SEE IT] Product/offer: [WHAT THEY GET] Current CTA: [WHAT YOU ARE USING NOW]

Create variations using different approaches:

• Benefit-focused (what they get)
• Action-focused (what they do)
• Urgency-focused (why now)
• Social proof-focused (who else)
• Fear-based (what they miss)
• Curiosity-based (what they discover)
• Value-focused (worth/price)
• Personal (first person: "my")
• Direct (second person: "your")
• Playful (if brand appropriate)

• Button text (2-5 words)
• Supporting text that could appear below
• Which approach it uses

What we offer: [PRODUCT/SERVICE] Goal of popup: [EMAIL CAPTURE/DISCOUNT/CONTENT] Offer: [WHAT THEY GET FOR NOT LEAVING] Brand tone: [DESCRIBE YOUR VOICE]

Create 3 different popup variations:

For each variation include:

Approaches:

• Variation 1: FOMO/scarcity angle
• Variation 2: Value/benefit angle
• Variation 3: Question/engagement angle

Product/Service: [WHAT THEY BOUGHT] Timeline: [WHEN WE SEND THIS] What we are asking for: [VIDEO/WRITTEN/STAR RATING] Incentive (if any): [WHAT WE OFFER]

Create 3 emails:

Email 1: Initial request

• Warm, grateful tone
• Specific about what kind of feedback helps
• Simple yes/no question to gauge willingness

• Different angle
• Make it even easier
• Provide specific prompts

• Last chance framing
• Emphasize impact and appreciation
• Alternative options (if video is too much, offer written)

• Testimonial prompts (questions to ask)
• Video testimonial guidelines (if applicable)
• Release form language

Average cart value: [AMOUNT] Product type: [WHAT THEY LEFT BEHIND] Typical customer: [WHO SHOPS WITH YOU] Current recovery rate: [IF KNOWN]

Email 1 (1 hour after abandonment):

• Helpful reminder tone
• No discount yet
• Address potential technical issues

• Highlight product benefits
• Add social proof
• Create some urgency

• Introduce incentive (discount/free shipping)
• Address common objections
• Scarcity if applicable

• Final chance
• Best offer
• Clear deadline

• Subject line (with 2 alternatives)
• Preview text
• Email body
• CTA
• Dynamic product block description

---

Content Creation Prompts (22 Examples)

Whether you are writing blog posts, newsletters, or social content, these prompts help you create compelling content faster.

Blog Writing

Target keyword: [PRIMARY KEYWORD] Target audience: [WHO WILL READ THIS] Word count: [TARGET LENGTH] Tone: [PROFESSIONAL/CONVERSATIONAL/TECHNICAL]

Structure the post with:

SEO requirements:

• Include the target keyword in H1 and first paragraph
• Use related keywords naturally throughout
• Write a meta description (155 characters)
• Suggest internal linking opportunities
• Suggest 3 external sources to reference

Example: "15 Productivity Hacks That Actually Work"

Target audience: [WHO IS THIS FOR] Main goal: [INFORM/ENTERTAIN/CONVERT] Each item should be: [BRIEF/DETAILED]

Structure:

• Introduction (why this matters, what they will learn)
• List items with consistent format:

• Conclusion (summary and next steps)

• Specific and actionable
• Organized logically (most important first, or categorical)
• Mix of obvious and surprising items
• Practical, not theoretical

Target reader: [WHO NEEDS THIS - SKILL LEVEL] End result: [WHAT THEY WILL ACHIEVE] Time to complete: [HOW LONG THE PROCESS TAKES] Requirements: [WHAT THEY NEED BEFORE STARTING]

Format the guide with:

Options being compared: [WHAT YOU ARE COMPARING] Comparison criteria: [WHAT MATTERS TO YOUR AUDIENCE] Target reader: [WHO NEEDS THIS COMPARISON] Any bias to declare: [IF YOU PREFER ONE OPTION]

Structure:

Subject: [WHO OR WHAT THE CASE STUDY IS ABOUT] Industry: [THEIR FIELD] Challenge: [PROBLEM THEY FACED] Solution: [WHAT WE DID] Results: [OUTCOMES ACHIEVED]

Format the case study as:

Include placeholders for:

• Before/after data
• Screenshots or visuals
• Direct quotes

Newsletter Content

Subscriber profile: [WHO SUBSCRIBES] Newsletter voice: [TONE AND STYLE] Length preference: [SHORT/MEDIUM/LONG] Primary goal: [INFORM/ENGAGE/SELL]

Include these sections:

What the newsletter covers: [TOPICS] Publishing schedule: [FREQUENCY] What makes it different: [UNIQUE VALUE] Who writes it: [AUTHOR INFO]

The welcome email should:

Social Content

The situation: [WHAT HAPPENED] The struggle: [WHAT MADE IT HARD] The turning point: [WHAT CHANGED] The lesson: [WHAT I LEARNED] The application: [HOW READERS CAN USE THIS]

Structure it as:

• Hook (first line that stops scrolling)
• Context (quick setup)
• Tension (the struggle)
• Resolution (what changed)
• Insight (the takeaway)
• CTA (engagement prompt)

• Be vulnerable but not oversharing
• Specific details make it real
• The lesson should be applicable to others
• End with a question or invitation to share

My perspective: [YOUR STANCE] Why I believe this: [YOUR REASONING] Evidence: [SUPPORTING POINTS] Target audience: [WHO SHOULD CARE]

The post should:

Tone: Confident but not arrogant. Provocative but not inflammatory.

Learning objective: [WHAT THEY WILL LEARN] Complexity level: [BEGINNER/INTERMEDIATE/ADVANCED] Number of slides: [7-10]

For each slide provide:

Slide structure:

• Slide 1: Hook/title (promise or question)
• Slides 2-8: One concept per slide (progressive)
• Slide 9: Summary/key takeaway
• Slide 10: CTA (follow for more, save this, share with someone)

• Caption (300-500 words, storytelling + value)
• First comment (engagement prompt)
• Hashtag set (20-30, mixed reach sizes)

Long-Form Content

Scope: [WHAT THIS COVERS] Target reader: [WHO AND WHAT THEY WANT TO ACHIEVE] Word count: [8000-15000 WORDS] Unique angle: [YOUR PERSPECTIVE/APPROACH]

Structure:

Topic: [WHAT THE EBOOK TEACHES] Reader: [WHO WILL DOWNLOAD THIS] Format: [PDF/DIGITAL] Goal: [LEAD GENERATION/AUTHORITY/SALES]

Structure:

Cover page elements:

• Title
• Subtitle
• Author/company

Introduction

• Why this topic matters
• What they will learn
• How to use this ebook
• About the author/company

• Chapter title
• Learning objectives
• Main content (teaching)
• Examples/case studies
• Key takeaways
• Action items

• Summary
• Next steps
• How to go further (your product/service)

• Pull quotes for emphasis
• Callout boxes for tips
• Checklists where helpful
• Placeholder notes for visuals

Topic: [SUBJECT MATTER] Audience: [DECISION MAKERS - TITLES AND INDUSTRIES] Purpose: [EDUCATE/PERSUADE/ESTABLISH AUTHORITY] Length: [WORD COUNT]

White paper structure:

Content Optimization

Original publish date: [WHEN IT WAS PUBLISHED] Target keyword: [PRIMARY KEYWORD] Current performance: [RANKING/TRAFFIC IF KNOWN] Goal: [IMPROVE RANKINGS/UPDATE INFO/EXPAND]

Analyze and improve:

Target audience: [WHO WILL SEE THIS] Goal: [CLICKS/OPENS/ENGAGEMENT] Platform: [BLOG/EMAIL/SOCIAL] Current headline (if any): [WHAT YOU HAVE NOW]

Create headlines using these frameworks:

For each headline:

• The headline text
• Which framework it uses
• Why it might work
• Where it would work best (email vs. social vs. SEO)

Content type: [BLOG/EBOOK/VIDEO/PODCAST] Target length: [WORD COUNT/DURATION] Target audience: [WHO WILL CONSUME THIS] Main keyword: [PRIMARY SEO TARGET] Unique angle: [YOUR PERSPECTIVE]

Outline structure:

Duration: [X MINUTES] Format: [SOLO/INTERVIEW/PRESENTATION] Audience: [WHO WILL WATCH/LISTEN] Style: [EDUCATIONAL/ENTERTAINING/PERSUASIVE] Platform: [WHERE IT WILL BE PUBLISHED]

Script structure:

HOOK (0:00-0:30) [Attention-grabbing opening - verbatim script]

INTRO (0:30-1:30) [Set up the topic and promise - verbatim script]

MAIN CONTENT Segment 1: [TOPIC] (1:30-X:XX) [Full script with timing markers]

Segment 2: [TOPIC] (X:XX-X:XX) [Full script]

[Continue for all segments]

CONCLUSION (X:XX-END) [Wrap up and CTA - verbatim script]

Include throughout:

• [PAUSE] markers
• [B-ROLL: description] suggestions
• [GRAPHIC: description] callouts
• [EMPHASIS] notes for delivery
• [TRANSITION] cues

Title: [WORKING TITLE] Keyword: [PRIMARY KEYWORD] Word count: [TARGET] Due date: [DEADLINE] Writer skill level: [JUNIOR/SENIOR]

Brief sections:

Creative Content

Company background:

• Founding date: [YEAR]
• Founder(s): [NAMES]
• Origin: [HOW IT STARTED]
• Mission: [WHY YOU EXIST]
• Current state: [WHERE YOU ARE NOW]

Product details:

• Name: [PRODUCT NAME]
• Category: [TYPE]
• Key features: [LIST FEATURES]
• Materials/specs: [TECHNICAL DETAILS]
• Price point: [RANGE]
• Target buyer: [WHO BUYS THIS]

Purpose: [BRAND AWARENESS/PRODUCT LAUNCH/CAMPAIGN] Target audience: [WHO WILL WATCH] Key message: [MAIN TAKEAWAY] Tone: [DESCRIBE THE FEELING] Call to action: [WHAT VIEWERS SHOULD DO]

Script format:

Scene 1: [DESCRIPTION] [TIMING: 0:00-0:XX] Visual: [What we see] Audio/VO: [What we hear] Text overlay: [Any text on screen]

Scene 2: [DESCRIPTION] [TIMING: X:XX-X:XX] Visual: [What we see] Audio/VO: [What we hear] Text overlay: [Any text on screen]

[Continue for all scenes]

Also provide:

• Music direction (mood, tempo, genre)
• Sound effects notes
• Transition recommendations
• End card specifications

Episode topic: [WHAT THIS EPISODE COVERS] Episode type: [SOLO/INTERVIEW/CO-HOSTED] Target length: [DURATION] Audience: [WHO LISTENS] Previous episodes context: [ANY RELEVANT CONTINUITY]

Episode structure:

Segment 1: [TOPIC] - Key points - Stories/examples - [X minutes]

Segment 2: [TOPIC] - Key points - Stories/examples - [X minutes]

[Continue for all segments]

---

Development Prompts (18 Examples)

Claude excels at code generation, explanation, and debugging. These prompts help developers work faster and produce better code.

Code Generation

Requirements:

• Input: [PARAMETERS AND TYPES]
• Output: [RETURN VALUE AND TYPE]
• Edge cases to handle: [LIST EDGE CASES]
• Performance considerations: [IF ANY]

• This will be used in: [WHERE/HOW IT WILL BE USED]
• Related code/patterns in the project: [ANY CONTEXT]
• Dependencies available: [LIBRARIES YOU USE]

Follow these conventions:

• [YOUR CODE STYLE PREFERENCES]
• [NAMING CONVENTIONS]
• [ERROR HANDLING APPROACH]

Endpoint: [METHOD] [ROUTE] Authentication: [AUTH METHOD] Request body: [EXPECTED PAYLOAD] Response format: [EXPECTED RESPONSE]

Framework: [EXPRESS/FASTAPI/DJANGO/ETC] Database: [YOUR DATABASE] ORM: [IF APPLICABLE]

Include:

Security considerations:

• Input sanitization
• Rate limiting notes
• Authorization checks

Use case: [WHAT THIS NEEDS TO STORE AND DO] Database type: [POSTGRESQL/MONGODB/MYSQL/ETC] Expected scale: [NUMBER OF RECORDS/USERS] Performance priorities: [READ-HEAVY/WRITE-HEAVY/BALANCED]

Requirements:

• Entities needed: [LIST MAIN ENTITIES]
• Key relationships: [HOW THEY CONNECT]
• Queries to support: [COMMON OPERATIONS]

Consider:

• Normalization vs. denormalization tradeoffs
• Future scalability
• Data integrity

Component name: [NAME] Props interface:

• [PROP1]: [TYPE] - [DESCRIPTION]
• [PROP2]: [TYPE] - [DESCRIPTION]

• [FEATURE 1]
• [FEATURE 2]
• [BEHAVIOR DESCRIPTIONS]

• [VISUAL DESCRIPTION]
• [RESPONSIVE BEHAVIOR]
• [ACCESSIBILITY REQUIREMENTS]

• State management: [REDUX/CONTEXT/ZUSTAND/NONE]
• Styling: [CSS MODULES/TAILWIND/STYLED-COMPONENTS]
• TypeScript: [YES/NO]
• Testing library: [JEST+RTL/CYPRESS/ETC]

Commands needed:

For each command specify:

• Arguments (required/optional)
• Flags/options
• Example usage

• Argument parsing library: [SPECIFIC OR SUGGEST]
• Config file support: [YES/NO]
• Output formatting: [JSON/TABLE/PLAIN]
• Error handling approach
• Exit codes

Code Review and Improvement

Context:

• This code does: [BRIEF DESCRIPTION]
• It will be used: [WHERE/HOW]
• Performance matters: [YES/NO - CONTEXT]
• This is for: [PRODUCTION/PROTOTYPE/LEARNING]

For each issue found:

• Severity: [CRITICAL/HIGH/MEDIUM/LOW]
• Location: [LINE NUMBER/SECTION]
• Problem: [WHAT IS WRONG]
• Solution: [HOW TO FIX]
• Code example: [FIXED VERSION]

Current issues:

• [ISSUE 1]
• [ISSUE 2]

• Must maintain: [WHAT CANNOT CHANGE]
• Breaking changes allowed: [YES/NO]
• Dependencies can add: [YES/NO]
• Target environment: [NODE VERSION/BROWSER SUPPORT/ETC]

Please provide:

Expected behavior: [WHAT SHOULD HAPPEN]

Actual behavior: [WHAT ACTUALLY HAPPENS]

What I have tried:

Environment:

• [LANGUAGE] version: [VERSION]
• OS: [OPERATING SYSTEM]
• Dependencies: [RELEVANT DEPENDENCIES]

Current performance:

• Execution time: [IF KNOWN]
• Memory usage: [IF KNOWN]
• Called [X] times per [TIMEFRAME]

• Must be at least [X]% faster
• Memory constraints: [IF ANY]
• Latency requirements: [IF ANY]

• Bottleneck identified: [WHERE IT IS SLOW]
• Data size typical: [SIZE OF INPUT]
• Can use caching: [YES/NO]
• Can add dependencies: [YES/NO]

Documentation

API context:

• Base URL: [BASE URL]
• Auth method: [AUTH TYPE]
• Rate limits: [IF ANY]
• Target developers: [WHO WILL USE THIS]

Documentation needs:

• [ ] Inline comments
• [ ] Function/method docstrings
• [ ] Module/file header
• [ ] README section
• [ ] Usage examples
• [ ] API reference

Documentation style: [JSDOC/SPHINX/RUSTDOC/ETC]

Please provide:

Project type: [LIBRARY/APP/TOOL/ETC] Language: [PRIMARY LANGUAGE] Purpose: [WHAT IT DOES]

Project details:

• Main features: [LIST KEY FEATURES]
• Installation method: [NPM/PIP/CARGO/ETC]
• Dependencies: [KEY DEPENDENCIES]
• Supported platforms: [WHERE IT RUNS]

Architecture and Planning

Requirements:

• Functional: [WHAT IT MUST DO]
• Non-functional: [PERFORMANCE/SCALE/SECURITY REQUIREMENTS]
• Scale: [EXPECTED USERS/REQUESTS/DATA VOLUME]
• Budget: [CONSTRAINTS ON INFRASTRUCTURE]

• Current tech stack: [WHAT WE USE]
• Integration needs: [EXTERNAL SYSTEMS]
• Team expertise: [WHAT WE KNOW]

Feature overview: [WHAT WE ARE BUILDING] Business context: [WHY WE ARE BUILDING IT] Success metrics: [HOW WE MEASURE SUCCESS]

Specification sections:

Current state:

• What exists: [CURRENT SETUP]
• Data size: [VOLUME]
• Usage patterns: [HOW IT IS USED]
• Downtime tolerance: [ACCEPTABLE DOWNTIME]

• Where we are going: [NEW SETUP]
• Why we are migrating: [REASONS]
• Success criteria: [HOW WE KNOW IT WORKED]

Context:

• Application type: [WEB APP/API/LIBRARY/ETC]
• Team size: [NUMBER OF DEVELOPERS]
• Age of codebase: [HOW OLD]
• Main pain points: [WHAT IS PROBLEMATIC]

Our use case: [WHAT WE NEED TO DO] Current stack: [WHAT WE USE NOW] Team: [SIZE AND EXPERIENCE LEVEL] Timeline: [PROJECT TIMELINE]

Evaluate against:

Known issues:

Please provide:

---

Business Prompts (15 Examples)

Claude can help with business analysis, strategy, and operational planning. These prompts cover common business scenarios.

Strategy and Planning

Business overview:

• What we sell: [PRODUCTS/SERVICES]
• Target customer: [WHO BUYS]
• Current revenue: [RANGE IF COMFORTABLE]
• Business model: [SUBSCRIPTION/ONE-TIME/FREEMIUM/ETC]

Conclude with:

• Strengths of current model
• Risks and weaknesses
• Opportunities for improvement

Context:

• Industry: [YOUR INDUSTRY]
• Stage: [STARTUP/GROWTH/MATURE]
• Main competitors: [KEY COMPETITORS]
• Recent changes: [ANY RECENT CONTEXT]

STRENGTHS (Internal, Positive)

• List 5-7 key strengths
• For each: What it is, why it matters, how to leverage it

• List 5-7 key weaknesses
• For each: What it is, impact, how to address it

• List 5-7 opportunities
• For each: What it is, potential impact, how to capture it

• List 5-7 threats
• For each: What it is, likelihood, how to mitigate

• S-O Strategies (use strengths to capture opportunities)
• W-O Strategies (improve weaknesses to capture opportunities)
• S-T Strategies (use strengths to mitigate threats)
• W-T Strategies (minimize weaknesses and avoid threats)

• Top 3 immediate priorities
• Top 3 long-term priorities

Product overview:

• What it is: [DESCRIPTION]
• Key features: [TOP FEATURES]
• Pricing: [PRICE POINT]
• Target customer: [WHO BUYS]
• Competitive advantage: [WHY US]

• Market size: [IF KNOWN]
• Competition: [MAIN COMPETITORS]
• Timing: [WHY NOW]

Operations

Process overview:

• Purpose: [WHY THIS PROCESS EXISTS]
• Frequency: [HOW OFTEN IT RUNS]
• Owner: [WHO IS RESPONSIBLE]
• Time required: [HOW LONG IT TAKES]

• [ROLE 1]: [THEIR PART]
• [ROLE 2]: [THEIR PART]

Current state:

• Process description: [HOW IT WORKS NOW]
• Steps involved: [STEP BY STEP]
• Time required: [DURATION]
• People involved: [WHO]
• Pain points: [WHAT IS WRONG]
• Metrics: [CURRENT PERFORMANCE]

• What should improve: [TARGETS]
• Constraints: [WHAT CANNOT CHANGE]

Financial

Business context:

• Stage: [STARTUP/GROWTH/MATURE]
• Revenue model: [HOW YOU MAKE MONEY]
• Industry: [YOUR INDUSTRY]
• Time horizon: [YEARS TO MODEL]

• Revenue: [CURRENT]
• Customers: [CURRENT]
• Pricing: [CURRENT]
• Costs: [MAJOR CATEGORIES]

For each assumption:

• The assumption value
• Rationale/justification
• Sensitivity range (optimistic/pessimistic)
• What would change it

Current situation:

• What we sell: [PRODUCT DESCRIPTION]
• Current pricing: [CURRENT PRICE/MODEL]
• Target customer: [WHO BUYS]
• Competition pricing: [COMPETITOR PRICES]
• Cost structure: [MARGIN INFO IF COMFORTABLE]

• Revenue target: [TARGET]
• Volume target: [TARGET]
• Positioning goal: [PREMIUM/MID/BUDGET]

For each model: - Pros and cons - Fit for our business - Implementation complexity

Communication

Context:

• What we are proposing: [PROJECT DESCRIPTION]
• Client background: [WHO THEY ARE]
• Their challenge: [PROBLEM WE SOLVE]
• Our solution: [HOW WE HELP]
• Budget range: [IF KNOWN]
• Timeline: [EXPECTED DURATION]

Full document covers: [SUMMARY OF FULL CONTENT]

Key points to emphasize:

Target reader: [WHO WILL READ THIS] Their priorities: [WHAT THEY CARE ABOUT]

Length: [WORD COUNT OR PAGE LENGTH]

The executive summary should:

Make it:

• Self-contained (readable without the full document)
• Scannable (clear structure, bullet points where appropriate)
• Action-oriented (what decisions need to be made)
• Free of jargon (unless reader expects it)

Meeting details:

• Duration: [TIME]
• Attendees: [WHO IS INVITED]
• Goal: [WHAT WE NEED TO ACCOMPLISH]
• Pre-work: [ANY PREP NEEDED]

Agenda structure:

Total should fit within [TIME]. Include recommended time allocation that adds up correctly.

Also provide:

• Meeting notes template
• Follow-up email template

Analysis

Research purpose: [WHY WE NEED THIS] Decision it will inform: [WHAT WE WILL DO WITH IT] Budget: [IF RELEVANT] Timeline: [WHEN WE NEED IT]

Research questions:

Develop a research brief covering:

Our product: [DESCRIPTION] Our positioning: [HOW WE POSITION] Key competitors:

Create:

Context:

• What is the decision: [DESCRIPTION]
• Why it matters: [STAKES]
• Timeline: [WHEN DECISION NEEDED]
• Key stakeholders: [WHO CARES]

Criteria that matter:

• [CRITERION 1]: [IMPORTANCE 1-5]
• [CRITERION 2]: [IMPORTANCE 1-5]
• [CRITERION 3]: [IMPORTANCE 1-5]

Project overview: [WHAT THIS IS] Goal: [WHAT WE ARE TRYING TO DO]

Known stakeholders:

Analyze each stakeholder:

The change: [WHAT IS CHANGING] Why it is happening: [DRIVERS] Who it affects: [IMPACTED GROUPS] Timeline: [WHEN] Scale: [HOW BIG]

Create a change management plan:

---

Research Prompts (10 Examples)

Claude's large context window and reasoning abilities make it excellent for research tasks.

Research question: [SPECIFIC QUESTION] Scope: [WHAT TO INCLUDE/EXCLUDE] Depth needed: [COMPREHENSIVE/FOCUSED] Purpose: [ACADEMIC/PROFESSIONAL/PERSONAL]

Structure the review:

Note: I understand you cannot access external databases. Please:

• Identify what I should search for
• Suggest key authors/papers to find
• Provide framework for analysis
• Offer guidance on evaluation criteria

[PASTE CONTENT OR DESCRIBE WHAT TO SUMMARIZE]

Context:

• My background: [EXPERT/NOVICE IN FIELD]
• Purpose: [WHY I NEED THIS SUMMARY]
• Focus: [SPECIFIC ASPECTS TO EMPHASIZE]

My current understanding: [WHAT I KNOW] What I am trying to learn: [LEARNING GOALS] Time I have: [DEPTH APPROPRIATE] My background: [RELEVANT CONTEXT]

Provide an exploration covering:

[PASTE DATA OR DESCRIBE THE DATASET]

Context:

• What this data represents: [DESCRIPTION]
• How it was collected: [METHODOLOGY]
• What I want to understand: [QUESTIONS]

Context:

• What these are: [DESCRIPTION]
• Why I am comparing: [PURPOSE]
• Decision I need to make: [IF APPLICABLE]

Timeframe: [HISTORICAL PERIOD TO ANALYZE] Focus: [SPECIFIC ASPECTS] Purpose: [WHY I NEED THIS ANALYSIS]

Provide:

[PASTE THE ARGUMENT OR DESCRIBE IT]

Please provide:

My current understanding: [WHAT I KNOW] My background: [RELEVANT EXPERTISE] Why I need to understand this: [CONTEXT] Depth needed: [OVERVIEW/DETAILED/EXPERT]

Please explain:

[PASTE SOURCE OR DESCRIBE IT]

Source details:

• Type: [ARTICLE/BOOK/WEBSITE/STUDY]
• Author: [WHO CREATED IT]
• Publication: [WHERE PUBLISHED]
• Date: [WHEN]
• Purpose: [WHY I AM EVALUATING]

General topic: [BROAD AREA OF INTEREST] Initial question: [MY CURRENT QUESTION] Purpose: [WHY I AM RESEARCHING] Constraints: [TIME/RESOURCES/SCOPE]

Please help me:

---

Productivity Prompts (10 Examples)

These prompts help you work more efficiently and manage your time and tasks better.

Project: [PROJECT NAME] Goal: [WHAT SUCCESS LOOKS LIKE] Deadline: [WHEN IT NEEDS TO BE DONE] Resources: [WHAT I HAVE AVAILABLE] Constraints: [LIMITATIONS]

Please provide:

[PASTE MEETING NOTES OR TRANSCRIPT]

Meeting context:

• Meeting type: [STATUS/BRAINSTORM/DECISION/ETC]
• Attendees: [WHO WAS THERE]
• Purpose: [WHAT THE MEETING WAS FOR]

This week's priorities:

Commitments:

• [MEETING/COMMITMENT 1]: [DAY/TIME]
• [MEETING/COMMITMENT 2]: [DAY/TIME]

• [TASK 1]
• [TASK 2]
• [ADD MORE]

• Working hours: [YOUR SCHEDULE]
• Energy patterns: [WHEN YOU ARE MOST PRODUCTIVE]
• Must happen: [NON-NEGOTIABLES]

Context:

• To: [RECIPIENT AND RELATIONSHIP]
• Purpose: [WHAT I NEED]
• Situation: [BACKGROUND]
• Tone needed: [FORMAL/CASUAL/URGENT/ETC]
• Desired outcome: [WHAT I WANT THEM TO DO]

Constraints:

• Length: [SHORT/MEDIUM/DETAILED]
• Deadline: [IF RELEVANT]
• Sensitive aspects: [IF ANY]

Also provide:

• Alternative version (different approach)
• Shorter version (if original is long)
• Key phrases I could customize

Decision: [WHAT WAS DECIDED] Date: [WHEN] Decision maker(s): [WHO] Context: [WHY THIS DECISION WAS NEEDED]

Options considered:

Create a decision record:

Audience: [WHO WILL READ THIS] Frequency: [DAILY/WEEKLY/MONTHLY] Format preference: [EMAIL/SLACK/DOC]

Information to include:

• Progress since last update: [WHAT HAPPENED]
• Current status: [WHERE THINGS STAND]
• Blockers: [IF ANY]
• Next steps: [WHAT IS COMING]
• Metrics: [KEY NUMBERS]

Process name: [WHAT YOU ARE DOCUMENTING] What it accomplishes: [OUTCOME] How often I do it: [FREQUENCY] Time it takes: [DURATION]

Current steps (rough):

Tools used: [SOFTWARE/TOOLS] Dependencies: [WHAT NEEDS TO BE IN PLACE]

Create documentation that includes:

What I need feedback on: [DESCRIBE] From whom: [WHO I AM ASKING] Deadline: [WHEN I NEED IT] Relationship: [COLLEAGUE/BOSS/CLIENT/ETC]

Specific areas I want feedback on:

Context they need:

• [BACKGROUND INFO]
• [GOALS]
• [CONSTRAINTS]

Context:

• Role/situation: [YOUR CONTEXT]
• What matters most: [PRIORITIES]
• Resources available: [TIME/MONEY/SUPPORT]
• Constraints: [LIMITATIONS]

For each area, help me develop:

My goal: [WHAT I WANT TO BE ABLE TO DO] Current level: [BEGINNER/INTERMEDIATE/ADVANCED] Time available: [HOURS PER WEEK] Timeline: [WHEN I WANT TO ACHIEVE THIS] Learning style: [HOW I LEARN BEST] Budget: [FOR RESOURCES]

Please create:

---

How Ralphable Makes These Prompts Even Better

The prompts above are powerful starting points. But imagine if they could:

• Iterate automatically until the output meets your standards
• Verify their own work against success criteria you define
• Handle edge cases with built-in fallback logic
• Improve over time as you refine and share them

From Static Prompts to Self-Improving Skills

Each prompt in this guide is a one-shot template. You submit it, get a response, and manually evaluate whether it meets your needs. If it does not, you tweak and try again.

Ralph Skills take a different approach. When you generate a skill in Ralphable, it includes:

Instead of hoping the output is good, skills define what "good" looks like:

• [ ] All required sections included
• [ ] Word count between 2000-3000
• [ ] No generic placeholder language
• [ ] Specific examples for every point

The AI evaluates its own output against these criteria before presenting it to you.

If the first attempt does not meet all criteria, the skill guides Claude to:

This eliminates the frustrating cycle of manual prompt adjustments.

Skills include instructions for handling edge cases:

• Ask for clarification on [specific points]
• Provide examples of what good input looks like
• Proceed with assumptions and note them clearly

Complex tasks are broken into atomic steps, each with its own verification:

• Goal: Gather necessary information
• Criteria: [checkboxes]
• Max attempts: 2

• Goal: Create initial version
• Criteria: [checkboxes]
• Max attempts: 3

• Goal: Polish to final version
• Criteria: [checkboxes]
• Max attempts: 2