In one hour, you'll actually know how to use Claude Code.

• It writes confident code that doesn't fit your codebase

  Because it never saw the file where you already solved that. Feeding it the right context is a skill, and it is the single biggest difference between people who love this tool and people who uninstall it.

• It goes off and changes twelve files

  You asked for one thing and got a refactor. There is a way to keep it on a short leash without micromanaging every line, and it takes about five minutes to set up.

• You're still copy-pasting into a chat window

  If your workflow is paste code, read answer, paste back, you are using a fraction of it. The whole point is that it reads and edits the files itself.

• The docs list a hundred features and no order

  Skills, MCP, hooks, subagents, slash commands, permission modes, scheduled tasks. All real, all useful, and no indication of which four actually matter on day one.

• It costs more than you expected

  Token spend creeps up because nobody tells you which habits are expensive. It's easy to end up paying two or three times over for exactly the same output.

• Nobody at work can tell you either

  It's too new. There's no colleague two desks over who has already worked it out, so everyone is guessing from the same YouTube videos.

None of this is fixed by reading more. It's fixed by someone sitting with you for an hour on your own work, saying “stop, do it this way instead” — and by walking away with a CLAUDE.md and a workflow that were built for what you actually do.

• ✗Treated it like autocomplete

  For weeks I pasted snippets in and pasted answers back, which is the slowest possible way to use a tool that can read and edit the whole project itself.

• ✗Explained my conventions again every single session

  All of it belonged in a CLAUDE.md and a couple of skills. I retyped the same paragraph for a month before I worked that out.

• ✗Let context pile up until quality quietly dropped

  A long session gets worse and more expensive at the same time. I blamed the model for a while. It was me not clearing.

• ✗Burned tokens on work that didn't need them

  Feeding it far more than the job required, on tasks that never warranted it. The fix is a handful of habits and they cost nothing to adopt.

• ✗Accepted diffs I hadn't really read

  Vibe coding is genuinely fast until the day it isn't, and then you're debugging code nobody in the room has ever read. There's a line, and I found it the hard way.

• ✗Ignored parallel work, loops and scheduling for far too long

  I sat and watched one agent work, one task at a time, while three more could have been running and an overnight job could have done the rest.

Every one of those cost me weeks, or money, or both. In the session I hand them over as habits you start with, which is the whole reason an hour with someone beats a month of figuring it out yourself.

• Developers

  You already ship code. The gap is workflow: how to hand off a whole task instead of a snippet, how to keep it inside your conventions, and how to review its work fast enough that it's still a net win.

  Ship the boring 60% of a ticket in minutes

• Engineering leads

  You need to tell a team how to use this without them all inventing their own habits. We set up a shared CLAUDE.md, agree what it should and shouldn't touch, and talk through the review discipline that keeps quality up.

  One workflow your whole team can copy

• Designers & PMs

  Read the codebase without asking an engineer. Make the small copy or spacing change yourself. Turn a messy doc into a proper spec, and prototype the thing instead of describing it.

  Fewer tickets you have to file and wait on

• Analysts & ops

  Point it at a folder of CSVs and ask questions in English. Automate the report you rebuild every Monday. Clean, reshape and cross-check data without learning pandas first.

  An afternoon of spreadsheet work, done before coffee

• Writers & researchers

  It edits files on disk, which means your drafts, notes and research folders are all fair game. Restructure a long document, chase inconsistencies across a dozen files, keep a real archive searchable.

  Work across a whole project, not one document

• Founders & solo operators

  You are the whole team. Build the internal tool nobody has time for, understand the code you paid someone else to write, and stop being blocked on a contractor for two-line changes.

  Unblock yourself on the small stuff

If you can use a browser and you're willing to type into a terminal for an hour, you're qualified. Tell me your role when you book and I'll build the hour around it.

Something not covered here? Ask it in the booking notes, or message me on Cal.com before you pay.