Learning Paths
Pick one path. Each is a page: who, prerequisites, ordered modules with rationale, exercises on your own codebase, a capstone, and an expected outcome. Do not read the whole site linearly.
Choose a path
| Path | Who | Outcome |
|---|---|---|
| Senior Engineer | ICs shipping features with agents daily | Spec → implement → verify loop you trust |
| CTO | Technical leaders setting org policy | Operating model, gates, and rollout plan |
| Solo Founder | Founders building product mostly alone | MVP shipped without architecture collapse |
| Engineering Manager | Managers of teams adopting agents | Team norms, review load, quality bar |
| Staff Engineer | Staff/principals owning system integrity | Architecture control under agent throughput |
| Multi-Tool | Teams on Claude Code + Cursor/Codex/etc. | One instruction surface across tools |
| Legacy Modernization | Engineers refactoring brownfield systems | Safe strangler / refactor with agents |
| Production Hardening | Teams taking agent-built code to prod | Verification, gates, and readiness |
| Multi-Agent Mastery | Leads coordinating parallel agents | Split, integrate, and recover without chaos |
If you only have an afternoon: Start Here → Mental Models → your role path's first three modules.
Related
- Start Here — orientation and operating model
- Glossary — shared vocabulary
- Playbooks — procedures once you know the model
- Failure Catalog — what to recognize early
- Templates — artifacts the paths ask you to fill