Vague Prompts Are the Real Problem, Not the Model — 50-Run Test Shows Prompt Quality Trumps Model Choice

A Reddit user ran an experiment to test the common claim that one AI model is smarter than another. They took ten common prompts and ran each one through ChatGPT 4, Claude Sonnet, and Gemini 1.5 Pro five times each — 150 outputs total.
What they found: the outputs were weirdly similar in quality. Not identical, but within the same tier. All three either gave something usable or all three gave "generic mush." They almost never disagreed on whether a prompt was answerable. The variable wasn't the model — it was the prompt.
Two prompts, different results
The same vague prompt produced identical bland output across models. For example:
"Write a cover letter for a marketing job"
All three returned the same kind of generic, applicable-to-anyone cover letter. People would call it a "ChatGPT cover letter" then try Claude and call it a "Claude cover letter" — same letter, different name.
But a specific prompt changed everything:
"Write a cover letter for a senior marketing role at a B2B SaaS company. I have 7 years of growth experience, mostly at Series A/B startups. The hiring manager is technical, ex-engineer. Avoid generic phrases like 'passionate about' or 'results-driven.' Use specific numbers from my background where it makes sense to invent plausible ones. Target 280 words."
All three returned something actually good. Different in style, but all useful.
Common pattern in complaints
The user reviewed dozens of "AI is so bad" complaints on Twitter and Reddit and noticed the same pattern: prompts like:
"Help me with my resume""Write a marketing plan""Explain quantum physics""Make this code better"
These prompts fail because they don't specify who you are, who it's for, what good looks like, or what to avoid. The model has to guess the most common version of that request — which is a generic template.
Mental model: prompt as brief
The key insight: stop thinking of it as "asking AI a question." Think of it as "writing a brief for an intern." A good brief tells the intern the audience, what success looks like, what to avoid, format, constraints, and at least one example of the kind of output you want.
Once the user started writing prompts like briefs, the model switching stopped. ChatGPT, Claude, and Gemini all got dramatically better — not because the models changed, but because the prompts changed.
If you're tempted to switch models because one gives bad results, try sharpening your prompt first. The model differences are real but much smaller than the prompt differences.
📖 Read the full source: r/ClaudeAI
👀 See Also

Claude CLI v2.1.154 Breaks Local vLLM — One-Line Patch Fixes It
Claude CLI ≥2.1.154 adds three new API roles (ctx, msg, system) that break local vLLM compatibility. A one-line patch to vLLM's Anthropic protocol restores it.

Top 5 Not-So-Obvious Agent Skills for Frontend Developers Using Claude AI
A frontend developer shares 5 specific Skills for Claude AI agents that improve productivity and code quality: Playwright, Advanced Types for TypeScript, LyteNyte Grid, Tailwind CSS Patterns, and PNPM Skills.

Managing Claude AI Token Consumption: Practical Tips from Developer Experience
A developer reports burning 94,000 tokens in 3 minutes using Claude's Explore feature, leading to rate limiting for 4 hours, and shares concrete strategies including maintaining an ARCHITECTURE.md file and using surgical prompts to control token usage.

The Prompt Structure That Fixed Claude AI Summaries of Large PDF Reports
A developer shares how switching from 'summarize this' to role + decision + specific extraction prompts turned Claude's generic summary output into actionable risk flags and concrete action items.