Out of 50+ supposedly-secret Claude prompt codes floating around AI communities, 86% do nothing. A few make Claude worse.
That’s what a Redditor discovered after six weeks of controlled testing. The post author ran before/after comparisons on Claude Opus 4.6 and Sonnet 4.5, fresh conversation each time, documented every result. Across the full list, only 7 codes survived. I’ve seen a lot of “unlock Claude’s hidden mode” posts that fall apart the moment you actually test them. This one holds up because the methodology is sound.
Why Most Codes Fail
None of the working codes are official Anthropic features. They work because Claude’s training data includes thousands of developers using these exact patterns in real prompts. The model learned the convention from those examples, not from any built-in command system.
That’s why vague uppercase strings like ALPHA, OMEGA, or BEASTMODE do nothing. There’s no learned convention behind them, so Claude treats them as noise. It’s also why /jailbreak paradoxically makes Claude more cautious. The model’s training data for that string is full of adversarial attempts, so it triggers a defensive response instead.
The working codes share one trait: a real, observable pattern in how developers used them before Claude was trained on that data.
The 7 That Changed Output
The author documented each one with before/after comparisons. Here’s the breakdown:
L99 forces commitment. Ask about Postgres database structure and you get a 200-word menu of options. Add L99 before the question and you get an 800-word opinion-first answer that picks one approach, explains exactly why it wins, and walks through the migration cost of getting it wrong. The hedging disappears.
/ghost strips AI writing tells. No “Here’s what I think,” no “It’s worth noting,” no closing commentary. Ask for a startup tagline and instead of a numbered list with “I hope these help!”, you get: “Ship faster. Sleep better.” For anyone writing marketing copy or content, this one pays off fast.
/deepthink forces Claude to reason through every layer before answering. Slower output, dramatically better quality on complex problems. Best for debugging, architecture decisions, and any question where the fast answer is probably wrong.
OODA structures the response as Observe-Orient-Decide-Act, a military decision loop. The author found it works well for production incidents, architecture decisions, and postmortems; any situation with uncertainty and time pressure.
ARTIFACTS shifts Claude from explaining to building. Ask for help launching a landing page and you get best-practice advice. Add ARTIFACTS and you get “ARTIFACT 1: Hero copy. ARTIFACT 2: Feature grid. ARTIFACT 3: Pricing table. ARTIFACT 4: HTML implementation.” Then it builds each one.
/mirror style-locks Claude to match your writing after you give it a sample. Sentence rhythm, vocabulary, register. Useful when you need output that sounds like you, not like a polished AI draft.
PERSONA only works with specificity. “PERSONA: senior developer” barely changes anything. “PERSONA: Senior backend engineer at Stripe, 12 years, hates ORMs, has been burned by Kubernetes three times” produces dramatically different output. The model responds to stated bias and history, not job titles.
3 Practical Applications
- Code and architecture review: L99 plus a specific PERSONA gets you opinionated feedback instead of a list of tradeoffs to consider. Combine them for decisions where you actually need a recommendation, not a menu.
- Marketing and content writing: /ghost removes the layer of AI self-commentary that makes copy feel generated. Combine with /mirror if you have writing samples. The before/after difference is noticeable in the first paragraph.
- Complex decisions under uncertainty: OODA for incidents and postmortems, /deepthink for any “why” question where the fast answer is likely wrong. These two are the most underused of the seven.
Tips and Pitfalls
The failure list is as useful as the working list. The author documented what to skip:
/jailbreak makes Claude more cautious. DAN mode is a ChatGPT meme; Claude has no reference point for it. /godmode produces longer responses, not sharper ones. BEASTMODE is the same, just louder. Generic PERSONA tags like “PERSONA: developer” add almost nothing without specificity.
The bigger pitfall is treating these as permanent features. The author retests the full list every two weeks because Claude model updates shift what works. Some codes from six months ago are now noise.
One note on methodology worth keeping: most “prompt hack” lists don’t test with fresh conversations. Prior context in the same session contaminates results because Claude naturally adjusts to your style over a session. The author ran each test in a clean context, which is why these replicate when you try them yourself.
Check the Original Thread
The community reaction on r/PromptEngineering was split; some called it traffic bait, others dug into the methodology. Both perspectives are worth reading. The full before/after examples and the debate about what actually drives the PERSONA effect are in the original post. Worth 10 minutes if you use Claude for technical work.
Frequently Asked Questions
Q: Isn’t this just clickbait marketing?
Format-wise, yeah, it looks like the classic listicle (“tested 50, here’s the 7 that work”). But the methodology seems legit – fresh conversations, systematic testing, honest about what didn’t work. Real question: does it matter if it drives traffic, or only if the codes actually help you? Test them yourself.
Q: Is the secret prompt code more important than the context I give Claude?
Nope. One commenter made a great point: context documents (rules, examples, constraints) do the heavy lifting. The actual prompt just steers. So if you’re chasing secret codes without solid context setup first, you’re missing the bigger win.
Q: Should I try to memorize all 50 prompts?
Hard no. Most people end up using 2-3 repeatedly – the ones that actually solve problems in their workflow. Find your 2-3, ignore the rest. Quality over quantity wins here.
Q: Do these codes actually work?
The author shows before/afters for 7 codes and claims they change Claude’s behavior. But “trust but verify” applies here. Try them in your own conversations and see if they stick for you. That’s the only test that matters.
I tested 50 ‘secret’ Claude prompt codes. Most are fake. Here are the 7 that actually changed how Claude responds (with before/after)
by u/AIMadesy in PromptEngineering