Our stack has evolved a lot over the past year. Here's exactly what we use, why, and how it fits together across a typical project.
Code: Cursor + Claude
Cursor is our primary editor, with Claude handling complex reasoning tasks. Engineers spend more time on architecture decisions and less time typing boilerplate.
Testing: Coverage Where It Counts
We target coverage on data transformations, payment logic, and auth — not an arbitrary percentage across the whole codebase.
Code Review: Automated Pre-Review
Before a human reviews a PR, automated checks catch security issues, performance regressions, and style violations — cutting review time significantly.
Documentation: Kept Current Automatically
API docs and deployment guides are generated from the codebase wherever possible, so they don't quietly go stale six months after launch.
The Meta-Point
The tools matter less than the discipline. Every task starts with: 'does this serve the client's actual goal?' The stack just makes the answer easier to act on.