Session 5 Companion · Your Capstone · Keep this open. Refer back anytime.
Claude always knows where you are. These three phrases get you back on track instantly:
| Command | What you're doing | ~Time |
|---|---|---|
| /introduction | You made it — the whole series is done 💖 Resources + how to stay connected | ~3 min |
| /refresher | The greatest hits from every week, with a quick "how" for each | ~4 min |
| /capstone-instructions | The rules of your build — read these before you start | ~5 min |
| /final-project | Your 90 minutes: plan → build → iterate (twice), then ship & present | ~90 min |
| /conclusion | Your certificate, your portfolio, and what's next | ~3 min |
Unzip your workshop-5-capstone folder, then launch Claude Code inside that folder — that's where today's commands live. Then your instructor will call each command in order. You can work in the terminal or in VS Code, whichever you prefer.
Mac: right-click the folder → "New Terminal at Folder." Windows: right-click inside the folder → "Open in Terminal." Then type:
claude
Or cd into the folder first, then run claude. Drag the folder into the terminal after cd to auto-fill the path.
File → Open Folder → your workshop-5-capstone folder. Open the Claude panel (the spark icon), then type /introduction.
VS Code has a built-in terminal (Ctrl + backtick) — you never need a second window.
You don't need a CLAUDE.md yet — you'll create one for your project during /final-project, right after your plan is approved. That's a habit worth keeping for every project from now on.
Your project needs at least two of these five. You already know how to do every one — here's the one-liner for each.
| Thing | What it is | How to add it |
|---|---|---|
| API | One program asking another to do something. | Sign up (e.g. fal.ai for audio/images), grab your key, ask me to use it — you paste the key into the file, never the chat. |
| Agent | A helper with one job and its own instructions. | Ask me: "make me an agent that [does the thing]." |
| Skill | A saved set of instructions for something you do often. | Ask me: "create a skill for [task]." |
| Plugin | An installable bundle (skills, tools, even MCPs together). | Add with /plugin from a marketplace, or just ask me to set it up. |
| MCP | A one-line install that gives me a new ability (e.g. Playwright = eyes in a browser). | Tell me the ability you want; I'll hand you the one line to paste in your terminal. |
| Save your context | Type /context to check how full I am. Around 40%+: ask me to "summarize what we've built and add decisions to my CLAUDE.md," then type /clear, and I re-read it. Write it down → clear → carry on. Your files are safe. |
| Pick your model | Type /model. Opus for complex, heavy thinking · Sonnet for lighter work and to stretch Pro-plan usage (lean on agents too) · Fable for stubborn bugs. |
| Mind your mode | Plan (think first) · Edit-with-permissions (I ask before each step — your default today) · Auto (I just go). Don't get stuck in auto by accident. |
| Debug with Fable | Hit a bug you can't shake? Switch to Fable (/model), ask it to look over your code and catch bugs. You approve every change. |
| What's happening | Fix |
|---|---|
The slash commands (/introduction, etc.) don't show up | Claude Code isn't in the right folder. Launch it inside your unzipped workshop-5-capstone folder (or open that folder in VS Code), then try again. |
| Claude feels forgetful or confused mid-build | Type /context. Over ~40%? Ask it to summarize what you've built into your CLAUDE.md, then /clear and it re-reads. Your files are safe — only the conversation resets. |
| A bug you can't shake | Switch to Fable (/model) and ask it to look over your code and catch bugs. Read what it finds and approve each change yourself. |
| Running low on usage (Pro plan) | Switch to Sonnet (/model) and lean on agents for the heavy lifting to stretch it further. |
| Deploy trouble on Vercel | Connect your GitHub repo to Vercel — same flow as your Workshop 2 game. Ask Claude for the exact steps for your project. |
| Claude asks for an API key | Never paste a key into the chat. Put it in the file yourself. If you already pasted one, delete that message and rotate the key. |
| Word | Plain English |
|---|---|
| API | One program asking another to do something (e.g. generate audio). |
| Agent | A helper with one job and its own instructions. |
| Skill | Saved instructions Claude uses for a task you repeat. |
| Plugin | A bundle of skills, commands, and MCPs installed together. |
| MCP | A one-line install that gives Claude a new ability. |
| Gauntlet Loop | Builders plus separate critics, run until the work is genuinely good. |
| Plan mode | Claude thinks and proposes but can't touch files. Toggle with Shift+Tab. |
| CLAUDE.md | Your project's memory file — Claude reads it first every time. |
| Context window | How much of your conversation Claude can hold. Check with /context. |
| Deploy / Vercel | Putting your app live on the internet at a real link. |
| GitHub | Cloud storage for your code — a folder in the sky that saves every version. |
| Resources | buildbeautifully.lovable.app/event-resources |
| Certificate | build-beautifully-certification.vercel.app |
| Website | buildbeautifully.lovable.app |
| @build_beautifully_1 | |
| Build Beautifully | |
| Invite a friend | tally.so/r/b56GAL |
Your certificate is real and shareable — deploy your app, submit the link, pass the test, and put it on your LinkedIn. You earned it. 💖