See all tags.
Day goal: participants leave Day 1 using Claude Code as a genuine daily driver — not a novelty, but a force multiplier they'll open first thing tomorrow morning.
Work through this page before the workshop starts. It takes 15–20 minutes if your machine is clean. The room has a TA for install friction at 8:30 AM, but plan to arrive with the readiness check already green — we open Section 1 by writing code, not by installing tools.
Summary — what this page covers A short tour of the app every lab builds on. Describe what BookTracker is, its four-project structure, the stack, and the fact that its CLAUDE.md starts minimal so attendees configure it themselves in Lab 1.
9:00 – 10:30 AM · 90 min — 40 min lecture/demo + 50 min lab
Duration: 50 min · Deliverable: functioning Claude Code session + committed CLAUDE.md
10:45 AM – 12:30 PM · 105 min — 50 min lecture/demo + 55 min lab
Duration: 55 min · Deliverable: a .claude/ directory (rules + skill folder + guardrail hook + plugin manifest), committed
.claude/
1:30 – 3:15 PM · 105 min — 40 min lecture/demo + 65 min lab
Duration: 65 min · Deliverable: a GitHub MCP session that queried the repo and created an issue
3:30 – 5:00 PM · 90 min — 30 min lecture/demo + 60 min lab
Duration: 60 min · Deliverable: working Reading Progress feature with tests, committed
The one page worth keeping.
Summary — what this page covers A quick-reference of how to install and operate Claude Code across all three surfaces (terminal, VS Code, JetBrains) plus the CLI and in-session slash commands used across Day 1.
Summary — what this page covers Quick answers to the questions that come up every time. Carry over the existing Day 1 FAQ and add the new steering-era ones. Keep answers to a few sentences.
