409: James Phoenix — Claude Code Masterclass

What It Covers

James Phoenix shares advanced Claude Code optimization techniques, spending $3,400 monthly on 2.3 billion tokens. He covers hierarchical rule systems, parallelized testing architecture, git work trees, and transitioning from coder to engineering manager.

Key Questions Answered

• •Hierarchical Claude.md Files: Place global rules in root Claude.md but create localized Claude.md files in subdirectories for package-specific patterns. This prevents context rot from excessive input tokens while maintaining relevant rules at appropriate application layers without degrading model performance.
• •Testing Parallelization Architecture: Eliminate seed data from SQL files entirely. Use factory functions to generate dynamic test data at runtime, prefix users with branch names, and create custom Postgres schemas per test. This enables true database isolation for parallel test execution across multiple agents.
• •Code Review Timing: Push back on Claude Code mistakes immediately during the active session rather than later. Finding the specific session ID afterward requires searching through histories with dash dash resume. Real-time correction prevents merging poor quality code that becomes harder to trace after multiple commits.
• •Mutative vs Additive Code Risk: Additive features that don't touch existing files pose minimal risk and can be deleted easily. Modificative code that updates dependencies, service layers, or existing infrastructure creates dangerous technical debt. Use separate git work trees for risky refactors to isolate potential failures.