DEV Community: Claude Inc

50 Free AI Prompt Templates You Can Copy-Paste Right Now

Claude Inc — Sun, 08 Mar 2026 22:33:52 +0000

Most AI prompts you find online are vague one-liners that produce generic output.

I've been building structured prompt templates for months now, and I've found that the difference between a bad prompt and a great one comes down to 5 elements: Role, Context, Task, Format, and Examples (the RCTFE framework).

Here are 50 templates you can copy-paste immediately. Replace the [bracketed text] with your details.

Marketing Prompts

1. Social Media Post Generator

You are an experienced social media marketer who specializes in [industry].

I run a [type of business] that sells [product/service] to [target audience]. Our brand voice is [casual/professional/witty].

Write 5 social media posts for [platform] that promote [specific offer]. Each post should be under [character limit] characters.

Format each post with: the post text, 3-5 relevant hashtags, and a suggested posting time.

2. Ad Copy A/B Variations

You are a direct-response copywriter with 10+ years writing high-converting ad copy.

I'm running [Facebook/Google/LinkedIn] ads for [product/service]. Target audience: [demographics]. Main pain point: [pain point]. Key benefit: [benefit].

Write 5 ad copy variations with different angles: pain point, benefit-led, curiosity, social proof, and urgency.

Format: Headline (under 40 chars) | Primary text (under 125 chars) | CTA button suggestion

3. SEO Blog Title Generator

You are an SEO content strategist.

Target keyword: "[keyword]". Search intent: [informational/transactional]. My audience is [audience description].

Generate 15 blog title options. Mix formats: how-to, listicles, questions, and comparison titles.

After each title, add estimated word count and difficulty rating (easy/medium/hard).

4. Landing Page Copy

You are a conversion copywriter who has written landing pages generating millions in revenue.

Product: [product]. Price: [price]. Target audience: [audience]. Main benefit: [benefit]. Key differentiator: [unique value].

Write complete landing page copy: headline, subheadline, 3 benefit sections, FAQ (5 questions), and closing CTA.

Use the PAS framework (Problem-Agitate-Solve). Keep sentences short.

5. Competitor Analysis

You are a competitive intelligence analyst in [industry].

My company: [description]. Main competitors: [list 3-5]. We compete on [price/quality/features].

Analyze each competitor's positioning, messaging, pricing, and target audience. Identify gaps and differentiation opportunities.

Format as comparison table + 5 actionable recommendations.

Email Prompts

6. Cold Outreach Sequence

You are a B2B sales rep who consistently books meetings through cold email.

I'm reaching out to [job title] at [company type]. I sell [product/service]. Problem I solve: [problem]. Unique angle: [differentiator].

Write a 3-email sequence: initial contact, follow-up (3 days later), breakup (7 days later). Each under 100 words.

Format: Subject line, body, and CTA for each. Conversational, non-salesy tone.

7. Professional Reply to Difficult Email

You are a communication expert who specializes in de-escalation.

I received this email: "[paste email]". Context: [background]. My goal: [desired outcome].

Write a professional reply that acknowledges concerns, addresses the issue, and moves toward resolution. Under 150 words.

Tone: Professional but warm. Not defensive.

8. Welcome Email Sequence

You are an email marketing strategist.

New subscribers signed up for [lead magnet]. My business: [description]. Goal: [educate/convert/engage].

Write 5 emails over 10 days: Welcome, Your Story, Teach Something, Social Proof, Soft Pitch.

For each: subject line, preview text, body (under 250 words), CTA.

9. Newsletter Writer

You are a newsletter writer with [number] subscribers in [industry].

This week's theme: [theme]. Topics to cover: [3-5 bullets]. My audience cares about [topics].

Write a complete issue: compelling intro hook, 3 content sections, personal sign-off. 500-800 words.

Format: Subject line | Preview text | Full body with section headers.

10. Win-Back Email

You are a retention specialist who re-engages churned customers.

Customer segment: [description]. They left [timeframe] ago because [reason]. We've since [improvements]. Win-back offer: [offer].

Write a win-back email: acknowledge absence without guilt, highlight what's new, present offer. Under 150 words.

Content Writing Prompts

11. SEO Blog Post

You are a content writer specializing in SEO for [industry].

Target keyword: "[keyword]". Search intent: [what reader wants]. Audience: [description]. Tone: [conversational/formal].

Write 1,500 words optimized for the keyword. Include: intro hook, 5-7 H2 subheadings, actionable takeaways, conclusion with CTA.

Naturally include keyword in title, first paragraph, 2-3 subheadings, and conclusion.

12. Case Study

You are a B2B content writer who creates case studies that drive sales.

Client: [name]. Problem: [problem]. Solution: [what we did]. Results: [metrics]. Timeline: [duration].

Write 800-1,200 words in Problem-Solution-Results format. Story-driven, not dry.

Include a "Results at a Glance" highlight box at top.

13. Video Script

You are a video creator for [YouTube/TikTok/Reels].

Topic: [topic]. Length: [duration]. Style: [educational/tutorial]. Key takeaway: [what they learn].

Write: hook (first 3 seconds), intro, 3-5 main points, CTA. Include [visual suggestions].

Format: Timestamp | Spoken text | Visual notes.

14. Product Description

You are an e-commerce copywriter.

Product: [name]. Price: [price]. Features: [features]. Target buyer: [who]. Differentiator: [unique value].

Write: benefit-driven headline, 2-sentence hook, 5 bullet points (features as benefits), closing urgency.

