How To Write AI Prompts That Actually Work: The Framework

The difference between a mediocre AI output and an expert-level one is usually the quality of the prompt. Most people don't understand this. They think "the AI is just not good enough." Wrong. They're just not prompting well enough.

I use the RACE Framework for every single prompt I write. It's the framework I developed over years of working with AI, and it's become the foundation for RACEprompt.

Why Most Prompts Fail

A bad prompt sounds like this: "Write me a marketing email about my product." That's not a prompt. That's a vague request with no context.

Good prompts sound like this: "I sell productivity software to busy executives. My audience is skeptical of new tools and needs clear ROI. My brand voice is direct and practical, not salesy. Write a 200-word email about the specific time I save vs. cost trade-off. Make the first sentence a stat that surprises them."

The difference is night and day. The second prompt gives the AI what it needs to actually help you.

The RACE Framework Breakdown

Every great prompt has four components:

R: Role

Who are you and what role should the AI play? Your professional background, expertise, and the perspective you want. Any context that helps the AI understand who you are and how to approach the task.

A: Action

What specifically do you need created or done? Be clear about the task, the format, and the scope. This is where you define exactly what you're asking for, not just a vague request.

C: Context

What's the background situation? Your business context, constraints, challenges, and why this matters. This is where you explain the circumstances around your request.

E: Expectation

What should the output look like? How will you know it's good? What defines success? Be specific enough that you could hand this criteria to a human and they'd know exactly what you want.

How to Actually Use This

When you're about to ask AI for something, run through this checklist:

• Have I given enough context about my situation and audience?
• Have I explained the problem I'm trying to solve, not just the task?
• Have I been specific about format, length, tone, and success metrics?
• Is my actual request clear and specific?

If you can check all four boxes, you're ready to prompt.

I've tested this framework with hundreds of prompts across every category you can imagine—writing, code, analysis, strategy, creative work. The consistency is remarkable. Better structure in the prompt almost always leads to better output.