Practise Claude Code where mistakes are free.
23 hands-on Lessons in your browser. Claude here is simulated, so you need no Claude account and nothing to install, and every wrong turn shows its real consequence.
Lesson 1 takes about 20 minutes, with no sign-up.
Make parseConfig in src/config.js reject an empty file with a clear error message, and add a test for it.
- readsrc/config.js
- readtest/config.test.js
- rungrep -rn "parseConfig" src test
- readsrc/cli.js
-
Claude
parseConfighands the text straight toJSON.parse, so an emptylinkcheck.jsonfails with a bareSyntaxErrorthat never names the file. Its one caller,src/cli.js, prints config errors and exits with code 2, andtest/config.test.jshas no case for an empty file yet. -
Reject an empty linkcheck.json
- In
src/config.js, makeparseConfigthrowConfig file is emptywhen the text is only whitespace, before it reachesJSON.parse. - In
src/cli.js, print a hint after that error, so the reader knows what to write. - In
test/config.test.js, add a test that an empty file is rejected.
- In
export function parseConfig(text) {+ if (!text.trim()) {+ throw new Error('Config file is empty');+ } const raw = JSON.parse(text);
console.error(`linkcheck: ${error.message}`);+ console.error('Hint: write a JSON object in linkcheck.json.'); process.exit(2);
Not in your request
test('the file must hold an object', () => { assert.throws(() => parseConfig('[]'), /must hold a JSON object/); });++test('an empty file is rejected', () => {+ assert.throws(() => parseConfig(' \n'), /empty/);+});
Make the error say "linkcheck.json is empty", and keep the change to src/config.js and test/config.test.js.
The error now names the file and says what to write, and the change stays in src/config.js and its test, so src/cli.js is left alone.
Reject an empty linkcheck.json
- In
src/config.js, makeparseConfigthrowlinkcheck.json is empty: write a JSON object, such as {}when the text is only whitespace, before it reachesJSON.parse. - In
test/config.test.js, add a test that an empty file is rejected with that message.
This is Lesson 2. You asked Claude for one small change, with plan mode on.
Would you approve this plan?
You approved an edit nobody asked for.
Item 2 of the plan changed src/cli.js, a file your request never named, and approving let that edit through.
That's the skill Lesson 2 teaches.
You read the plan before approving it. The revised plan leaves src/cli.js alone, and nothing was edited while you decided.
This was Lesson 2, free with an account.
Why practise here
Real consequences
Your mode, your permission rules and your hook scripts decide what happens, so a wrong choice plays out as it would for real.
Real tools in this tab
bash, git, node and npm run on a virtual disk in your browser, and what they print is their own output.
The guide's own Checks
Each Lesson ends with the Check the guide itself uses, run on your files, and a Badge when it passes.
The journey
Beginner
6 Lessons
- Install, sign in and look around
- Choose who approves what: permission modes and plan mode
- Your first change, from request to commit
- Keep a session on track
- Project memory with CLAUDE.md
- Beginner capstone: fix a reported bug, from plan to commit
Intermediate
9 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
- Intermediate capstone: get a repository ready for a new teammate
Advanced
8 Lessons
- Parallel sessions with worktrees
- Choose an orchestration pattern
- Run and save a dynamic workflow
- Script Claude Code with
claude -p - GitHub Actions
- Share your setup with a team
- Put bounds on autonomous runs
- Advanced capstone: add CI review your team can share
Lesson 1 needs no account. The other 5 Beginner Lessons are free with an account. Intermediate and Advanced come with the full course.
Lesson 1 takes about 20 minutes, with no sign-up.