A weak prompt almost always fails for one of five specific reasons — not because you "used the wrong words." This guide gives you the CLEAR framework (Context, Length & format, Examples, Ask for uncertainty, Refine) built directly from OpenAI's and Anthropic's own published prompt engineering guidance, plus a before/after example and a diagnostic checklist so you can find the exact letter your prompt is missing.
Most people troubleshoot bad AI output by rewriting the whole prompt from scratch, or by adding vague phrases like "be more detailed" or "try harder." That rarely works, because it does not address which specific ingredient is missing. The five ingredients below cover nearly every failure pattern — and they matter whether you're using ChatGPT for one of the income paths in our guide to making money with AI or for the marketing tools in our roundup of AI tools for marketers. Prompt quality, not the tool or the business model, is usually the real bottleneck.
Why "Just Ask Better" Advice Doesn't Work
Generic advice like "be more specific" is true but useless — it does not tell you specific about what. Anthropic's own prompt engineering guidance, updated November 2025, frames it more usefully: state exactly what you want without ambiguity, and explain why it matters, not just the rule itself. OpenAI's prompt engineering documentation makes a related point — a prompt should be organized into clear sections (identity, instructions, examples, context) rather than a single unstructured block of text, because the model has to guess less when the structure does the organizing for it.
In practice, both companies converge on the same five underlying ingredients. We grouped them into a mnemonic so you can check your own prompts against it in under a minute.
The CLEAR Framework
C — Context. State who the output is for and why the task matters, not just what to produce. Anthropic's guidance specifically calls out sharing the reasoning behind a constraint, not just the constraint itself — a model that understands why you want short paragraphs will generalize that intent better than one that was only told "keep it short."
L — Length & format. Specify word count, structure, and output shape up front — and tell the model what to do instead of what not to do. "Write three short paragraphs in plain prose" works better than "don't use bullet points," because the second version still leaves the model to guess at the actual format you want.
E — Examples. Show one or two examples of the output you want instead of describing it in the abstract. OpenAI calls this few-shot learning — providing sample input/output pairs so the model can infer the pattern — and Anthropic's guidance singles it out as "particularly effective for tone, style, and subtle patterns" that are hard to describe in words.
A — Ask for uncertainty. Explicitly give the model permission to say "I don't know" or "I'm not sure" instead of guessing. Anthropic's guidance is direct on this point: allowing the model to acknowledge limitations reduces confident-sounding wrong answers — a small addition with an outsized effect on factual tasks.
R — Refine. Treat your first prompt as a draft, not a final answer. Both companies recommend testing and iterating rather than trying to perfect a single mega-prompt — OpenAI frames this as testing changes systematically, and Anthropic recommends starting simple and adding complexity only once you have confirmed it actually helps. For a genuinely complex task, break it into a sequence of smaller prompts (prompt chaining) instead of asking for everything in one shot.
Before and After: One Prompt, Fixed With CLEAR
Here is a typical vague prompt and the same request rebuilt using all five letters:
| Version | Prompt |
|---|---|
| Before | "Write me a LinkedIn post about using AI in marketing." |
| After (CLEAR) | "I'm a freelance marketing consultant posting to LinkedIn to attract small-business clients (Context). Write one LinkedIn post, 120-150 words, three short paragraphs, no bullet points or hashtags (Length & format), in the direct, slightly informal style of this example: [paste a real post you like] (Examples). If you're not confident a specific stat is accurate, flag it instead of stating it as fact (Ask). I'll give you feedback and we'll do a second pass (Refine)." |
The "after" version is longer to write, but it removes almost every decision the model would otherwise have to guess at — audience, tone, structure, and honesty boundaries are all specified instead of implied.
Two Techniques That Matter Less Than They Used To
Older prompt-engineering advice still circulating online recommends two techniques that Anthropic's current guidance now downgrades. Wrapping every prompt section in XML tags was once recommended for structure; Anthropic now describes it as "less critical" given how much better current models understand plain, well-organized instructions without it. Heavy role-prompting — forcing an elaborate persona like "you are a world-class expert with 20 years of experience" — is the second: Anthropic's guidance notes that heavy-handed personas often constrain helpfulness rather than improving it, and that requesting a specific perspective directly tends to work better than dressing it up as a character. If a prompt you copied from an old thread isn't working, one of these two outdated habits is a common reason.
Diagnostic Checklist: Which Letter Is Missing?
Match the symptom you're seeing to the most likely missing ingredient:
- Output is generic or "could have been written by anyone": almost always missing Context — the model doesn't know who this is for or why it matters.
- Output is the wrong length, or in the wrong structure (paragraphs instead of a table, etc.): missing Length & format — say exactly what shape you want, not what you don't want.
- Tone or style is close but not quite right: missing Examples — describe it less, show it more.
- Model states something confidently that turns out to be wrong: missing Ask — you never gave it permission to say "I'm not sure."
- First draft is decent but you keep rewriting the whole prompt from zero: missing Refine — give feedback on the output you got instead of starting over.
Frequently Asked Questions
Do I need to use all five letters in every prompt? No. Both OpenAI and Anthropic recommend starting simple and adding only the ingredients that address your specific problem — a quick brainstorming prompt doesn't need the same structure as a client deliverable.
Does this apply to Claude and Gemini too, or just ChatGPT? The five underlying ingredients come from Anthropic's own guidance for Claude and align closely with OpenAI's guidance for ChatGPT, so the framework transfers across major assistants — the interface differences don't change what the model needs to do good work.
Is there a shortcut for reusing good prompts instead of rebuilding CLEAR from scratch every time? Yes — once you've built a CLEAR prompt that works well for a repeatable task (a weekly report, a type of social post, a client email), save it as a template rather than rewriting it. That's the entire idea behind a structured prompt library.
Stop Rebuilding Prompts From Scratch
AI Prompt Library PRO gives you 500 ready-to-use prompts across 10 business categories, already built using the same principles as the CLEAR framework — so you paste, adjust the specifics, and go.
Get AI Prompt Library PRO — $27Sources: Anthropic, "Prompt engineering best practices for 2026" (published November 10, 2025); OpenAI, "Prompt engineering" — OpenAI API documentation. Last reviewed: August 2026.