Claude Code can read a project, edit files, and run commands. That makes the useful skills practical ones: describing a small change, reviewing what changed, and proving it works. Evan demonstrates each step on his screen, then guides you through the same step on your own project.
Sessions are built around three kinds of learners: individuals practicing on their own projects, nontechnical builders who need to direct and verify changes, and development teams building a shared review routine.
Anthropic's overview currently describes Claude Code as a tool that reads your project, edits files, and runs commands. It is available in the terminal, in code editors (IDEs), in a desktop app, and on the web. Most surfaces require a Claude subscription or a Console account, and the desktop app requires a paid subscription.
Those details change, so read the official Claude Code overview before you choose a surface. Whether you can use a given surface depends on your own account, plan, and organization settings.
Prerequisites
Because Claude Code can change files and run commands, a session only works well when these are settled first.
An approved, safe projectA practice project, a sanitized copy, or a repository your organization has approved for this use. No credentials or customer records.
Account and access permissionA working Claude account for the surface you will use, and permission from whoever controls the account and the code.
Runtime and environment for your surfaceThe terminal, editor, desktop app, or browser setup that surface expects, plus whatever the project needs to run. Confirm this before the session starts.
A way to undo changesVersion control or a backup, so any change can be reviewed and reversed.
Seven steps, three kinds of practice
Every learner works through the same loop: understand, define, direct, inspect, debug, test, hand off. The exercise at each step changes with who is in the room.
1. Understand the project
Individuals
Open a small personal or practice project and ask Claude Code to explain what it does, where the entry point is, and how to run it. Check each statement against the files yourself.
Nontechnical builders
Use a copy of a simple site or tool you already own. Ask for a plain-language map of the pages, data, and settings, then mark anything you cannot confirm.
Development teams
Pick one module in an approved repository. Have Claude Code summarize its responsibilities and dependencies, then compare that summary with the people who maintain it.
2. Define one small change
Individuals
Write a one-sentence change, such as adding a field to a form or renaming a label, with a note on what must stay the same.
Nontechnical builders
Describe a change a visitor would notice, such as clearer button text or a new line in a table. Add what done looks like in terms you can check in a browser.
Development teams
Turn a small ticket into acceptance criteria, the files likely involved, and the behavior that must not change. Keep it small enough to review in one sitting.
3. Direct the work
Individuals
Give Claude Code the change, the constraints, and the command that proves it works. Ask it to explain its plan before it edits files.
Nontechnical builders
Ask for the plan in plain language first. Approve it, request changes, or stop. Decide in advance which actions need your permission.
Development teams
Agree on how the team phrases a task, which commands may run, and where work happens, for example a branch or a worktree, so changes stay isolated.
4. Inspect the diff
Individuals
Read every changed line. Ask why each file was touched and remove edits that are not part of the request.
Nontechnical builders
Ask Claude Code to describe each change as what a visitor would see. Flag anything you do not understand and ask for a simpler explanation or a smaller change.
Development teams
Review the diff as you would a colleague's pull request: scope, naming, side effects, secrets, and unrelated formatting changes.
5. Debug what breaks
Individuals
Introduce or find a small failure. Give Claude Code the exact error and the steps to reproduce it, and ask for a cause before a fix.
Nontechnical builders
Copy the visible error message or describe what you saw on screen. Ask for likely causes in order, and check the first one before accepting a change.
Development teams
Share a failing test or log excerpt that contains no private data. Compare the proposed cause with what the team knows about the system.
6. Write meaningful tests
Individuals
Ask for a test that fails without the change and passes with it. Reject tests that only repeat the code.
Nontechnical builders
Write a short checklist of behaviors, such as submitting a valid form and an invalid form, and ask Claude Code to turn it into automated checks or a manual test script.
Development teams
Cover the boundaries that matter: invalid input, permissions, empty data, and the path the change touches. Decide what is tested automatically and what is checked by hand.
7. Verified handoff
Individuals
Write a short note: what changed, how you checked it, what you did not check, and how to undo it.
Nontechnical builders
Hand the change to whoever owns the site with the same four points, plus the exact page and steps to see it work.
Development teams
Open a reviewable change with the test results, known gaps, and rollback notes. Record the checks run against the published or staged version, not only a local preview.
What you leave with
A small change you directed, reviewed, and tested yourself.
A way to phrase a task so the result is easy to check.
A diff review habit and a short handoff note you can reuse.
A list of what to verify before anything is published.
What it does not do
A session teaches a working method. It does not guarantee tool access, certify code as secure or correct, or replace review by the people responsible for a production system. Building a finished product is separate work you can scope on the hire Evan page.
Standard session formats for Claude Code
Two published sessions, both live on screen share with Evan Weber. Pick the length that matches how much work you want to cover.
1-hour session
$300 USD
Standard offer: 1 to 4 people
Best for one priority workflow. Bring a single task, approved sample inputs, and a clear idea of what a useful result looks like.
4-hour session
$1,000 USD
Standard offer: up to 8 people
Room for several workflows or more practice with each one. The time is shared across the group, so agree on priorities before booking.
Live screen-share work with Evan on your own priority task
Approved sample inputs and account access ready before the session starts
Evan demonstrates on his screen, then guides you through the same steps on your work
Software subscriptions and usage costs are separate from the session fee.
You're welcome to record the session with agreed permissions, and you own that recording. Confirm any trainer-provided recording, follow-up materials or support before booking.
An approved, safe project or a copy you are allowed to change, permission to use the tool with that project, and a working account for the Claude surface you plan to use. You also need whatever runtime and environment that surface expects, for example a terminal or code editor setup. Confirm these before the session so working time goes to the exercise.
Does Claude Code require a particular subscription?
Anthropic's overview says most surfaces require a Claude subscription or a Console account, and the desktop app requires a paid subscription. Plans and requirements change, so check the official overview for the surface you will use. Access depends on your own account and organization settings, and nothing on this page guarantees it.
Is this only for professional developers?
No, but the exercises differ. Individuals can practice on small projects, nontechnical builders can learn to direct, inspect, and verify changes without writing code by hand, and development teams can practice a review and testing routine on an approved repository. A tool can edit files and run commands, so everyone needs to understand what they are approving.
Can I bring my company's private repository?
Only if your organization approves it. A safe default is a practice project, a sanitized copy, or a small internal tool that holds no customer records or credentials. Never send passwords, keys, or confidential data through this website.
How is this different from the other training pages?
This page covers Claude Code specifically. The broader AI coding training page compares tools, the Codex page covers OpenAI's Codex, and the Replit page covers building and publishing in Replit. Pick the one that matches the tool you will use.
What does it cost?
The standard sessions are $300 USD for 1 hour and $1,000 USD for 4 hours. Larger groups, implementation, and development work are custom quotes. Software subscriptions are separate.