Claude Code guide in three levels, Beginner to Advanced: hands-on lessons with checked exercises, every volatile fact cited to its source. Independent community guide.
Intermediate
Intermediate · about 4 hours · Verified against Claude Code v2.1.292 (stable) on 2026-10-15
One developer's setup. You shape Claude Code to your own project: skills, project memory, model and effort, permissions and the sandbox, hooks, subagents, MCP servers and plugins.
You're ready for this level if you can
- Install Claude Code, start it safely in a repository, tell which model and account a session uses, and check its answers against the code.
- Choose a permission mode for a task, decide when a change needs a plan, and approve only a plan you would merge.
- Take one change from request to commit: explore, plan, implement, test, review the diff, correct, commit.
- Stop or rewind a wrong turn, and choose between clear, compact and resume.
- Create a short, true project CLAUDE.md and show that a new session follows it.
Practice
Practice in your own repository: shaping Claude Code to your project is the point of this level. Run each check from your copy of the practice template as npm run check -- <lesson-id> --dir <your repo>. If you'd rather not change your own repository, use the template copy itself; the capstone runs there.
To go step by step, run npm run learn in your copy and use Claude Code in a second terminal beside it. The app takes you through every lesson and the capstone, one step at a time, asks which folder you practice in, and checks your work as you go. Each page below teaches the same lesson on its own.
A copy you made for the Beginner level may not have the Intermediate checks or lessons: npm run check then lists no i- lessons. Bring them in from the template, in your copy:
git fetch https://github.com/wesammustafa/claude-code-practice main
git checkout FETCH_HEAD -- checks capstone learn
git commit -m "Add the Intermediate checks and lessons"
A copy older than the app has no learn script, so npm run learn says Missing script: "learn": run node learn/app.mjs instead.
Prepare your own repository
Lessons save the files their checks read in a .practice/ folder, in the repository you practice in. Before your first lesson in one of your own repositories, create that folder there and tell git to ignore it without a commit (gitignore):
mkdir -p .practice
echo '.practice/' >> "$(git rev-parse --git-path info/exclude)"
Windows: New-Item -ItemType Directory -Force .practice and Add-Content (git rev-parse --git-path info/exclude) '.practice/'.
Your copy of the practice template already ignores .practice/ in its .gitignore, so it needs neither command.
When to use what
Seven of the ways to extend Claude Code, each with the sign that you need it; Extend Claude Code lists the rest. Each links its lesson.
- Project memory: Claude gets a convention or command wrong twice. Add it to
CLAUDE.md, or to a rule in.claude/rules/scoped to the files it applies to (How Claude remembers your project; lesson: Organize project memory and see what loaded). - Skills: you give Claude the same instructions or workflow again and again. A project skill lives in
.claude/skills/<name>/SKILL.md(Extend Claude with skills; lesson: Turn a repeated workflow into a skill). - Hooks: something must happen every time at a set point in a session, such as before a tool runs, whatever Claude decides. Hooks are defined in a settings file such as
.claude/settings.json(Hooks; lesson: Enforce a rule with a hook). - Subagents: a side task should run in its own context window and report back. A project subagent lives in
.claude/agents/(Create custom subagents; lesson: Delegate to a custom subagent). - Dynamic workflows: the job needs more agents than one conversation can coordinate. A saved project workflow lives in
.claude/workflows/(Workflows; lesson: Run and save a dynamic workflow). - MCP servers: Claude needs tools or data outside your files, such as a browser, a database or an API. A project-scope server is listed in
.mcp.jsonat the project root (Connect Claude Code to tools via MCP; lesson: Connect a tool with MCP). - Code intelligence: Claude reads many files to find where a symbol is defined or used. A code intelligence plugin gives it a language server instead (Code intelligence plugins; lesson: Install and manage plugins).
Permissions decide what Claude may do in all of these, and the sandbox limits what its shell commands can reach (Permissions, settings scopes and the sandbox). Model and effort tune any of them (Pick the model and effort).
They combine: a plugin packages skills, agents, hooks and MCP servers so they install as one unit (Install and manage plugins).
Lessons
- Turn a repeated workflow into a skill
- Organize project memory and see what loaded
- Pick the model and effort
- Permissions, settings scopes and the sandbox
- Enforce a rule with a hook
- Delegate to a custom subagent
- Connect a tool with MCP
- Install and manage plugins
Each lesson takes 20 to 25 minutes.
Capstone
Get a repository ready for a new teammate: turn a team lead's brief into setup a teammate gets from git, choosing the mechanism for each need, then fix a real bug with it.
By the end of this level you can
- Write a project skill that runs by name and loads on its own when it applies.
- Write a hook that enforces a rule, and show it firing.
- Delegate to a custom subagent with limited tools.
- Add an MCP server at project scope, and install a plugin from an Anthropic marketplace.
- Put permission rules in the right scope, turn on the sandbox, and pick the model and effort for a task.
- Organize project memory, and find out what loaded when an instruction isn't followed.
Electives
Optional lessons beside the core path:
- Skill patterns: live data, supporting files and a context of its own.
- Claude in Chrome: verify UI changes in your own browser.
- The status line: show the model, the folder and the context in a bar of your own.
- Fast mode: faster Opus answers, paid for beyond your plan.
Official companions
- Claude Code in action: Claude Academy's course on running long, hands-off sessions you can trust.
- Introduction to agent skills and Introduction to subagents: Claude Academy's courses on skills and subagents.
Next level
Advanced: beyond one session.
Sources: Extend Claude Code · How Claude remembers your project · Extend Claude with skills · Hooks · Create custom subagents · Workflows · Connect Claude Code to tools via MCP · Plugins · Code intelligence plugins · Configure the sandboxed Bash tool · gitignore · Claude Code in action · Introduction to agent skills · Introduction to subagents