Claude Code team runs dozens of Claudes in parallel: 7 verification rules, starting with E2E tests
minchoi · x · 2026-11-19
minchoi distills the Claude Code team's methodology: 90% of their code is written and reviewed by Claude, nobody reads every diff, and verification does the work—enabling dozens of parallel Claude instances. Rule 1: if you invest in only one kind of test, make it end-to-end over real user flows (add to cart, checkout, confirmation), since unit tests can pass while the feature is broken.
Related event: Claude Code Team Says 90% of Its Code Is Written and Reviewed by Claude(4 posts)→
More from coding & agent
- From $180 first gig to $20k AI installs: two pricing plays for selling AI to mid-size firms — aryanXmahajan · 2026-11-19
- Claude Code verification rules: differential tests, REVIEW.md isolation, and mined rules — minchoi · 2026-11-19
- Claude Code rules: 3 failed fixes then a human, and checks a change can't edit — minchoi · 2026-11-19
- Property tests for invariants: throw thousands of generated inputs at rules that must never break — minchoi · 2026-11-19
- Give Claude a way to run the change, not just the tests: verify skill in .claude/skills/ — minchoi · 2026-11-19
- Claude Code team says Claude writes and reviews ~90% of their code, aided by 7 verification rules — minchoi · 2026-11-19