Claude Secret Code Combos — 9 Stacking Patterns That 3x Your Output (2026)

Single codes are training wheels

Most guides on "Claude secret codes" stop at the single-code level. You learn L99, you learn /ghost, you learn PERSONA, and you use them one at a time on different prompts. That's how you get started.

What almost nobody documents is that you can stack them. Two or three prefixes on the same prompt, in the right order, produce results that no single code can match. The stacking pattern matters — some combos compound, others cancel each other out, and a few actively make Claude worse.

We tested over 40 combos across writing, coding, decision-making, and sales tasks throughout March and April 2026. Here are the 9 that consistently outperformed the best single code, with the use case for each.

Why stacking works

Each prompt prefix tells Claude something about what kind of response you want. A single prefix changes one dimension. Stacking changes multiple.

For example:

• L99 says: commit to one answer instead of giving me a menu
• PERSONA: <expert> says: answer from this specific person's point of view
• Combined: commit to one answer, from this specific expert's point of view

The combination is not additive — it's multiplicative. A senior backend engineer with 12 years of experience giving you a committed opinion is a different kind of answer than either prefix alone.

The catch: order matters, and not all prefixes play nicely together. Stacking 5 prefixes is almost always worse than stacking 2. The sweet spot is 2-3.

The 9 combos that work

1. PERSONA + L99 — The expert who actually has an opinion

The combo: PERSONA: <specific expert with bias and experience>. L99 <your question>

What it does: Forces Claude to answer from a specific expert's point of view AND commit to a single recommendation instead of hedging.

Example:

PERSONA: Senior Postgres DBA with 15 years at Stripe, hates ORMs, has seen every connection pool bug in production. L99 Should I use PgBouncer or RDS Proxy for my fintech app at 10K QPS?

Why it works: L99 alone gives you a committed opinion from generic-Claude. PERSONA alone gives you a perspective but Claude still hedges. Together, you get the committed opinion of someone who has actually been in production. The bias of the persona makes the recommendation stronger, not weaker.

Best for: Technical architecture decisions, infrastructure choices, hiring trade-offs.

2. /skeptic + ULTRATHINK — Question the question, then go deep on the answer

The combo: /skeptic ULTRATHINK <your question>

What it does: Claude first challenges whether you're asking the right question, then if the question survives, gives you a thesis-depth answer.

Example:

/skeptic ULTRATHINK Should I add a recommendation engine to my 500-user app?

Claude will probably tell you no — your app doesn't have enough data to justify the engineering cost. But if your situation actually warrants the engine, it will give you a 1000-word breakdown of the build-vs-buy trade-off.

Why it works: ULTRATHINK alone goes deep on whatever you ask. /skeptic alone challenges the question but doesn't always give you the alternative. Together, you get the right question AND the right depth of answer.

Best for: High-stakes strategy decisions, product direction, pivot questions.

3. /ghost + /punch — The cold email combo

The combo: /ghost /punch <text to rewrite or generate>

What it does: Removes AI tells (/ghost) AND makes every sentence hit harder (/punch). The result reads like a sharp human wrote it, not like AI.

Example:

/ghost /punch Rewrite this cold email to a SaaS founder. Original: "Hi John, I hope this finds you well. I wanted to reach out about an exciting opportunity..."

What you get back: an opening line that doesn't waste a word, no "I hope this finds you well," no "I wanted to reach out," and a clear ask in 4 lines instead of 12.

Why it works: /ghost alone humanizes the writing but can leave it flabby. /punch alone tightens the writing but can leave the AI patterns intact. Together, the email reads like the kind of cold email you'd actually reply to.

Best for: Cold outreach, sales follow-ups, LinkedIn DMs.

4. PERSONA + WORSTCASE — The risk-assessment combo

The combo: PERSONA: <expert>. WORSTCASE <your plan>

What it does: Asks a specific expert what they would be most worried about if you executed your plan. Surfaces failure modes you hadn't considered.

Example:

PERSONA: Security engineer at a Series B SaaS, has been on call during three breaches, deeply paranoid about session tokens. WORSTCASE We're rolling out SSO next week using a cookie-based session model.

Claude will list the specific failure modes a paranoid security engineer would bring up: cookie hijacking, CSRF, session fixation, the specific Cloudflare config mistakes that have leaked sessions in the past.

Why it works: Generic risk analysis gives you generic risks. Specific persona + worst-case framing gives you the risks that actually happen to people like you.

Best for: Pre-launch reviews, security audits, deploy planning, anything where the cost of being wrong is high.

5. /mirror + /trim — The voice-locked tightener

The combo: Show Claude a writing sample first, then /mirror /trim <text to rewrite>

What it does: Locks Claude into your writing style (/mirror) AND cuts every unnecessary word (/trim). The result sounds like you, but tighter than you usually write.

Why it works: /mirror alone matches your voice but can match your verbosity too. /trim alone tightens the writing but loses your voice. Together you get a sharper version of your own writing.

Best for: Editing your own draft posts, ghostwriting, polishing tweets that sound like you.

6. ARTIFACTS + /shipit — The deliverables combo

The combo: ARTIFACTS /shipit <task>

What it does: Forces Claude to output a numbered list of concrete deliverables (ARTIFACTS) AND make each one production-ready (/shipit). No theory, no explanations — just the artifacts you need to ship.

Example:

