Day 1 — The Claude Code Track

Summary — what this page covers The landing page for Day 1. It sets the goal for the day, shows the full schedule, explains the BookTracker through-line, and tells participants how to use these docs. Keep this short and motivating — it's the first thing attendees read.

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.

Day at a glance

Time	Session	Format
9:00 – 10:30 AM	Section 1: Foundations + Claude Code CLI	Lecture + Demo + Lab
10:30 – 10:45 AM	Morning Break	—
10:45 AM – 12:30 PM	Section 2: Steering Claude Code — CLAUDE.md, Rules, Skills, Subagents & Hooks	Lecture + Demo + Lab
12:30 – 1:30 PM	Lunch (Lab 2 continues, self-paced)	—
1:30 – 3:15 PM	Section 3: IDE Integration + MCP Ecosystem	Lecture + Demo + Lab
3:15 – 3:30 PM	Afternoon Break	—
3:30 – 5:00 PM	Section 4: AI in the SDLC	Lecture + Demo + Lab

What you'll be able to do (learning outcomes)

By the end of Day 1, you will be able to:

Outcome	Where it's delivered
Install, configure, and operate Claude Code from the terminal, VS Code, and JetBrains (Rider/IntelliJ)	Before You Begin · Section 1 (terminal) · Section 3 (VS Code + JetBrains) · Command Reference
Use Claude Code to accelerate architecture design, code construction, refactoring, testing, and debugging	Section 2 (construction via skills/rules) · Section 4 (architecture · refactoring · testing · debugging) · Lab 4
Explain how LLMs work — tokens, context windows, turns, grounding — and apply that to practical integration decisions	Section 1 (mechanics → decisions) · Section 2 (context economics → where instructions live)

The through-line: BookTracker

[Write 2–3 sentences: every section builds on one evolving ASP.NET Core API — BookTracker. Attendees clone it once and improve it across all four labs. Link to the BookTracker page.]

How to use these docs

• Before You Begin — confirm your plan and tools before 9:00 AM.
• Each Section page has the concepts, demos, and key takeaways.
• Each Lab page is the hands-on exercise with a committed deliverable.
• The Steering Reference Card and Command Reference are keepers — print them.