How memory is selected, how settings and models resolve, how hooks block a bad finish, and how to run agents in parallel. 22 focused lessons, each with an exercise and a quick reference.
A layered CLAUDE.md setup with @include, path-scoped rules and CLAUDE.local.md
A Stop-hook quality gate that blocks completion until tests and lint pass
A UserPromptSubmit hook that prepends branch, date and PR status to every prompt
A TypeScript refactoring agent in .claude/agents/
Layered permission rules that give a team safe defaults
Never lose work to a crash or accidental Ctrl-C again. Master session flags, interrupt recovery, and fork-session for risky experiments.
Layer global, team, project, and personal rules. Use @include, scoped paths frontmatter, and CLAUDE.local.md to give Claude exactly the right context.
Compaction is automatic — but you can steer it. Use /compact with custom instructions and /context to monitor window fullness before hitting the blocking limit.
Claude does not inject all memories — a Sonnet side-query selects up to 5 topic files per turn. Learn exactly how selection works and what it looks at.
The description field is your only selector signal. Write memory entries that reliably surface when you need them and age gracefully over time.
Go beyond basic skills. Use model, effort, paths, context:fork, allowed-tools, and when_to_use to build intelligent auto-triggered skills.
Five config layers, one rule set. Know which file to edit for user defaults, team rules, personal overrides, and security-critical flags.
27 events, 5 hook types, and exit code 2 — the three things you need to know to automate anything Claude Code does.
Use UserPromptSubmit hooks and shell injection to automatically prepend branch, date, PR status, and env state to every prompt.
Use Stop hooks with exit code 2 to prevent Claude from reporting completion until your tests pass, linter is clean, or any custom check succeeds.
Define specialized agents with scoped tools, permission modes, turn limits, and model overrides. Build a TypeScript refactoring specialist in .claude/agents/.
Isolate risky work in a git worktree. Agents with isolation:worktree get their own branch — reviewed before merging, auto-deleted if nothing changed.
Run long tasks without blocking the conversation. Use run_in_background, Ctrl+B mid-execution, and async agents that survive Escape.
Claude becomes a pure dispatcher with 4 tools. Workers do all the implementation. Use it for large parallel tasks that decompose into independent workstreams.
Run named teams of Claude agents with a shared task queue in tmux pane splits. Grant per-worker permission modes and monitor all agents visually.
Five ways to set the model and which wins. The opusplan alias switches automatically. Append [1m] for 1M context. Use CLAUDE_CODE_SUBAGENT_MODEL in CI.
Exact match, prefix, wildcard, tool-wide — build layered permission rules that give your team safe defaults without blocking day-to-day work.
Ask Claude to schedule recurring tasks. Make them durable. Set up autonomous morning CI check-ins and PR reminders that run while you sleep.
Type "ultraplan" anywhere to spawn a remote Opus planning session in your browser. Local terminal returns immediately. Teleport the plan back or run it as a PR.
Voice input, the BUDDY companion, KAIROS channels, and always-on mode. Features your colleagues have never heard of — and how to turn them on.
Hand Claude a repo-scale job. It plans, decomposes, dispatches hundreds of background agents, checkpoints progress, and resumes an interrupted run from saved state. Run /workflows to view runs.
The Faster ↔ Smarter slider. /effort xhigh for hard tasks, low for trivial ones. A direct token-cost lever orthogonal to model — pair low+Haiku, xhigh+Opus 4.8.
One year of access for $20, or subscribe for $45/month to get this course and every other one.
Daily Claude Code use. The course skips installation and basic prompting. If you are new, start with Claude Code Fundamentals.
The 22 lessons are listed at 15 to 25 minutes each, about 7.5 hours in total. Each one ends with an exercise and a quick reference, so you can take them in any order.
No. Swarms are experimental. Dynamic workflows are a research preview. Cron scheduling needs a feature flag. ULTRAPLAN needs claude.ai sign-in and the GitHub app. Each lesson lists its eligibility requirements and how to check them.
Software Factories assumes you know hooks, quality gates and permission rules. It points back to this course's lessons on those topics (T608, T610, T617) and to CLAUDE.md Architecture (T602).