for your team
Engineering
You already know how to code. This is the part that's new — handing real work to an agent that reads the whole repo, writes the tests, and shows you the diff before anything lands.
playbooks
Full worked systems, not one-off prompts — each walks the whole workflow end to end. Pick one and follow it.
Map a codebase you've never seen
Point Claude at an unfamiliar repo and get a grounded tour — the real modules, how a request flows, and where the scary parts live — in plain English, naming files that exist.
open the playbook →Trace a bug to its root cause and prove the fix
Hand Claude the full stack trace and the failing input, get a ranked list of likely causes with file:line pointers, then a fix plus a test that fails on the old code and passes on the new.
open the playbook →Backfill the tests you never wrote
Take a module with no tests, have Claude list the behaviours worth pinning down — including the nasty edge cases — and write a suite that covers them, flagging any latent bugs it finds on the way.
open the playbook →Refactor safely behind a green suite
Clean up a gnarly file without changing behaviour — using the test suite as your seatbelt, running it before and after so you can prove nothing broke instead of hoping.
open the playbook →Run a wide, boring migration without breaking things
The repo-wide change you've been dreading — swap a library, rename an API, bump a pattern across 80 files — done in one sweep, with a clear list of the cases it couldn't convert one-to-one for you to decide by hand.
open the playbook →Onboard onto a strange codebase and ship your first fix
The full arc — week one on a repo you've never seen, a bug in production, the author long gone — to a reviewed, tested fix you understand. The big one that ties every other engineering playbook together.
open the playbook →