This series has covered many individual principles - time to look at the most common beginner mistakes together, with a direct pointer to which chapter already explained the matching solution.

Mistake 1: too-vague prompts

"Make this better" or "Add a search" (chapter 12) leaves too much open. The solution is in chapter 5: clear instructions, giving context, concrete examples. A vague prompt almost always leads to a result that doesn't quite match what you had in mind - meaning more rework, not less effort.

Mistake 2: too big a task at once

Making a request like "Build me the complete category feature including migration, validation, form, and tests" in one single step, without checking in between, can work - but if something goes wrong, it's unclear which of the many affected spots caused it. Chapter 12 shows the step-by-step approach, chapter 18 shows plan mode for exactly this kind of larger undertaking - together, they're the solution.

Mistake 3: missing context

A bug report like "The search doesn't work" (chapter 13), instead of a concrete description with expected and actual behaviour, forces Claude Code to first figure out what's actually wrong itself - time that a better description could have saved.

Mistake 4: blind trust without review

Approving proposed changes without checking them, just because it's faster, undermines exactly the safety layer described in chapters 8 and 9. Especially for commands run through the Bash tool or larger file changes, it's always worth a brief, critical look before approving - Claude Code is usually right, but "usually" is no substitute for checking it yourself.

Mistake 5: choosing the wrong permission mode for the situation

Using bypass mode from chapter 9 out of pure convenience in an important project is a risk that's rarely worth the time saved. Default mode is almost always the right starting point, especially for anything with real consequences.

Mistake 6: piling everything into one endless session

Starting a new, unrelated topic in the same, already very long session as the previous topic, instead of starting fresh with /clear from chapter 16, unnecessarily speeds up hitting the full context window situation from chapter 22 - with all the downsides that come with a compaction.

Mistake 7: never writing down project rules

Explaining the same rule again in every new session, instead of writing it into CLAUDE.md from chapter 10 once, costs more time in the long run than properly capturing the rule once - and it also makes it easy to forget, especially when several people work on the same project (chapter 25).