Design
Think before you touch code. FreeYou're the director now
FreeYou've got the team — the first move is telling them exactly what to build.
Ships · The Project Brief KitKnow your team
FreeWhich teammate handles which task, and what each one costs you.
Ships · The Model-PickerSpec before you build
FreeSoonScope it, kill your own feature creep, and define what "done" actually means.
Ships · a scope-cutting promptCreate
Set up the shop, then build. PaidSet up the shop
PaidDev environment, git as a time machine, and secrets handled from minute one.
Ships · a repo-bootstrap kitRead the blueprint
PaidFrontend, backend, database — enough architecture to direct, not to hand-build.
Ships · an architecture cheat-sheetDirect the build
PaidThe build loop — and how to review a pull request you didn't write.
Ships · a pushback promptTests from day one
PaidThe tripwire that catches the junior's mistakes before your users do.
Ships · a test-scaffolding promptDon't reinvent the wheel
PaidStripe, fulfillment, auth, email — the senior instinct is to buy it.
Ships · a buy-vs-build checklistDeploy
Make it live, safely. PaidEnvironments
PaidLocal, staging, production — and where Docker earns its keep.
Ships · an environments kitShip it
PaidDeploy basics, push-to-deploy, and how to roll back when it goes wrong.
Ships · a deploy checklistMaintain
Keep it alive. PaidThe boring middle
PaidDependencies, monitoring, backups — and watching the bill.
Ships · a maintenance checklistKeep the junior in check
PaidOngoing review, technical debt, and knowing when to refactor vs ship.
Ships · a review-cadence kitCapstone
Ship a real one
Run the full loop on your own project, start to deployed — with the whole team behind you.
The lessons that move fastest — model pricing, tooling, the current lineup — get a monthly review, with the volatile bits dated on the page. The roster you read is the roster that's current.