Learn with Goover - Make Claude Code Yours

​Most people use Claude Code as a smarter autocomplete. I want to show you how to turn it into a tool that is configured to your project, enforces your rules, and doesn't quietly burn through your plan limits.

​Bring a laptop and a real repository. You will leave with at least three things installed and working.

​What Skills we'll build together:

1. ​A setup command: Every project needs Claude to know the same handful of things. We'll build a single command that scaffolds it, and cover the part almost everyone gets wrong: the difference between telling Claude a rule and actually enforcing one.

2. ​A council command: One model gives you one opinion, but we'll wire up several independent perspectives that run in parallel and then argue with each other for the decisions where being confidently wrong is expensive.

3. ​A simple-vault: Every conversation starts from zero, so most people re-explain their project every morning. We'll build a simple knowledge base that loads itself at the start of every session, survives clearing the conversation, and lives in your repo where your teammates can read it. No Obsidian, no database, no tooling. Just folders and files.

​Costs and Best Usage Practices

​A section on where tokens actually go, using published numbers, and the handful of habits that make the biggest difference. Including two that surprise most people: why clearing a session is free but compacting one isn't, and the invisible charge waiting for you when you come back from lunch.

​Who's This For?

​Anyone who has used Claude Code at least once and suspects they're using maybe a fifth of it. Engineers, founders, PMs. You do not need to be a strong programmer, but you should be somewhat comfortable in a terminal.

​Before you arrive (please do this, it takes 5 minutes)

1. ​Install Claude Code: npm install -g @anthropic-ai/claude-code

2. ​Run claude once and sign in. Confirm it works: claude --version

3. ​Have a real code repository on your laptop, ideally one you know well. If your setup breaks, come anyway and pair with someone. We'll have a repo ready to go.

​Lunch provided. Doors 11:30, we start at 11:35.