Back to feed
Dev.to
Dev.to
7/7/2026
The 12 tools I use to pilot Claude Code in production: kept, dropped, contested

The 12 tools I use to pilot Claude Code in production: kept, dropped, contested

Short summary

Author documents 12 production tools refined across 60 days managing a 118,000-line ERP with Claude Code: CLAUDE.md conventions, persistent memory systems, project rules, skills for forced protocols, and bash hooks for deployment safety. Each tool is retained/dropped/contested based on empirical ROI. Falsify-before-fix and deploy-safeguard patterns demonstrate 6-18x incident response improvement and prevent secrets leakage.

  • •Twelve production tools systematically refined and evaluated for ROI over 60 days of real ERP deployment
  • •Falsify-before-fix protocol and deploy-safeguard hooks reduce incident response time 6-18x
  • •Memory systems, rules documentation, and drift probes mature from ad-hoc practice to documented doctrine

Generated with AI, which can make mistakes.

#ai-tools#ai-agents
Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

60 days with Claude Code on a production ERP: the honest balance (no hype, raw numbers)
Dev.to
3 Claude Code habits that were quietly costing me (and the fixes I actually run)
Dev.to
Lessons from running 12 companies' software built with Claude Code: verification habits over agent quality
Dev.to
Claude Code hooks are the seatbelt nobody buckles — here's the 10-hook setup that makes agent disasters impossible
Dev.to