The Fundamentals, Made Faster to Practice

Module 2 covered scoping context to what's load-bearing for a task. In practice, that means clearing the conversation with /clear when starting a genuinely new, unrelated topic, and using /compact to summarize a long session on the same topic instead of letting it run indefinitely.

Module 1 established naming real files and symptoms. @ autocompletes a real file path directly instead of typing it out in full, and a pasted screenshot is often faster and more precise than describing a visual layout bug in words.

A long task can run in the background while you keep working, as covered in Module 5. For two genuinely independent tasks on the same repo, separate git worktrees give each Claude Code session its own isolated files, avoiding uncommitted-change conflicts between them.

Bonus: Tips & Tricks. You've built the whole loop on Fixly, module by module. This closing lesson is a practical grab-bag: the everyday shortcuts and habits that make real Claude Code sessions faster, once the fundamentals from Modules 1-5 are already second nature.

Context Hygiene: /clear and /compact. After shipping the export feature, starting the security review as a brand-new topic in the same session keeps carrying export-feature detail that's no longer relevant. /clear wipes the conversation and starts fresh; /compact summarizes what's happened so far to free up room without losing the thread entirely. Same discipline as Module 2's context engineering, just as a session habit.

You just finished the export feature and are about to start an unrelated task: auditing Fixly's auth code. Should you use /clear or /compact before starting?

• →/clear -- the auth audit is a genuinely new, unrelated topic, so a fresh context avoids diluting it with leftover export-feature detail (the same context rot risk from Module 2).
• →/compact -- because it's always better to keep every prior detail available, just summarized.

Point at Things Faster: @files and Pasted Images. Module 1 taught naming real files in your prompt. @ does that with autocomplete: typing @src/exp jumps straight to src/export.js instead of typing the full path. And for a real UI bug, pasting a screenshot directly into the prompt is often faster and more precise than describing what's visually wrong.

Pick the Fastest Way to Point at This Bug. Decide which pointing technique fits a real Fixly report, applying the same 'name something real' discipline from Module 1.

Running More Than One Thing at Once. A long-running task (like a broad refactor) doesn't have to block everything else -- running it in the background frees you to keep working, and you check back on it later, the same discipline from Module 5's lesson on background runs. For two genuinely independent tasks on the same repo, separate git worktrees let you run two Claude Code sessions in parallel without them stepping on each other's uncommitted changes.

Why use two separate git worktrees for two independent Claude Code sessions, instead of running both in the same working directory?

• →Two sessions editing the same working directory at once could overwrite or conflict with each other's uncommitted changes -- separate worktrees give each one its own isolated files.
• →Claude Code physically cannot run more than one session in the same directory, ever.

That's the Toolkit. None of these tricks replace the discipline from Modules 1-5 -- they just make it faster to practice: clean context, precise pointing, and running independent work in parallel without stepping on yourself. That's the full Claude Code Masterclass, end to end.