3.5 Session 3 wrap-up

Info
⏱ Duration: ~15 min · 🎯 Goal: consolidate what you built, solve the closing quiz and get ready for Week 4 (Design).

Today you stopped waiting on IT: you built your own tool. With Claude Desktop’s Code tab —no terminal, no installs— you turned a KPI CSV into an executive dashboard with traffic lights, reviewing each change in the diff and verifying it in the Browser pane. That’s building with governance.

Recap — what you mastered this week

CapabilityFor what
The three tabs (Chat / Cowork / Code)Knowing when to converse, delegate in the background, or build.
Pre-flight settings (Local, folder, model, Manual)Starting Code with full control over your files.
Diff + Accept/RejectReviewing and approving each change before it touches your folder.
Browser pane + auto-verificationSeeing the result and letting Claude check its own work.
Plan first (Plan mode / planning before acting)Letting Claude propose a plan before touching your files.
CLAUDE.md + clean sessionsPinning project rules and protecting each session’s memory.
The 5 permission modesMoving from Manual to Accept edits/Plan at your own pace.

For next week

Tip
Bridge task (≤15 min): bring a visual idea. Week 4 is Claude Design: from prompt to prototype. Think of a committee-level visual deliverable you’d like to prototype —an “Elektra Rewards 2.0” landing page, a deck, a one-pager— and bring the idea (and any visual references) to the session.

What’s next: from code to design

This week you built a functional tool. In Week 4 you level up on presentation with Claude Design: you describe what you want and get a polished prototype, committee-ready —and you’ll be able to hand off to Claude Code to build what you designed. The circle closes.

Warning
Permanent guardrail: no PII, NDA data, or commercially sensitive information. Only fictitious workshop material.

✅ Checkpoint

You have your working HTML dashboard, open in the Browser pane, with changes accepted via diff. You can explain the three tabs and name the 5 Code permission modes.

Closing quiz — 3 questions

1. What distinguishes the Code tab from the Cowork tab? Code is an interactive assistant with direct access to your local files where you approve each change in real time; Cowork is an autonomous agent working in the background in a sandboxed VM.

2. Why doesn’t Code require installing Node.js or the CLI? Because “the desktop app includes Claude Code”: the desktop app already bundles it, no terminal.

3. What’s the recommended mode progression? Start in Manual to see exactly what Claude does, then move to Accept edits or Plan as you get comfortable.