SERIES

Claude Code

Ten lessons on Claude Code. Plan the work, give it the real file and the real error, and keep a person on the checks.

Slash commands change. If the product and a lesson disagree, the in-product list wins. Product claims were checked against the Claude Code documentation in October 2026. Official Claude Code documentation.

  1. 01 An agent is a model, tools, and a loop Claude Code keeps going after the first answer. A model decides, tools act, and the result comes back until the job is done or the run gets stuck. 3 min read
  2. 02 You manage. The agent builds. Claude writes quickly. The result follows the brief and the review. Say what done is, what must not change, and show one real example. 3 min read
  3. 03 Plan before you build For a change with more than one reasonable design, have Claude write the approach and wait. Approving a plan is cheaper than undoing the wrong edit. 3 min read
  4. 04 Give it the real file, the real error, and an example Point at the file, paste the full error, and show one example to copy. A paraphrase drops the line that mattered. 3 min read
  5. 05 A short project memory file CLAUDE.md is the short handbook a session reads at the start. Build, test, conventions, gotchas. No secrets, and no second copy that disagrees. 3 min read
  6. 06 Skills and commands you can reuse A skill is a saved procedure Claude loads when the description matches. Write it from your own workflow, and read every line before you rely on it. 3 min read
  7. 07 Parallel work and connected tools Give each parallel job its own branch or worktree. A connected tool server is real access. Add one only when you will actually use it. 3 min read
  8. 08 Permissions, checks, and a small eval set Keep access tight, make Claude run the tests, and keep ten to twenty real tasks. Judge a change in a fresh session, with evidence. 4 min read
  9. 09 From a thin slice to production Get one path working end to end before you widen it. Production needs a trace, data you trust, and a person on the irreversible step. 3 min read
  10. 10 A starter workflow for this week Define done, let Claude interview you, approve a plan, build one thin slice, and keep the change only if a fresh review agrees. 3 min read

Talk with an engineer