Picture someone copying a prompt off a Reddit thread, tacking on “take a deep breath” at the end, and feeling clever about it. That someone was me, eight months ago. I had a whole folder of these. “You are an expert with 20 years of experience.” “Think carefully before responding.” “This is very important to my career.” I stacked them like I was building a sandwich, convinced that more layers meant better output.
Then a researcher named u/AIMadesy spent three months running actual controlled tests. 120 popular prompt “codes.” A fixed task battery. Measured results. What he found is either vindicating or embarrassing, depending on how many prompt hacks you’ve been stacking.
🧪 Why This Actually Matters
Most prompt advice is anecdotal. “This worked for me once” dressed up as a system. Nobody holds the task constant and changes one variable at a time. Nobody runs the comparison. The advice spreads because it sounds plausible, someone shares it in a Discord, it gets 400 upvotes, and suddenly half the internet is appending “let’s think step by step” to every prompt like it’s a magic incantation.
This guy did the actual work. Three months, one guide, real numbers. He ran the same task repeatedly, isolated variables, and measured outcomes instead of vibes. The findings hit different when there’s data attached. You stop arguing about what should work and start seeing what does.
📍 Three Things That Surprised Him (and Should Surprise You)
1. Where your scope sentence lives matters more than how it’s worded.
He used to obsess over phrasing things like “review only the database logic.” Turns out that was the wrong variable. Moving the exact same sentence from the end of a prompt to the beginning cut token output by 30%. Position, not phrasing. Claude pays more attention to what comes first. Think of it like a conversation: if you tell a friend what you need upfront, they listen differently than if you drop it as an afterthought at the end. Front-load your constraints or they get fuzzy, and you end up with a 1,200-word response when you needed a quick summary.
2. About half the famous prompt techniques are decorative.
Of 120 popular prompt codes tested, 47% had zero measurable effect over a plain prompt. “Take a deep breath” worked on older Claude, does nothing on Sonnet 4.6 or Opus 4.7. “You are a Stanford-trained expert” actually makes reasoning worse on complex tasks, possibly because it anchors the model toward confident-sounding output rather than careful analysis. “Please respond only in JSON” still needs structure hints, not just the request. Most “step by step” variants are already default behavior on modern Claude versions. You’ve been typing extra characters for nothing, and worse, some of them are actively hurting output quality.
The irony is that the techniques most confidently shared online tend to be the oldest ones, tested on Claude 2 or early 3, never updated. They became gospel before anyone checked whether they still applied.
3. Skill file descriptions are basically everything.
If you use Claude Code with custom skills and they’re not auto-activating, the description field is almost always the culprit. “Helps with database stuff” never triggers. “Use when configuring database connection pooling, choosing pool sizes, or debugging connection exhaustion” triggers reliably every time. The model pattern-matches the user’s intent against that description in real time. Vague descriptions match weakly. Specific ones win. This one change, rewriting your skill descriptions to name the exact scenario, will do more for your Claude Code workflow than any prompt trick you’ve collected.
💡 Tips Worth Stealing Right Now
Scope goes first, full stop. Don’t bury constraints at the bottom. Front-load them and watch Claude actually stay on task instead of drifting into a five-paragraph essay when you needed a bullet list.
Test your favorite hacks on a fixed task. Run the same task with and without your “magic phrase” and compare outputs directly. Use the same input every time, don’t change the topic or complexity. You’ll know within two runs whether it’s doing anything real. If you can’t tell the difference, it isn’t making one.
Audit your existing prompts once a quarter. Models update, default behaviors shift, and what worked six months ago may now be redundant or counterproductive. Treat your prompts like code: they need maintenance, not just accumulation.
Write skill descriptions like search queries. Think about the exact moment someone would reach for this skill. Name that moment explicitly. “Use when the user asks about X, Y, or Z” is always better than “helps with things related to X.” Specificity is what triggers reliable activation.
🚀 Want the Other 9 Lessons?
The full guide is 40 pages, free, no email required. Nine more findings from the same testing process, covering everything from system prompt length to tool use patterns. If you’re building seriously with Claude, it’s worth the half hour. The kind of stuff you won’t find in a Reddit thread because nobody bothered to test it before posting.
And next time you’re tempted to add “take a deep breath” to a prompt, at least run a quick A/B test first. You probably won’t bother with it after that.
Frequently Asked Questions
Q: Why does putting scope at the beginning of a prompt work better than putting it at the end?
It’s about how Claude processes context. When you front-load the scope, the model’s attention mechanisms treat everything that follows as filtered through that specific constraint. If you bury the scope at the end, the model has already built a generalized understanding of the context, then has to backtrack to reconcile your constraint against what it already processed. Practically: put “Only review the database logic” at the top, and you’ll get tighter, more focused outputs.
Q: How do I actually test whether a prompt technique works, or am I just seeing random variation?
Keep your inputs identical and change only the prompt. Many people accidentally vary both at once, so they never know which variable actually mattered. Run the same task through 5+ prompt variations in isolation, measure token count or output quality, and look for consistent patterns. Anecdotal “it worked once” testing is noise; systematic comparison is signal.
Q: Do I really need all those prompt techniques people swear by?
Not anymore. Testing 120 popular techniques found 47% had zero measurable effect on Sonnet 4.6 or Opus 4.7. Things like “take a deep breath” worked on older Claude, but newer versions handle implicit logic without hand-holding. Some techniques actually hurt on reasoning tasks. Keep what works for your workflow, but don’t assume viral prompt advice is still current.
Q: My skill file isn’t auto-activating. What’s wrong?
The description is probably too vague. “Helps with database stuff” almost never triggers because it has low semantic similarity to specific queries like “I’m hitting connection pool limits.” Rewrite it to be hyper-specific: “Use when configuring database connection pooling, choosing pool sizes, or debugging connection exhaustion.” Vague descriptions = weak matches. Specific ones win reliably.
spent 3 months testing claude prompts for a guide, 3 things that surprised me
by u/AIMadesy in PromptEngineering