Cross-platform compatibility: macOS + Windows support

- Replace sqlite3 exercise with curl in Lesson 14 (curl ships on both platforms)
- Rewrite validate-14.sh to check api-response.json using Node.js instead of sqlite3
- Add Windows key bindings (Win+Shift+S, Ctrl+Click) to Lesson 15
- Fix Unix-centric language in Lesson 13 ("Unix tools" → "command-line tools")
- Update graduation bonus challenge #5 to reference curl/GitHub MCP instead of sqlite3
- Update README with cross-platform install instructions and Git Bash prerequisite

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: matthewwilson

README.md

@@ -4,9 +4,20 @@ An interactive, hands-on tutorial for learning Claude Code — built entirely in
 
 ## Prerequisites
 
-- [Claude Code](https://claude.anthropic.com/claude-code) installed (`npm install -g @anthropic-ai/claude-code`)
-- Node.js 18 or later
 - An Anthropic account (authenticated with Claude Code)
+- **Windows only:** [Git for Windows](https://git-scm.com/download/win) (provides Git Bash, which Claude Code requires)
+
+## Install Claude Code
+
+**macOS / Linux:**
+```bash
+curl -fsSL https://claude.ai/install.sh | bash
+```
+
+**Windows (PowerShell):**
+```powershell
+irm https://claude.ai/install.ps1 | iex
+```
 
 ## Getting Started
 

tutorial/lessons/13-headless-mode.md

@@ -18,7 +18,7 @@ Claude processes the prompt, prints the result, and exits. No interactive UI, no
 
 ### Piping input
 
-Combine Claude with standard Unix tools:
+Combine Claude with standard command-line tools:
 
 ```bash
 cat error.log | claude -p "explain this error and suggest a fix" > summary.txt

tutorial/lessons/14-cli-tools-and-mcp.md

@@ -81,20 +81,19 @@ Here's a decision framework:
 
 Let's see Claude use a CLI tool for data work. Ask Claude:
 
-> "Create a SQLite database at `exercises/sample-app/tasks.db` with a `tasks` table matching our Task interface (id, title, priority, completed, createdAt). Insert at least three sample tasks with different priorities. Then query the database to show what's in it."
+> "Use curl to fetch todos from `https://jsonplaceholder.typicode.com/todos?_limit=5`, save the response to `exercises/sample-app/api-response.json`, then analyze the data — how many are completed vs incomplete?"
 
-This demonstrates Claude using `sqlite3` — a non-code-editing CLI tool — to create and populate a real database. Watch how Claude translates the Task interface into SQL and handles the data types.
+This demonstrates Claude using `curl` — a non-code-editing CLI tool — to fetch real API data and work with it. Watch how Claude runs the command, saves the output, and reasons about the JSON response.
 
 ## Hints
 
-- Ask Claude to show you the exact `sqlite3` commands it plans to run before executing them, so you can understand how it maps the Task interface to SQL.
-- If `sqlite3` isn't found, have Claude help you install it or adjust your PATH, then retry the exercise.
-- After Claude creates the database, have it run a `SELECT * FROM tasks;` query to verify that your sample rows were inserted correctly.
+- If you want to see what Claude is doing step by step, ask it to explain each command before running it.
+- `curl` is pre-installed on both macOS and Windows 10+, so this should work on any modern system.
+- After Claude saves the file, have it read back the JSON and summarize what it contains.
 
 ## Completion Criteria
 
-- A SQLite database file exists at `exercises/sample-app/tasks.db`.
-- The database contains a `tasks` table matching the Task interface.
-- The `tasks` table contains at least three rows of data.
+- A JSON file exists at `exercises/sample-app/api-response.json`.
+- The file contains valid JSON with at least one entry.
 
 When you're done, type `/next` to continue.

tutorial/lessons/15-working-with-images.md

@@ -32,14 +32,14 @@ You can include multiple images in a single conversation. For example:
 
 ### Image references
 
-When Claude mentions an image in its response, you can `Cmd+Click` (Mac) or `Ctrl+Click` (Linux) the reference to open it.
+When Claude mentions an image in its response, you can `Ctrl+Click` (Windows/Linux) or `Cmd+Click` (Mac) the reference to open it.
 
 ## Exercise
 
 **Try providing an image to Claude.**
 
 Option A — If you have a screenshot handy:
-- Take a screenshot of anything (`Cmd+Shift+4` on Mac) and paste it with `Ctrl+V` / `Cmd+V`
+- Take a screenshot (`Cmd+Shift+4` on Mac, `Win+Shift+S` on Windows) and paste it with `Ctrl+V` / `Cmd+V`
 - Ask Claude to describe what it sees
 
 Option B — Reference a file path:
@@ -50,7 +50,7 @@ Option C — Just read:
 
 ## Hints
 
-1. The easiest approach: take a screenshot of this terminal right now (`Cmd+Shift+4` on Mac), then paste it into Claude and ask "what do you see?"
+1. The easiest approach: take a screenshot of this terminal right now (`Cmd+Shift+4` on Mac, `Win+Shift+S` on Windows), then paste it into Claude and ask "what do you see?"
 2. Claude can read most common image formats: PNG, JPG, GIF, WebP
 3. This is about knowing the capability exists — you'll use it naturally when you encounter a visual debugging situation
 

tutorial/lessons/16-graduation.md

@@ -46,7 +46,7 @@ Pick a small feature — for example, "sort tasks by priority". Ask me to implem
 
 ### 5. MCP Integration
 
-In Lesson 14 you used `sqlite3` via the CLI to create a database. Now try configuring the [SQLite MCP server](https://github.com/modelcontextprotocol/servers/tree/main/src/sqlite) in `.claude/settings.json` and using it to query the same database. Compare the experience — how does structured tool access differ from raw CLI? When would you prefer one over the other?
+In Lesson 14 you used `curl` via the CLI to fetch API data. Now try configuring the [GitHub MCP server](https://github.com/modelcontextprotocol/servers/tree/main/src/github) in `.claude/settings.json` and using it to list issues or PRs on a repo. Then do the same thing with the `gh` CLI. Compare the experience — how does structured MCP tool access differ from raw CLI? When would you prefer one over the other?
 
 ## Common Frustrations (and What to Do)
 

tutorial/validators/validate-14.sh

@@ -1,34 +1,33 @@
 #!/usr/bin/env bash
 # Validator for Lesson 14: CLI Tools & MCP Servers
-# Checks that tasks.db exists with a tasks table and at least one row.
+# Checks that api-response.json exists with valid JSON content.
 
 set -euo pipefail
 
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
 REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
-DB_FILE="$REPO_ROOT/exercises/sample-app/tasks.db"
+JSON_FILE="$REPO_ROOT/exercises/sample-app/api-response.json"
 
-# Check 1: tasks.db must exist
-if [ ! -f "$DB_FILE" ]; then
-  echo "[LESSON 14] INCOMPLETE: exercises/sample-app/tasks.db does not exist"
+# Check 1: api-response.json must exist
+if [ ! -f "$JSON_FILE" ]; then
+  echo "[LESSON 14] INCOMPLETE: exercises/sample-app/api-response.json does not exist"
   exit 1
 fi
-echo "[LESSON 14] tasks.db found"
+echo "[LESSON 14] api-response.json found"
 
-# Check 2: Must contain a tasks table
-if sqlite3 "$DB_FILE" ".tables" 2>/dev/null | grep -q "tasks"; then
-  echo "[LESSON 14] tasks table found"
-else
-  echo "[LESSON 14] INCOMPLETE: tasks.db does not contain a 'tasks' table"
+# Check 2: Must contain valid JSON (use Node.js — guaranteed available)
+if ! node -e "JSON.parse(require('fs').readFileSync('$JSON_FILE', 'utf8'))" 2>/dev/null; then
+  echo "[LESSON 14] INCOMPLETE: api-response.json does not contain valid JSON"
   exit 1
 fi
+echo "[LESSON 14] valid JSON"
 
-# Check 3: Must have at least one row
-ROW_COUNT=$(sqlite3 "$DB_FILE" "SELECT COUNT(*) FROM tasks;" 2>/dev/null || echo "0")
-if [ "$ROW_COUNT" -ge 3 ]; then
-  echo "[LESSON 14] tasks table has $ROW_COUNT row(s)"
+# Check 3: Must have at least one entry (array with length > 0)
+ENTRY_COUNT=$(node -e "const d = JSON.parse(require('fs').readFileSync('$JSON_FILE', 'utf8')); console.log(Array.isArray(d) ? d.length : 1)" 2>/dev/null || echo "0")
+if [ "$ENTRY_COUNT" -ge 1 ]; then
+  echo "[LESSON 14] JSON contains $ENTRY_COUNT entry/entries"
 else
-  echo "[LESSON 14] INCOMPLETE: tasks table has $ROW_COUNT row(s) — insert at least three sample tasks"
+  echo "[LESSON 14] INCOMPLETE: api-response.json appears to be empty"
   exit 1
 fi