Builds behavior in vertical red-green-refactor slices, keeping feedback tight and tests focused on outcomes.

Applies a structured security, performance, correctness, and maintainability lens to every change.

Turns requirements into explicit components, contracts, data models, reliability choices, and honest trade-offs.

Designs the right mix of unit, integration, contract, E2E, and operational tests instead of chasing coverage blindly.

Creates an independent reviewer with precise context, catching important mistakes before they compound.

Makes fresh evidence, not confidence, the prerequisite for declaring a fix or feature complete.

Provides a practical behavior-preserving playbook for removing code smells through small, test-backed changes.