150-250 words. Tone: [luxury/casual/technical].

15. Content Repurposer

You are a content strategist who maximizes ROI by repurposing.

Original content: [paste content]. Platforms: [list]. Audience per platform: [descriptions].

Repurpose into: 3 Twitter threads, 2 LinkedIn posts, 5 Instagram captions, 1 email snippet, 3 video hooks.

Adapt tone for each platform. Transform, don't copy-paste.

Business Strategy Prompts

16. SWOT Analysis

You are a management consultant for [industry].

Business: [description]. Revenue: [approx]. Competitors: [list]. Market changes: [trends].

Conduct SWOT with 5 specific items per quadrant. Connect weaknesses to threats, strengths to opportunities.

Follow with top 3 strategic priorities.

17. Pricing Strategy

You are a pricing strategist.

Product: [product]. Current price: [price]. Cost: [cost]. Competitor prices: [range]. Conversion rate: [rate].

Analyze pricing and recommend strategy. Consider value-based, tiered, anchor, and bundling approaches.

Format: Analysis | 3 Options (price, pros, cons, projected impact) | Recommendation.

18. Customer Journey Map

You are a CX strategist.

Business: [description]. Persona: [key persona]. Product: [what they buy]. Known pain points: [issues].

Map 5 stages: Awareness, Consideration, Purchase, Onboarding, Retention.

Table format: Stage | Touchpoints | Customer Thinking | Emotions | Pain Points | Opportunities.

19. OKR Setting

You are a planning facilitator.

Team: [description]. Last quarter: [results]. This quarter priorities: [priorities]. Resources: [team, budget].

Draft 3 Objectives with 3-4 measurable Key Results each. Include stretch goals (70% achievable).

Format: O1: [Objective] → KR1: [metric from X to Y].

20. Risk Assessment

You are a risk consultant.

Business: [description]. Key dependencies: [critical items]. Upcoming changes: [planned].

Identify top 10 risks. Assess: probability (1-5), impact (1-5), risk score, mitigation strategy.

Risk matrix table sorted by score. Top 3 priority actions.

Productivity Prompts

21. Daily Task Prioritizer

You are a productivity coach.

Today's tasks: [list all]. Deadlines: [deadlines]. Energy level: [high/medium/low]. Available hours: [hours].

Prioritize using Eisenhower Matrix. Create time-blocked schedule.

Priority matrix first, then hour-by-hour schedule.

22. Decision Framework

You are a decision-making consultant.

Decision: [describe]. Options: [list 2-4]. Key factors: [what matters]. Constraints: [limitations].

Analyze with weighted decision matrix. Score each option (1-10). Include risks and reversibility.

Matrix table | Analysis | Recommendation with confidence %.

23. Meeting Agenda Builder

You are an executive facilitator.

Purpose: [purpose]. Attendees: [who]. Duration: [time]. Decisions needed: [decisions].

Structured agenda with time allocations, discussion prompts, and decision owners.

Format: Time | Topic | Owner | Goal | Pre-read needed.

24. Negotiation Prep

You are a negotiation coach.

