Congratulations - you've made it through all 28 chapters of this series! From the first overview of Claude.ai and Claude Code to a fully built-out recipe planner with search, categories, tests, git history, and team conventions. This final chapter wraps everything up as a cheat sheet you can come back to any time.

The finished project

rezept-planer/
  package.json       Project metadata and npm scripts
  CLAUDE.md          Project rules, shared with the whole team
  server.js          Express server: recipes, search, category filter
  src/
    recipes.js       Storage functions and validation
  data/
    recipes.json     Stored recipes incl. category
  public/
    index.html       Web interface with search and category filter
    app.js           Frontend logic
    style.css        Styling
  tests/
    recipes.test.js  Validation, search, regression test
  .claude/
    settings.json    Hooks (automatic tests after changes)
    commands/        Custom slash commands (e.g. /check-field)

Cheat sheet: the built-in slash commands

• /help — overview of available commands (chapters 3, 16)
• /clear — start a new, empty conversation (chapters 16, 22)
• /compact — deliberately compress the history (chapters 16, 22)
• /model — show/switch the model in use (chapter 16)
• /cost — show usage for the current session (chapters 16, 26)
• /permissions — manage permission settings (chapters 9, 16)
• /agents — show/manage subagents (chapters 16, 19)
• /resume — continue a previous session (chapters 16, 22)
• /init — create a CLAUDE.md draft for the current project (chapters 10, 16)

Cheat sheet: the tools behind the scenes

• Read, Grep, Glob — read-only: opening files, searching for text, finding files by name (chapter 6)
• Edit, Write — write: targeted changes or full rewrites (chapter 7)
• Bash — running commands, with extra care for potentially risky actions (chapter 8)

Cheat sheet: the permission modes

• Default — ask before every action, the safe default (chapter 9)
• Accept edits — automatically accept file changes, for well-understood series of changes (chapter 9)
• Plan mode — plan first, then implement with approval, for larger undertakings (chapters 9, 18)
• Bypass — almost no confirmations, only in tightly controlled, low-risk situations (chapter 9)

Cheat sheet: the golden rules

1. Clear, specific instructions with context and examples (chapter 5).
2. Tackle larger tasks in steps, using plan mode where needed (chapters 12, 18).
3. Describe bugs precisely: expected vs. actual, with reproduction steps (chapter 13).
4. Actually review proposed changes instead of approving them blindly (chapters 4, 27).
5. Write recurring project rules into CLAUDE.md, not just mention them in conversation (chapters 10, 23, 25).
6. Start a new session for new, unrelated topics (chapters 16, 22).
7. Use subagents for scoped research to keep the main session lean (chapter 19).
8. Only set up hooks after testing the command manually first (chapter 21).
9. Save progress regularly in small, well-described commits (chapter 24).

Where to go from here

The recipe planner from this series is deliberately kept small, so every concept could be shown clearly - as a real project there would of course be plenty more to build out: user accounts, a real database instead of the JSON file, deployment to a server, further features like serving-size conversion or shopping lists. Every one of these extensions can be tackled with exactly the same principles you've learned in this series: phrase things clearly, work in steps, plan for larger undertakings, test, commit - and look back at this chapter whenever you need to.

Thank you for working through this series - good luck putting Claude Code to work in your own projects!