The Anatomy of a Great Prompt

Most people write prompts like they're typing into a search bar. Short, vague, missing context. Then they're surprised when the output is generic.

Here's the framework that fixes that.

The RCTFC Framework

Every great prompt has five elements. You don't need all five every time, but the more you include, the better your results.

Why This Works

RCTFC works because it mirrors how you'd brief a real person. Nobody walks into a consultant's office and says "do marketing." You explain who you are, what you need, and what the constraints are. Claude works the same way.

The framework also eliminates the most common failure mode: ambiguity. Every element you add removes a dimension of guessing. And every time Claude guesses, the output gets more generic.

Building a Prompt Step by Step

Let's take a real task and build it up using RCTFC.

The task: You need a cold email for your SaaS product.

Write a cold email for my SaaS product.

When You Don't Need All Five

Not every prompt needs the full RCTFC treatment. Here's the practical guide:

Quick tasks (Task only):

"Summarize this email thread in 3 bullet points: [paste]"

For simple, well-defined tasks, a clear Task is often enough. Claude will infer reasonable defaults for everything else.

Medium tasks (Role + Context + Task):

"You're a financial analyst. Here's our Q3 revenue data: [paste data]. Identify the three most significant trends and explain why they matter."

When the output needs a specific perspective or you're providing data, add Role and Context.

Complex tasks (Full RCTFC):

The full framework. Proposals, content pieces, strategic analysis, anything where quality matters and you want to minimize back-and-forth.

The Role Element Deep Dive

The Role is the most underused element. It fundamentally changes how Claude approaches your task — not just the content, but the entire analytical framework.

Review this pricing proposal and identify concerns.\n\n[As a CFO]: Focus on financial risks, margin impact, and cash flow implications.\n\n[As a sales leader]: Focus on what will make this hard to close deals and where deals will stall.\n\n[As a customer]: Focus on what would make you hesitate to buy and where you'd push back.

Each role surfaces different insights from the same document. The CFO catches margin risk. The sales leader spots friction in the buying process. The customer flags confusing pricing tiers. All three perspectives are valuable — and you can get all three in one conversation.

Effective roles for business operators:

• Devil's advocate — Forces Claude to challenge your assumptions instead of validating them
• Industry analyst — Gets structured, data-oriented analysis
• Executive coach — Gets thoughtful questions and frameworks, not just answers
• Experienced copywriter — Gets punchy, conversion-focused writing
• Board member — Gets the hard questions you haven't thought of

The Context Element Deep Dive

Context is where most people underinvest. Here's what to include:

Company context: What you do, your market, your size, your stage. Claude writes very differently for a 5-person startup vs. a 500-person enterprise.

Audience context: Who will read this? Their role, sophistication level, what they care about, what they already know.

Situational context: What prompted this task? A customer complaint, a board meeting, a competitive move? The "why" behind the request shapes the output.

Historical context: What have you tried before? What's worked and what hasn't? This prevents Claude from suggesting things you've already ruled out.

Context: We're a B2B SaaS company ($8M ARR, 200 customers) that sells to mid-market e-commerce companies. We just lost our 3rd enterprise customer this quarter to [Competitor X], who launched a cheaper tier. Our churn has increased from 3% to 5% monthly.\n\nOur CEO is presenting to the board next week and needs a retention strategy that we can execute with our current team of 12 (no new hires approved until Q3).\n\nTask: Draft a 90-day retention plan that addresses the competitive threat without a price cut. Include specific tactics, owners, and success metrics.

The Format Element Deep Dive

Format is the secret weapon for getting output you can actually use. Without format guidance, Claude defaults to long-form prose with headers — which is fine for some tasks but terrible for others.

Formats that work well:

The Constraints Element Deep Dive

Constraints are the guardrails that prevent Claude from going off track. They're especially important for writing tasks.

Common constraints that improve output:

• Word/length limits — "Under 200 words" or "2-3 paragraphs max"
• Tone restrictions — "No jargon" or "Write at an 8th-grade reading level"
• Content exclusions — "Don't mention pricing" or "Don't reference competitors by name"
• Audience calibration — "They already know what our product does, don't re-explain it"
• Structural rules — "One idea per paragraph" or "Lead with the data, then interpret"

Common Patterns That Work

These are copy-paste patterns you can use in any conversation:

The Devil's Advocate

I'm about to make a decision and I want you to challenge my assumptions. Don't validate my thinking — poke holes in it. Ask me the questions I'm not asking myself. Be direct about where my logic is weak.\n\nHere's my plan: [describe your plan]

The Structured Analysis

Analyze this and format your response as:\n1. Executive Summary (3 sentences max)\n2. Key Findings (bullet points, prioritized)\n3. Recommendations (numbered, with effort level: low/medium/high)\n4. Risks (if any, with mitigation suggestions)\n\nHere's what I need you to analyze: [paste content]

The Iterative Draft

Let's work on this iteratively. Start with a rough first draft — don't try to be perfect. I'll give you specific feedback, and we'll refine from there.\n\nHere's what I need: [describe the task]\n\nAfter the draft, tell me what decisions you made and where you'd like my input.

The Multi-Perspective Analysis

Analyze this from three perspectives:\n1. The optimistic case — what goes right and why\n2. The pessimistic case — what could go wrong and why\n3. The realistic case — what's most likely to happen\n\nThen tell me which perspective I should weight most heavily and why.\n\nHere's the situation: [describe the situation]

A Complete Example

Let's put it all together with a real scenario:

The RCTFC Cheat Sheet

Keep this handy until the framework becomes second nature:

Next Steps

You now have the framework. The next playbook — Projects, Memory & Skills — shows you how to make this context persistent so you don't have to write a full RCTFC prompt every time. You'll bake the Role, Context, and Constraints into your Project instructions, and your daily prompts become just Task + Format.