ARTIFACTS /shipit I need to launch a landing page for a $599 desktop app for SaaS sales teams.

Claude returns numbered artifacts: hero copy, feature grid, pricing table, FAQ, HTML implementation. Each one is shippable as-is, not a draft.

Best for: Solo founders who don't have time for theoretical breakdowns. Just give me the things and I'll ship them.

7. /deepthink + /blindspots — The pre-decision combo

The combo: /deepthink /blindspots <decision>

What it does: Reasons through every layer of the decision (/deepthink) AND surfaces what you're not seeing (/blindspots). The combination catches both the obvious analysis and the things you don't know that you don't know.

Example:

/deepthink /blindspots I'm thinking of moving from a monolith to microservices because deploys are getting slow.

Claude walks through the deploy problem ("slow deploys are usually fixed at the build pipeline level, not the architecture level"), then surfaces the blindspots ("you're about to trade slow deploys for distributed-systems debugging, and your team has no SRE experience").

Best for: Major technical or product decisions where you're already 80% convinced — and that's exactly when you most need someone to check your blindspots.

8. PERSONA + /steelman — The opposition combo

The combo: PERSONA: <expert who would disagree with you>. /steelman <your position>

What it does: Asks a specific expert who would disagree with you to make the strongest possible argument against what you're planning. The persona makes the disagreement specific and credible.

Example:

PERSONA: 20-year enterprise sales leader who built and sold three SaaS companies, deeply skeptical of product-led growth. /steelman My plan: ditch outbound sales entirely and go pure self-serve with a free tier.

Claude will give you the actual case against pure self-serve from someone who has lived through the trade-offs — and the case will be stronger than anything you'd construct yourself, because you're emotionally attached to your plan.

Best for: Validating a contrarian decision before you commit to it. The strongest test of any plan is the strongest argument against it.

9. CONTEXT + L99 + /raw — The clean answer combo

The combo: CONTEXT: <background>. L99 /raw <question>

What it does: Loads relevant background context (CONTEXT), forces a committed answer (L99), and strips all formatting (/raw) so the response is plain prose with no headings, bullets, or markdown. The result reads like a one-paragraph answer from a thoughtful colleague over Slack.

Example:

CONTEXT: Solo founder, $30K total revenue so far, 2 part-time contractors, runway of 8 months, last week's launch hit r/SaaS top page. L99 /raw Should I hire a full-time engineer now?

You get back a single short paragraph with a committed answer and the specific factors that informed it — not a 600-word essay with three bulleted lists.

Best for: Questions where you don't need a document, you need an opinion. Slack-level answers, not blog-level answers.

Combos that DON'T work (we tested these)

Not every combination compounds. These are the ones we tested that produced worse results than either single code:

• /godmode + ULTRATHINK — Both push for maximum output. Together you get 2000-word responses that meander without ever getting to the point. Pick one.
• /ghost + PERSONA — /ghost strips the AI fingerprints, but PERSONA's specificity often gets lost when /ghost flattens the voice. The answer becomes generic.
• /raw + ARTIFACTS — Contradictory: /raw strips formatting, ARTIFACTS demands structured deliverables. Claude picks one and ignores the other (usually /raw wins).
• /deepthink + /punch — /deepthink wants to explain, /punch wants to compress. The explanation gets compressed past the point of usefulness.
• OODA + ULTRATHINK — OODA is already a structured deep-thinking framework. Adding ULTRATHINK on top just makes the OODA structure 3x longer without adding insight.

The pattern: combos that change different dimensions compound (style + commitment, persona + reasoning, context + format). Combos that change the same dimension fight each other.

How to think about stacking

A simple rule of thumb: pick prefixes from different categories.

• Persona category: PERSONA, CONTEXT
• Reasoning depth category: L99, ULTRATHINK, /deepthink, OODA
• Question challenge category: /skeptic, /steelman, /devil, /blindspots
• Output style category: /ghost, /punch, /trim, /mirror, /raw
• Output structure category: ARTIFACTS, /table, /json, /checklist

Pick one from 2-3 different categories and combine. Don't pick two from the same category.

Get all 120 codes (and the full combo guide)

Free: Browse 11 working codes at clskills.in/prompts — click to copy, no signup.

Full reference (120 codes + 30+ combo recipes, $5-$10): The Claude Code Cheat Sheet Pro tier includes every tested combo with the use case, the order that matters, and the situations where it fails. Lifetime updates.

Related guides

• 100 Claude Secret Codes — The Full List
• 7 Hidden Claude Prompts That Actually Work
• Claude Cheat Codes — The Complete Guide
• L99 Claude Explained
• PERSONA Claude Prompt Guide
• /skeptic Claude Prompt Guide
• ULTRATHINK Claude Prompt Guide

TL;DR

Claude secret codes are useful one at a time — they're 3x more useful when stacked correctly. The 9 combos that consistently outperform single codes are: PERSONA+L99 (technical decisions), /skeptic+ULTRATHINK (high-stakes strategy), /ghost+/punch (cold emails), PERSONA+WORSTCASE (risk assessment), /mirror+/trim (editing your own writing), ARTIFACTS+/shipit (deliverables), /deepthink+/blindspots (pre-decision review), PERSONA+/steelman (testing your contrarian plan), and CONTEXT+L99+/raw (Slack-level answers). Stack 2-3 codes from different categories. Stacking 5+ usually makes things worse.