Checkpoint: brief an agent

Time to put the whole course into one brief. In the build-along courses you'll build Klippy, a personal agent on Cloudflare, and a lot of it, the front end especially, you'll build by briefing Claude Code. This is the kind of brief you'll write there.

A brief that works has the same parts every time:

1. Goal. What should exist when it's done, in one or two sentences.

2. Where. The files or folder, and the pattern to follow.

3. Docs. Which source to check for anything version-sensitive (Context7 for library docs; a skill like Remix's or Cloudflare's if it's installed).

4. Out of scope. What not to touch, and no new packages unless asked.

5. Done means. A check that passes or fails, and the output as proof.

6. Plan first. Reply with the plan before editing.

What it leaves out matters too. The house rules (pnpm, never edit generated files) are already in CLAUDE.md, so the brief doesn't repeat them, and anything that must never happen is a hook or a deny rule, not a sentence.

Checkpoint. Klippy saves notes. Brief an agent to add a notes page to the web app at apps/web: a list of the person's saved notes, newest first, that reads them from the agent's existing listNotes method. Use the Remix skill and check current docs with Context7. Include all six parts. Claude replies with the plan it would follow.

Finish this checkpoint and the Agent wrangler badge is yours. You can say what a coding agent does, keep a lean CLAUDE.md, brief changes that are small and proven, and add skills, MCP servers, subagents and hooks. Next, Your first Worker starts the Klippy build-along, and in Build the front end with agents you'll write briefs like this one for real.