After 3 months of A/B testing 160 Claude prompt codes: the boring takeaways
Samarth, creator of clskillshub.com, spent three months A/B testing 160 Claude prompt codes using a controlled test rig (same task batteries, fresh contexts, blind-rated outputs). The key findings:
1. Most prompt codes are placebo
Codes like ULTRATHINK, GODMODE, ALPHA, and UNCENSORED showed zero measurable shift in reasoning, length, or quality against a no-prefix baseline. The verbose Claude output is mistaken for improvement.
2. Only ~7 codes consistently shift reasoning
L99(the hedge-killer) — still the workhorse, sharper on Sonnet 4.6/Opus 4.7/skeptic— forces premise-challenging; pairs with L99 for code review/blindspots— surfaces unconsidered checks (e.g., CI-vs-local case-sensitive path bug)/decompose— fuzzy task breakdownOODA— only works on time-pressured decisions, breaks on open-ended strategyARTIFACTS— fading because newer Claude versions structure outputs by default
3. Stacking 3+ codes confuses the model
As of 2026, the model partial-honors one code and ignores the others. Stick to 2-code stacks max. Samarth's daily driver: L99 + /skeptic.
4. Prompt codes rot — retest required
Model updates shift behavior. Codes that worked in October 2025 are not the same set today. If a source says "tested in 2025" and was never updated, treat it as historical.
5. Skills files > prompt codes for Claude Code
Auto-activating skill files in ~/.claude/skills/ provide domain context via YAML descriptions without re-prompting. Prompt codes force a reasoning mode; skills files give context. Different problems, different solutions.
Samarth used Claude Code to build the test harness, classification code, and frontend — and ships skill files for his own stack. The free library includes 100 prompt codes, 40-page Claude guide, and 1,545 community-attributed skill files (MIT/Apache, full attribution): clskillshub.com/prompts, clskillshub.com/guide, clskillshub.com/free. Paid tiers exist but are not required to use anything below.
For developers using Claude Code daily, the actionable takeaway: drop the hype prompt codes, test your own, and invest in skill files for context.
📖 Read the full source: r/ClaudeAI
👀 See Also
![[Update] You Asked for a Secure, 'Always-On' Way to Run OpenClaw Without the VPS Headache. We Built It. Waitlist is Open.](/covers/article-139.jpg?v=3)
[Update] You Asked for a Secure, 'Always-On' Way to Run OpenClaw Without the VPS Headache. We Built It. Waitlist is Open.
OpenClaw announces a new feature that allows users to run their platform securely and continuously without the complexities of VPS. The waitlist is now open for early access.
Token Master: Architecture Concept to Save 30-70% on AI Agent Costs
A detailed architectural approach to intelligent multi-model routing that can dramatically reduce token consumption.
Claude Prompt Codes Retested: L99 Sharper, OODA Narrower, ARTIFACTS Faded, and 3 New Codes to Use
A 6-month retest of L99, OODA, and ARTIFACTS prompt codes on Claude shows L99 sharper on Sonnet 4.6/Opus 4.7, OODA failing on strategic prompts, ARTIFACTS unnecessary for code, and three new codes (/skeptic, /blindspots, /decompose) earning daily use. Stack no more than 2 codes.
Yes Flow/No Flow: A Simple Technique to Reduce Context Hallucination in AI Coding Sessions
A Reddit user shares the Yes Flow/No Flow technique for maintaining consistency in AI conversations by rewriting prompts instead of stacking corrections, which helps reduce context breakdown and hallucination during long coding sessions.