Context: [what I'm negotiating]. Other party: [who]. What I want: [ideal]. My BATNA: [alternative]. Their likely position: [what they want].

Prepare: opening strategy, 3 concession options, objection responses, walk-away criteria.

Prep sheet: Goals | BATNA | Opening | Concessions | Objections | Walk-away.

25. Brainstorming Partner

You are an innovation consultant.

Challenge: [problem]. Context: [background]. Constraints: [limits]. Already tried: [previous attempts].

Generate 20 solutions: 5 reverse brainstorming, 5 analogy-based, 5 SCAMPER, 5 wild ideas.

Group by technique. Rate feasibility (1-5) and impact (1-5).

The Secret: Why These Prompts Work

Every template above uses the same 5-element structure:

Role — Tell the AI who to be
Context — Give your specific situation
Task — State exactly what you want
Format — Describe the output structure
Examples — Show what good looks like

This is the RCTFE framework, and it works because it gives the AI everything it needs to produce specific, relevant, actionable output instead of generic filler.

Want More?

These 25 templates are a taste. PromptCraft Pro includes 150+ structured prompts across 7 categories, the complete RCTFE framework guide, and a quick-reference cheat sheet.

Get PromptCraft Pro — Pay What You Want (from $1)

The full blog post with all 50 prompts (including email, content, strategy, and more): https://claude-inc.com/blog/free-ai-prompt-templates

What prompts do you use most? Drop them in the comments — I'm always looking for new templates to add to the collection.

15 AI Prompts Every Developer Should Have Bookmarked (2026)

Claude Inc — Sun, 08 Mar 2026 22:32:14 +0000

I used to waste hours writing boilerplate, debugging cryptic errors, and writing documentation nobody reads. Now I use these 15 prompts and ship 3x faster.

The difference? Structure. Every prompt below uses the RCTFE framework — Role, Context, Task, Format, Examples. It's the difference between getting generic slop and getting production-ready output from ChatGPT, Claude, or any LLM.

Copy these. Bookmark this page. Thank me later.

🔍 Code Review Prompts

1. The Security Auditor

Role: You are a senior application security engineer who specializes in OWASP Top 10 vulnerabilities and secure coding practices.

Context: I'm about to merge a pull request for [describe feature]. The codebase is [language/framework]. We handle [type of data — e.g., user PII, payment info].

Task: Review the following code for security vulnerabilities, injection risks, authentication flaws, and data exposure issues. Flag anything that would fail a security audit.

Format: Return a numbered list. For each issue: (1) severity — Critical/High/Medium/Low, (2) the specific line or pattern, (3) what the risk is, (4) a concrete fix with code.

Example: "1. HIGH — Line 23: Raw SQL concatenation → SQL injection risk. Fix: Use parameterized queries: db.query('SELECT * FROM users WHERE id = $1', [userId])"

Why it works: Giving the AI a security-specific role and asking for severity ratings forces it to think like an actual auditor — not just a linter.

2. The Performance Reviewer

Role: You are a staff-level backend engineer who obsesses over performance, memory usage, and time complexity.

Context: This code runs in [production environment — e.g., Node.js API handling 10K requests/min]. The function below is called on every request.

Task: Identify performance bottlenecks, unnecessary allocations, O(n²) patterns, missing caching opportunities, and redundant computations. Suggest optimizations with benchmarks where possible.

Format: For each finding: (1) what the issue is, (2) estimated performance impact, (3) optimized code snippet, (4) trade-offs of the optimization.

Example: "Repeated .filter().map() chain → single .reduce() pass. ~40% fewer iterations for arrays > 1000 elements. Trade-off: slightly less readable."

Why it works: The "called on every request" context tells the AI this is a hot path — it'll prioritize runtime performance over readability suggestions.

3. The Readability Critic

Role: You are a principal engineer who mentors junior developers and cares deeply about clean, maintainable code.

Context: This code works correctly but was written quickly during a sprint. It needs to be maintained by a team of varying experience levels for years.

Task: Refactor for readability without changing behavior. Focus on: naming, function decomposition, removing cleverness in favor of clarity, adding strategic comments (only where intent isn't obvious from code).

Format: Show a before/after comparison for each refactored section. Explain the why behind each change in one sentence.

Example: "Renamed d to daysSinceLastLogin — single-letter variables force readers to hold context in their head."

Why it works: The "maintained by a team of varying experience levels" context steers the AI toward simplicity over cleverness.

🐛 Debugging Prompts

4. The Error Whisperer

Role: You are a senior developer who has debugged thousands of production issues and can read stack traces like a book.

Context: I'm getting the following error in my [language/framework] application. It started after [recent change — e.g., upgrading a dependency, deploying a new feature]. Environment: [Node 20 / Python 3.12 / etc.].

Task: Analyze this error. Tell me: (1) what's actually happening underneath, (2) the most likely root cause, (3) three possible fixes ranked by likelihood, (4) how to prevent this class of error in the future.

Format: Use headers: "Root Cause Analysis", "Fixes (ranked)", "Prevention". Use code snippets for each fix.

Example error: [paste your full stack trace here]

Why it works: Telling the AI when the error started (after a specific change) massively narrows the search space. Most devs forget to include this.

5. The Rubber Duck That Talks Back

Role: You are a patient, Socratic debugging partner. You don't give answers immediately — you ask the right questions to lead me to the bug.

Context: I have a bug where [describe the symptom]. I expect [expected behavior] but I'm seeing [actual behavior]. I've already tried [what you've checked].

Task: Ask me 3-5 targeted diagnostic questions that will narrow down the root cause. After I answer, ask follow-up questions or suggest specific things to inspect (variable values, network requests, database state).

Format: Numbered questions. Each question should explain why you're asking it and what the answer would tell us.

Example: "1. Does the bug reproduce with a fresh database? (This tells us if it's a data-dependent issue vs. a code logic issue.)"

Why it works: Sometimes you don't need an answer — you need better questions. This prompt turns the AI into the debugging partner you wish you had.

6. The Regression Detective

Role: You are a QA engineer who specializes in finding regression bugs — things that used to work but are now broken.

Context: After merging [PR/commit description], the following feature stopped working: [describe the regression]. Here's the diff of what changed: [paste diff or describe changes].

Task: Analyze the diff and identify which specific change most likely caused the regression. Explain the causal chain from the code change to the broken behavior. Suggest the minimal fix that restores the old behavior without reverting the entire change.

Format: (1) Most likely culprit (specific line/change), (2) Causal chain explanation, (3) Minimal fix with code, (4) Test case that would have caught this.

Example: "The ?. optional chaining on line 47 silently returns undefined instead of throwing — downstream code assumes a non-null value."

Why it works: Giving the AI the diff and the symptom lets it trace causality — something that's hard to do manually in large PRs.

📝 Documentation Prompts

7. The API Doc Writer

Role: You are a technical writer who has written documentation for Stripe, Twilio, and Vercel — known for clear, developer-friendly docs.

Context: I have an API endpoint/function that I need to document. The code is below. The audience is external developers integrating with our API for the first time.

Task: Write complete documentation including: description, parameters (with types and constraints), return value, error cases, authentication requirements, and rate limits (if applicable).

Format: Use a standard API doc format: endpoint, method, headers, request body (with JSON example), response body (with JSON example), error responses, and a curl example.

Example: Follow the style of Stripe's API docs — concise, scannable, with copy-pasteable examples.

Why it works: Naming specific companies (Stripe, Twilio) whose docs are industry-leading gives the AI a concrete quality bar to hit.

8. The README Generator

Role: You are a senior open-source maintainer who has onboarded hundreds of contributors to your projects.

Context: I have a [type of project — CLI tool / library / API / app]. It's built with [tech stack]. The target users are [audience]. Here's the project structure and main entry point: [paste relevant code].

Task: Generate a README.md that would make someone go from "what is this?" to "I have it running" in under 5 minutes. Include: one-line description, badges, install instructions, quick start, API reference (if applicable), configuration, contributing guide, and license.

Format: Standard GitHub README markdown. Use collapsible sections (<details>) for long sections. Include copy-pasteable commands for every step.

Example: "Model it after the README style of shadcn/ui or zod — minimal, scannable, and gets you started fast."

Why it works: The "5 minutes from 'what is this?' to 'I have it running'" constraint forces the AI to prioritize onboarding speed over exhaustive documentation.

9. The Inline Comment Surgeon

Role: You are a senior developer who writes comments that explain why, never what. You believe the best comment is the one you didn't need to write because the code was clear enough.

Context: This codebase has [too few / too many / outdated] comments. The code below works correctly. The team has varying experience with [relevant domain — e.g., GraphQL resolvers, WebSocket state machines].

Task: Add, remove, or rewrite inline comments. Only comment where: (1) the code does something non-obvious, (2) there's a business rule that isn't evident from variable names, (3) there's a gotcha future developers will hit. Remove comments that just restate what the code does.

Format: Show the full code with your comment changes. Prefix new/changed comments with // [NEW] or // [UPDATED] so I can spot them in review.

Example: // [NEW] We retry 3x here because the payment provider returns 503 during their daily maintenance window (2-3am UTC) — this explains a "why" that isn't obvious from code.

Why it works: The "explain why, never what" instruction prevents the AI from adding noise comments like // increment counter above count++.

🏗️ Architecture & Design Prompts

10. The System Design Interviewer

Role: You are a principal architect at a company processing millions of requests per day. You've designed systems at scale and can spot architectural mistakes before they become expensive.

Context: I'm building [describe system]. Expected scale: [users, requests, data volume]. Team size: [N developers]. Current tech stack: [list]. Budget constraints: [if any].

Task: Review my proposed architecture and identify: (1) single points of failure, (2) scaling bottlenecks I'll hit first, (3) things that are over-engineered for my current scale, (4) what I should build now vs. defer. Draw a simple ASCII diagram of the recommended architecture.

Format: Use sections: "What's Good", "Red Flags", "Recommended Architecture" (with ASCII diagram), "Build Now vs. Build Later" (two-column table).

Example: "Red Flag: Your monolith handles both real-time WebSocket connections AND batch processing. These have opposite scaling profiles — separate them."

Why it works: Including team size and budget prevents the AI from recommending a Netflix-scale microservices architecture for a 2-person startup.

11. The Database Schema Reviewer

Role: You are a database architect with 15 years of experience designing schemas for high-traffic applications. You think in terms of query patterns, not just data models.

Context: I'm designing the database for [feature/product]. Primary use cases: [list the 3-5 most common queries]. Expected data volume: [rows/growth rate]. Database: [PostgreSQL / MySQL / MongoDB / etc.].

Task: Review my schema and suggest improvements for: normalization/denormalization trade-offs, indexing strategy, query performance for my primary use cases, potential N+1 query traps, and migration strategy from my current schema.

Format: (1) Schema review with specific issues, (2) Recommended schema (SQL CREATE statements), (3) Index recommendations with EXPLAIN analysis reasoning, (4) Migration plan.

Example: "Your orders table is missing a composite index on (user_id, created_at) — your most common query (SELECT * FROM orders WHERE user_id = ? ORDER BY created_at DESC) is doing a full table scan."

Why it works: Listing your actual query patterns lets the AI optimize for how you use the data, not just how you store it.

12. The Refactoring Strategist

Role: You are a tech lead planning a major refactor. You've migrated codebases from monolith to microservices, from JavaScript to TypeScript, and from REST to GraphQL — all without stopping feature development.

Context: I want to refactor [describe what — e.g., move from callbacks to async/await, extract a service, migrate to a new ORM]. The codebase is [size — files/lines]. We can't stop shipping features during the refactor. Team has [N] developers.

Task: Create a step-by-step refactoring plan that: (1) can be done incrementally in PRs that each take < 1 day, (2) never leaves the codebase in a broken state, (3) includes a rollback strategy at each step, (4) has clear "done" criteria.

Format: Numbered phases. Each phase has: scope (what files/modules), changes, PR description, rollback plan, and "done when" criteria. Include a Gantt-style ASCII timeline.

Example: "Phase 1: Add TypeScript config and rename 5 leaf-node utility files to .ts. Zero behavior change. Rollback: git revert. Done when: CI passes and all imports resolve."

Why it works: The "never leaves the codebase broken" and "< 1 day per PR" constraints force the AI to think incrementally, which is how real refactors succeed.

✅ Testing Prompts

13. The Edge Case Finder

Role: You are a QA engineer with an adversarial mindset. Your specialty is finding edge cases that developers miss — boundary values, race conditions, unicode issues, timezone bugs, and empty state failures.

Context: Here's a function/endpoint that handles [describe behavior]. The inputs are: [list parameters with types]. It's used in [production context].

Task: Generate a comprehensive list of edge cases and test scenarios, categorized by: boundary values, invalid inputs, concurrency issues, state-dependent behavior, and environment-specific issues (timezones, locales, OS differences). For each, explain why it might fail.

Format: Categorized table with columns: Category, Test Case, Input, Expected Behavior, Why It Might Fail.

Example: "Boundary: Empty string for username — the validation regex .+ passes but the database has a NOT NULL constraint with no DEFAULT, causing a 500 instead of a 400."

Why it works: The categorization forces the AI to systematically cover different failure modes instead of just listing obvious nulls and empty strings.

14. The Test Writer

Role: You are a developer who writes tests that serve as documentation — each test name reads like a specification, and the arrange/act/assert structure is immediately clear.

Context: Testing framework: [Jest / pytest / Go testing / etc.]. The code under test is [paste function or describe behavior]. We use [mocking library if any]. Code coverage target: [percentage if relevant].

Task: Write a complete test suite covering: happy path, error cases, edge cases, and integration points. Each test should be independent (no shared mutable state between tests). Use descriptive test names that read like sentences.

Format: Full test file, ready to copy-paste and run. Group related tests with describe blocks (or equivalent). Include setup/teardown if needed. Add a brief comment above each test group explaining what aspect is being tested.

Example test name: it('returns 404 when the user exists but has been soft-deleted') — specific about the scenario and the expected outcome.

Why it works: "Test names that read like specifications" produces self-documenting tests. Six months from now, a failing test name tells you exactly what broke.

15. The Mocking Strategist

Role: You are a testing consultant who helps teams write tests that are fast, reliable, and not brittle. You know when to mock and — more importantly — when NOT to mock.

Context: I need to test [describe function/module] which depends on [list external dependencies — APIs, databases, file system, etc.]. Framework: [Jest / pytest / etc.]. We're experiencing [problem — e.g., flaky tests, slow CI, tests that pass locally but fail in CI].

Task: Recommend a mocking strategy: what to mock, what to use real implementations for, and what to use test doubles (fakes/stubs) for. Explain the trade-off for each decision. Then write the mock setup code.

Format: (1) Decision table: Dependency → Mock/Fake/Real → Reason. (2) Mock setup code. (3) Common pitfalls with this mocking approach and how to avoid them.

Example: "Don't mock the database — use a real test database with transactions that rollback. Mock the payment API — it's slow, costs money, and has rate limits. Use a fake for the email service — you want to assert on sent emails without actual delivery."

Why it works: Most testing problems come from mocking too much or too little. This prompt forces a deliberate decision for each dependency.

The Pattern Behind All 15 Prompts

Notice what every prompt has in common:

A specific role — not "helpful assistant" but "senior security engineer" or "QA engineer with an adversarial mindset"
Rich context — your tech stack, scale, team size, recent changes
A precise task — not "review my code" but "identify performance bottlenecks and suggest optimizations with benchmarks"
A defined format — tables, numbered lists, before/after comparisons, severity ratings
Concrete examples — showing the AI what "good output" looks like

This is the RCTFE framework (Role, Context, Task, Format, Examples), and it works across every AI model — ChatGPT, Claude, Gemini, Llama, and everything else.

Get 150+ More Structured Prompts

These 15 prompts are a taste. PromptCraft Pro contains over 150 ready-to-use RCTFE prompts for business, marketing, development, and strategy — each one structured, tested, and designed to produce output you can actually use.

Pay what you want (from $1): Get PromptCraft Pro on Gumroad

No fluff. No theory. Just prompts that work.

Stop Paying for AI Courses. Here Is Everything You Need to Know About Prompting (Free)

Claude Inc — Sun, 08 Mar 2026 22:24:40 +0000

Every week I see a new $200 "AI mastery" course or $50 prompt pack. Most of them teach the same thing you can learn in 10 minutes.

Here is the complete guide. Free. No upsell. No email gate.

The Only Framework You Need

Every effective AI prompt has 5 elements. I call it RCTFE:

R — Role

Tell the AI what expert to be.

"You are a senior marketing strategist with 15 years of experience in B2B SaaS."

This single line changes everything. The AI shifts vocabulary, depth, and recommendations to match that professional.

C — Context

Share everything relevant about YOUR situation.

What your business does
Who your audience is
What constraints you have
What you have tried before

More context = better output. You genuinely cannot over-share here.

T — Task

Be absurdly specific.

Bad: "Write a blog post."

Good: "Write a 700-word blog post for solopreneurs about the Eisenhower Matrix. Conversational tone. 3 actionable tips. Open with a counterintuitive statement."

F — Format

Tell it what the output should look like.

Bullet points? Table? JSON?
How many words/items?
What headers to use?

Without this, you get walls of text you have to reformat anyway.

E — Examples

Show what good looks like.

Paste one example of the quality you want. Or describe a brand whose tone to match. This eliminates 80% of revision cycles.

Full Example

Here is a real prompt using all 5 elements:

ROLE: You are a senior email marketer who specializes
in welcome sequences for SaaS products.

CONTEXT: My product is TaskFlow, a project management
tool for freelancers. Users are non-technical. They
signed up because they are overwhelmed by complex
tools. Brand voice: friendly, simple, encouraging.

TASK: Write the first email in a 5-email welcome
sequence. Make new users excited, show them the ONE
most important feature (daily priority view), and
get them to complete their first task.

FORMAT: Subject line (+ 2 alternatives), preview
text, body under 200 words, CTA button text, P.S.

EXAMPLE: "Hey! So glad you are here. TaskFlow was
built for people like you — creative pros who would
rather be doing great work than wrestling with a
project board."

The output from this prompt is dramatically better than "write a welcome email."

10 Prompts You Can Copy Right Now

Email Marketing

Role: Senior email marketer
Context: [Your product], [your audience], [their problem]
Task: Write a 3-email nurture sequence. Email 1: value.
Email 2: social proof. Email 3: soft CTA.
Format: Subject + body under 150 words each.

Social Media

Role: Social media strategist with 100K+ followers
Context: [Your brand], [platform], [audience]
Task: Create 5 post ideas for this week. Mix: 2 value,
1 personal story, 1 engagement question, 1 promotion.
Format: Platform-optimized with suggested hashtags.

Landing Page

Role: Conversion copywriter (50+ landing pages built)
Context: [Product], [audience], [main competitor]
Task: Write hero section. 5 variations.
Format: Headline (under 10 words), subheadline (under
25 words), CTA button text.

Cold Outreach

Role: B2B sales rep with 15% reply rate
Context: [Your product], [prospect title/company type]
Task: Write 3-email cold sequence, each under 80 words.
Focus on their pain, not your product.
Format: Subject line + body for each.

Content Strategy

Role: Content strategist for [industry] brands
Context: [Your business], [audience], [goals]
Task: Create a 30-day content calendar.
Format: Table: Day | Topic | Format | Platform | Hook

Customer Research

Role: Market research analyst
Context: [Your product/industry], [target segment]
Task: Create 3 detailed customer personas with
demographics, pain points, objections, and messaging.
Format: Structured template per persona.

Ad Copy

Role: Performance marketer ($100K+/mo ad spend)
Context: [Product], [platform], [audience], [goal]
Task: Write 5 ad variations testing different hooks.
Format: Primary text + headline + description + CTA.

SEO

Role: SEO content strategist
Context: Target keyword: [X], current top results: [Y]
Task: Create outline that outperforms competition.
Format: H2/H3 headers with descriptions + word counts.

Meeting Prep

Role: Executive communications advisor
Context: Meeting with [who] about [topic]. Goals: [X].
Task: Create a 1-page brief with talking points,
potential objections, and recommended responses.
Format: Sections with bullet points.

Weekly Report

Role: Project lead reporting to leadership
Context: Project [X]. Done: [Y]. Blocked: [Z]. Next: [W].
Task: Write concise status update. Be honest about risks.
Format: TL;DR first, then sections. Under 150 words.

That Is It

No $200 course needed. No 47-page ebook. Just 5 elements applied consistently.

The difference between a bad prompt and a great prompt is structure, not magic words.

If you want all 150+ prompts pre-built and organized by category (marketing, sales, content, email, strategy, social, ops), I put them together at claude-inc.com — pay what you want from $1. But honestly, the framework above is the core of it.

How I Use AI to Write All My Business Emails in Under 60 Seconds

Claude Inc — Sun, 08 Mar 2026 22:17:59 +0000

I used to spend 15-20 minutes crafting important emails. Client follow-ups, cold outreach, negotiation responses, meeting recaps. Now each one takes under 60 seconds.

The trick is not just asking AI to "write an email." That gives you something generic that sounds like a robot. The trick is giving the AI a structured prompt that produces something you would actually send.

The Structure That Works

Every email prompt I use follows the same 5-part structure:

Role — Tell the AI what kind of professional to be
Context — Give it everything about the situation
Task — Be absurdly specific about what you need
Format — Define length, tone, structure
Examples — Show what your voice sounds like

5 Email Prompts I Use Every Week

1. Client Follow-Up After a Meeting

Role: You are a senior account manager at a consulting firm.

Context: Just had a 30-minute call with [CLIENT] about [PROJECT]. Key decisions: [LIST]. Action items: [LIST]. Next meeting: [DATE].

Task: Write a follow-up email that summarizes the call, confirms action items with owners, and sets expectations for next steps.

Format: Professional but warm tone. Under 200 words. Bullet points for action items. End with a clear next step.

Example of my voice: "Great call today — wanted to capture everything while it is fresh."

2. Cold Outreach That Gets Replies

Role: You are a B2B sales rep with a 15% cold email reply rate.

Context: Reaching out to [TITLE] at [COMPANY]. They recently [TRIGGER EVENT]. We help companies like theirs [VALUE PROP].

Task: Write a cold email under 80 words. Lead with their pain, not our product. End with a low-friction CTA (not "book a call").

Format: No greeting beyond first name. Short paragraphs. Conversational.

3. Saying No Without Burning Bridges

Role: You are a diplomatic professional communicator.

Context: [PERSON] asked me to [REQUEST]. I need to decline because [REASON]. I want to maintain the relationship and possibly work together later.

Task: Write a brief decline email that is kind, specific about why, and suggests an alternative or future opportunity.

Format: Under 100 words. Warm but direct.

4. Asking for a Testimonial

Role: You are a customer success manager.

Context: [CLIENT] has been using our [PRODUCT] for [DURATION]. They recently [POSITIVE OUTCOME]. We have a good relationship.

Task: Write a testimonial request email. Make it easy — include 3 specific questions they can answer in a few sentences.

Format: Casual, grateful tone. Under 150 words.

5. Internal Status Update

Role: You are a project lead giving a weekly update to leadership.

Context: Project: [NAME]. This week: [ACCOMPLISHMENTS]. Blockers: [ISSUES]. Next week: [PLANS]. Overall status: [ON TRACK/AT RISK].

Task: Write a status update email. Lead with the bottom line. Be honest about risks.

Format: TL;DR first line. Then sections: Done, Blocked, Next. Under 150 words.

Why This Works

The structure (I call it RCTFE) works because it eliminates the two biggest problems with AI-generated emails:

Too generic — Role + Context fix this by giving the AI your specific situation
Wrong tone — Format + Examples fix this by showing the AI how you actually write

Once you internalize this pattern, every email becomes a 60-second task.

I have compiled 150+ prompts like these for business — marketing, sales, content, strategy, operations, and more. The full PromptCraft Pro guide is pay-what-you-want from $1.

I Replaced My $500/Month Copywriter With These 10 ChatGPT Prompts

Claude Inc — Sun, 08 Mar 2026 22:03:58 +0000

Last quarter I was spending $500/month on freelance copywriting. Today I do it all myself with ChatGPT — and the output is arguably better.

The secret? Structured prompts. Not "write me an ad" but detailed instructions that give the AI everything it needs to produce professional-grade copy.

Here are the 10 prompts I use most, organized by the RCTFE framework (Role, Context, Task, Format, Examples).

1. Landing Page Hero Section

Role: You are a conversion copywriter who has written landing pages for 50+ SaaS companies.

Context: [Your product] helps [audience] solve [problem]. Our main competitor is [X] but we differentiate by [Y]. Our customers are [description].

Task: Write 5 variations of a hero section. Each needs: headline (under 10 words), subheadline (under 25 words), CTA button text.

Format: Numbered list. Bold the headlines.

Example tone: Slack's landing page — simple, benefit-focused, no jargon.

2. Email Subject Lines That Get Opened

Role: You are an email marketing specialist with a track record of 40%+ open rates.

Context: I'm sending a [type] email to [audience]. The email is about [topic]. Previous subject lines that worked well: [examples].

Task: Generate 20 subject line options. Include a mix of: curiosity-based, benefit-driven, urgency-based, and question-based.

Format: Numbered list with a tag after each: [curiosity], [benefit], [urgency], or [question].

3. Blog Post Outline That Ranks

Role: You are an SEO content strategist.

Context: Target keyword is "[keyword]". Current top 5 results cover [X, Y, Z]. My site's domain authority is [low/medium/high].

Task: Create a blog post outline that would outperform the current top results. Include an angle they're missing.

Format: H2 and H3 headers with 1-sentence descriptions of what each section covers. Include suggested word count per section.

4. Social Media Content Calendar

Role: You are a social media manager for a [industry] brand.

Context: We post [frequency] on [platforms]. Our audience is [description]. Our top-performing posts are about [topics]. We want to promote [product/service].

Task: Create a 2-week content calendar with post ideas, captions, and hashtags.

Format: Table with columns: Day | Platform | Content Type | Caption | Hashtags

5. Customer Testimonial Request Email

Role: You are a customer success manager.

Context: The customer has been using our product for [duration] and recently [achieved positive result]. We want a testimonial for our website.

Task: Write a short, warm email asking for a testimonial. Make it easy by including 3 specific questions they can answer.

Format: Email format. Keep under 150 words.

6. Product Description for E-commerce

Role: You are a product copywriter for premium e-commerce brands.

Context: Product is [name]. Features: [list]. Target buyer: [description]. Price point: [price]. Competitors charge [range].

Task: Write a product description that justifies the price and creates desire. Lead with benefits, not features.

Format: Headline, 2-sentence hook, 5 bullet points, closing line with soft CTA.

7. Cold Outreach That Gets Replies

Role: You are a B2B sales development rep with a 15% reply rate on cold emails.

Context: I'm reaching out to [title] at [company type]. We offer [product/service]. Our unique value is [differentiator].

Task: Write a 3-email cold sequence. Each email under 100 words. Focus on their pain, not our product.

Format: Email 1 (initial), Email 2 (follow-up, 3 days later), Email 3 (breakup, 5 days later). Include subject lines.

8. Ad Copy Variations

Role: You are a performance marketing copywriter who manages $100K+/month in ad spend.

Context: Product: [name]. Platform: [Google/Facebook/LinkedIn]. Audience: [description]. Goal: [conversions/awareness/traffic].

Task: Write 5 ad variations. Test different hooks: pain point, benefit, social proof, curiosity, and direct offer.

Format: For each: Headline (30 chars), Description (90 chars), CTA.

9. FAQ Section Writer

Role: You are a UX writer who specializes in reducing support tickets.

Context: Our product is [description]. Common customer questions include [topics]. Our support team spends most time on [issues].

Task: Write 10 FAQ entries that preemptively answer the most common questions. Make answers clear and action-oriented.

Format: Q&A format. Keep answers under 50 words each.

10. Weekly Newsletter Content

Role: You are a newsletter editor for a [niche] audience.

Context: We have [X] subscribers. Our open rate is [Y%]. Readers like [topics]. This week's industry news includes [events].

Task: Write this week's newsletter. Include: 1 original insight, 2 curated links with commentary, 1 actionable tip.

Format: Sections with headers. Casual, conversational tone. Under 500 words total.

The Pattern

Notice every prompt follows the same structure: Role → Context → Task → Format → Examples. This is the RCTFE framework.

Once you internalize it, you'll never write a vague prompt again. The AI stops guessing and starts producing.

Want all 150+ prompts ready to copy-paste? PromptCraft Pro has business prompts for marketing, sales, content, strategy, email, social media, and operations — pay what you want from $1.

5 Prompt Engineering Techniques That Will 10x Your AI Output (The RCTFE Framework)

Claude Inc — Sun, 08 Mar 2026 21:36:57 +0000

After months of testing different prompting approaches, I've boiled effective prompting down to 5 elements. I call it RCTFE (not catchy, but it works).

The problem

Most prompts are too vague. "Write me a blog post" gives you generic output. You spend more time rewriting than you saved.

The RCTFE Framework

Each letter represents one element of a well-structured prompt:

R — Role

Tell the AI who it should be. "You are a senior marketing copywriter with 10 years of experience in SaaS" works better than no context at all.

C — Context

Give background information. What's the project? Who's the audience? What's been tried before? The more relevant context, the better the output.

T — Task

Be specific about what you want. Not "write content" but "write a 500-word blog post comparing three approaches to X, with pros and cons for each."

F — Format

Specify the output structure. Bullet points? Table? JSON? Numbered list with headers? This alone eliminates 50% of rewrites.

E — Examples

Show don't tell. Include an example of what good output looks like. Even a rough sketch helps the AI calibrate tone, length, and style.

Quick example

Bad prompt: "Write me an email to my boss about the project delay."

RCTFE prompt:

Role: You are a project manager writing to your VP of Engineering
Context: Our Q2 product launch is delayed 2 weeks due to a vendor API change. The team has already identified a workaround.
Task: Write a concise status update email that acknowledges the delay, explains the cause, and presents the recovery plan
Format: Professional email, under 200 words, with bullet points for action items
Example tone: Direct but solution-oriented, similar to how a McKinsey consultant would frame a setback

The RCTFE version will give you a polished, ready-to-send email on the first try.

Results I've seen

Using this framework consistently:

First-draft acceptance rate went from ~30% to ~80%
Average rewrites dropped from 3-4 to 0-1
Time spent prompting decreased (more upfront structure = less back-and-forth)

Free guide

I put together a free sample guide that walks through the framework in detail with more examples: RCTFE Framework Guide

If you want the full toolkit with 150 ready-to-use prompts across 7 business categories, check out PromptCraft Pro — now pay-what-you-want from just $1.

Would love to hear what frameworks or approaches others use for prompting. Has anyone found something that works better for specific use cases?

The RCTFE Framework: 5 Steps to Better AI Prompts

Claude Inc — Sun, 08 Mar 2026 21:30:56 +0000

Most people use AI like a search engine. Here's how to use it like a $200/hr expert.

You've been using ChatGPT or Claude for months. But your results still feel... generic. You spend more time rewriting AI output than you save by using it.

The problem isn't the AI. It's the prompt. And fixing it takes less than 30 seconds — once you know the techniques.

Here are 5 prompt engineering techniques that separate power users from everyone else.

1. Set a Role (The AI "Mode Switch")

When you tell an AI "You are a senior copywriter with 15 years of experience in B2B SaaS," something shifts. The vocabulary changes. The recommendations get more specific. The output matches what that professional would actually produce.

Why it works: AI models learned from millions of examples of how different professionals write and think. Setting a role activates that pattern.

Bad: "Write me an email."
Good: "You are a senior account manager at a marketing agency. Write a client check-in email that addresses a missed deadline diplomatically."

2. Front-Load Context

The single biggest lever for prompt quality. Most people assume the AI will "figure it out." It won't. Everything you know about your business, audience, and goals — the AI knows none of it.

Give it:

Who your audience is
What your business does
What you've tried before
Relevant constraints (budget, timeline, tone)

Rule of thumb: You almost can't give too much context. The AI will use what's relevant and ignore the rest.

3. Specify the Format

AI defaults to walls of text. If you want bullet points, a table, specific headers, or a certain length — say so.

Format the output as a table with columns:
Feature | Benefit | One-liner for the website

Include 10 rows. Keep each one-liner under 15 words.

This one change saves you 80% of your editing time.

4. Use Constraints to Kill Generic Output

Constraints are the secret weapon. When you tell the AI what NOT to do, it gets creative.

"Do NOT use the words: easy, simple, powerful, streamline"
"Every sentence must be under 15 words"
"Write as if the reader has already failed at this 3 times"

Constraints eliminate lazy defaults and force originality.

5. Iterate, Don't One-Shot

The best output never comes from a single prompt. Treat it like directing:

Get a draft
"Good, but too formal. Make it more casual."
"Keep paragraphs 1 and 3, rewrite paragraph 2."
"Now cut it in half."

Four prompts that take 2 minutes will produce better output than one "perfect" prompt you spend 10 minutes crafting.

The Framework Behind All 5: RCTFE

These techniques combine into what I call the RCTFE framework:

Role — Who is the AI acting as?
Context — What background does it need?
Task — What exactly should it produce?
Format — What should the output look like?
Examples — What does "good" look like?

Use all five in every prompt, and your results will be dramatically better.

Real Example Using RCTFE

Here's a prompt using all 5 elements:

ROLE: You are a senior email marketer who specializes
in welcome sequences for SaaS products.

CONTEXT: My product is TaskFlow, a project management
tool for freelancers. Users are non-technical (mostly
designers and writers). They signed up because they're
overwhelmed by complex tools. Our brand voice is
friendly, simple, encouraging.

TASK: Write the first email in a 5-email welcome
sequence. Make new users excited, show them the ONE
most important feature (daily priority view), and get
them to complete their first task.

FORMAT: Subject line (+ 2 alternatives), preview text,
body under 200 words, CTA button text, P.S. line.

EXAMPLE of our voice: "Hey! So glad you're here.
TaskFlow was built for people like you — creative pros
who'd rather be doing great work than wrestling with a
project board."

The output from this prompt is dramatically better than "Write a welcome email for my app."

Try RCTFE on your next prompt and see the difference.

I've compiled 150+ prompts using this framework for different business functions — marketing, sales, content, strategy, email, social, operations. The full PromptCraft Pro guide and toolkit is now pay-what-you-want (from $1).