A look back across the week
Briefing well is the last of the friction. Before you close the course, look back at the week - because the shape of the arc is the actual lesson, and it’s a deliberately different shape than the one this course’s siblings walk.
The arc, in one breath
Section titled “The arc, in one breath”You started with a repo you didn’t write. budgetcli came to you as a friend’s weekend project - lightly documented, holding the promise of your own money but not yet trustworthy enough to do it. Over the chapters you turned it into something you’d actually run.
You installed Cursor - the VS Code you already knew, with AI bolted on - and shipped a first reviewed change, the CSV date-parse fix, so you’d seen one full turn of the loop before anything was at stake. You learned the modes and the judgment behind Ask, Agent, and custom Plan or Debug postures. You picked models with intent - Auto for the everyday, a stronger model where the categorisation engine’s design actually paid for the reasoning. You steered context - letting self-gathering retrieval find what it needed and @-pinning only to correct a miss. When Cursor kept reintroducing the float-money bug and the wrong taxonomy, you stopped re-explaining and wrote it down once in rules. You set the blast radius - the sandbox as the load-bearing control, with allow/deny rules treated as policy rather than guarantees. You fanned work across parallel worktrees and pushed async work onto a Cloud Agent, three flavours of more-than-one-agent that are not the same primitive in three hats. And in this last chapter you smoothed all of it into reflex - posture by instinct, model by habit, surface by task shape, briefs tight enough that runs go where you meant.
Where it mirrored the spine, and where it diverged
Section titled “Where it mirrored the spine, and where it diverged”This course rides the same teach-by-doing spine as its siblings - one inherited repo, one week, each primitive introduced exactly when the work demands it - and budgetcli is the same project the Codex course runs on, on purpose, so you can read the two side by side and see the primitive underneath the tool’s spelling of it. Rules are rules whether they’re AGENTS.md or .cursor/rules/*.mdc. A read-only exploration posture is the same discipline whether it’s Cursor’s Ask mode or Codex’s read-only profile. Brief the agent the same four ways in either. Learn the discipline once and you carry it across all of them.
Where Cursor diverged from that spine is worth naming, because it’s the reason this course was written at all. The other tools in this family are terminal-first; Cursor is a GUI editor that grew a CLI, and that inverts the arc. You started in an editor - Tab completions and an Agent sidebar, the most interactive surface there is - and the week moved outward toward autonomy: from watching every diff, to fanning parallel agents across worktrees, to handing a Cloud Agent a branch you’d review when you got back. The editor-first → agents → headless progression is Cursor’s own, and the two-pool cost model, the self-gathering context, the split-model planning, and the four-surface choice are moves a terminal-first tool simply doesn’t have to make. The discipline mirrored the spine; the surface of it was Cursor’s alone.
The whole job
Section titled “The whole job”Strip away the tool and every chapter taught one thing. AI coding agents are extraordinary at the general - broad, fast, fluent across languages - and blind to the particular: they don’t know your codebase, your conventions, your domain, or that on budgetcli money is integer cents and never a float. You are the inverse - slower, narrower, but you know all of that cold. Every move in this course was a way to hand the agent the context it was missing: rules that persist it, skills that package it, modes that bound it, briefs that aim it.
That’s the discipline. Not a keystroke, not a clever command - closing the gap between what you know and what the agent knows, on purpose, every time. By now none of the moves should feel like steps. That’s the whole goal of a workflow chapter: to make the deliberate automatic. The reflexes are yours, worn in by your own week of corrections on a repo you’ve turned from someone else’s weekend project into a service you trust with your own money. Now go close the gap somewhere it matters.
For the spec-level other half - the exhaustive “what is this primitive and every option it takes” view this story stayed deliberately light on - see the per-tool reference pages and Cursor’s own docs at cursor.com/docs. This course taught you the practice; that’s the reference.