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
Automated QA and Testing with AI: A New Era for Software Testing
antirez describes using LLM agents for automated QA by writing a markdown file that instructs the agent to perform manual testing on new releases. Applied to DwarfStar and Redis Arrays, this approach raises software quality without compromising on thoroughness.
Config Rollback Watchdog Gateway: Combine Health Checks with Automatic Rollback
A Reddit user proposes a watchdog that restarts the OpenClaw gateway on port failure, combined with automatic config rollback after 5 failed starts to prevent configuration-induced boot loops.
100K Lines of Rust with AI: Contracts, Spec-Driven Dev, and Performance
Cheng Huang built a Rust multi-Paxos engine with AI agents, achieving 300K ops/sec. Key techniques: AI-written code contracts, lightweight spec-driven development, and aggressive optimization.
How to Stop Hitting Claude Limits: Treat Each Session Like a Token Budget
User shares how they fixed daily Claude limits by stopping message bloat — scope the task, load only relevant context, clear after each session. Includes practical workflow & infographic.