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
Essential Custom Instructions for Claude to Prevent Common Annoyances
A Reddit user shares three specific custom instructions to address common Claude annoyances: requiring warnings before destructive commands, preventing mid-answer plan changes, and keeping code blocks exclusively for functional code.
Claude's Data Sources: When to Request Web Searches for Current Information
Claude sometimes relies on internal training data instead of performing web searches, which may provide outdated information. Users can request web searches specifically to get more current results.
Multi-model routing reduces OpenClaw API costs by 50%
A developer cut OpenClaw API costs by 50% by routing different tasks through different models: Claude for complex reasoning, DeepSeek for file operations and test generation, and Gemini or GPT for mid-range tasks.
Save on Claude Code Bills by Routing Planning Tokens to Cheaper Models
A user cut $40 in overage fees by splitting Claude Code workflows: planning steps go to Haiku 3.5, actual edits and decisions stay on Opus/Sonnet. A 30-line wrapper handles routing; setup took ~2 hours.