Skip to content
Module
Module 5 of 5Lesson 3 of 3~10 min

Exit kit and application plan

After a course, good practices fade quickly if nothing anchors them in the team's daily work. This lesson gives you the essentials of the course in a reusable form and helps you plan how to apply them to your repository in the weeks that follow, so your way of working with Claude Code lasts.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will have the course's templates, prompts and checklists (CLAUDE.md, settings, hook, subagent, review checklist) and you will have planned how to apply them to your repository over 7 and 30 days.

Topics covered

  • Claude Code kit
  • CLAUDE.md templates
  • application plan
  • AI coding agent
  • best practices

Where it fits

Review, automate and deliver your set-up

How do I know the agent's work is good before it ships, and install the whole set-up on my repository?

Lessons in this module

  1. Review the agent's work, then automate it
  2. Workshop: your way of working on your repository
  3. Exit kit and application plan (this lesson)

What you will learn in this module

This lesson is part of the course Work with Claude Code on a real project: context, planning, review

  • Explain what fills Claude Code's context window and manage it (/context, /clear, /compact, resuming and naming sessions), taking cost into account.
  • Write a short, useful CLAUDE.md placed at the right level of the hierarchy (user, project, local, subdirectory, path-scoped rules), with imports if needed.
  • Run a task on existing code as explore, plan, code, commit, with plan mode, verification criteria and Git rather than checkpoints alone.
  • Choose and justify the right mechanism for a need (CLAUDE.md, skill or command, subagent, MCP server, hook) and set it up in the repository.
  • Choose a permission mode and write allow, ask and deny rules suited to the project's risks, in the right settings file.
  • Write simple hooks as deterministic guardrails (block, format, verify) and know their risks and limits.
  • Review the agent's work with a checklist (scope, tests, secrets, migrations, dependencies) and an independent review, and know when to automate it in non-interactive mode or in GitHub Actions.

Related courses