Developers
R999once
Four hands-on modules inside a simulated Claude Code.
- Developers track · 4 modules, hands-on
- Progress saved, certificate on completion
- Lifetime access and every update
- 14-day refund, one email
Track 01Developers
Claude Code course for developers.Stop prompting. Start engineering.
Most developers use Claude like a faster autocomplete. This track teaches the operating model by making you drive it: in a simulated Claude Code you open a repo, write skills that fire, dispatch subagents, add hooks and wire an MCP server, step by step, with nothing to break.
Who it is for
- Engineers already using Claude Code who feel they only touch 20% of it
- Tech leads deciding how a team should adopt agents without chaos
- Solo builders who want to ship products faster with fewer regressions
- Anyone who has written a prompt file and wondered why it keeps drifting
By the end
You will be able to
- Write skills that Claude picks up reliably, with tests that prove it
- Design subagent workflows for review, research and refactors
- Wire MCP servers so Claude can act on your real systems safely
- Set up hooks, permissions and worktrees for hands-off runs
- Debug agent failures with a repeatable method instead of vibes
Developers
What you will work with
The same building blocks Anthropic documents for Claude Code, taught in the order they actually matter. You do each one yourself in the simulator before you touch your own repo.
- 01
CLAUDE.md and memory
The operating manual Claude reads first. What belongs there, what belongs in the repo, and how to keep it from drifting.
- 02
Claude skills (SKILL.md)
How to create custom Claude skills that trigger when they should, with evals that prove it. The core of the course.
- 03
Subagents and agent workflows
Fan-out research, review gates, adversarial verification, and deterministic orchestration for unattended runs.
- 04
Hooks and permissions
Guardrails the model cannot skip: pre-commit checks, formatting, and permission modes for hands-off sessions.
- 05
MCP servers
Give Claude tools on your real systems. Design tool schemas an LLM can use, build a server, and debug what it actually sent.
- 06
Worktrees and plugins
Isolated workspaces for parallel agents, and packaging skills as plugins your whole team installs.
Curriculum
4 modules. Every one hands-on.
01Claude Code fundamentalsOpen the Code panel, point it at a repo, give it a task and review the diff before anything lands.
- Open the Code tab, pick a Local environment and a folder
- Read CLAUDE.md and understand why it is the first file Claude reads
- Give a task and watch the read, plan, edit loop in the transcript
- Review a proposed change in Manual mode and approve it
- Switch between Manual, Accept edits, Plan and Auto and see what changes
02Skills that stickWrite a skill, watch it fail to trigger, fix the description and watch it fire.
- Create a SKILL.md from the + menu next to the prompt
- See why a vague description means the skill never runs
- Rewrite the description with the exact phrases people use
- Trigger the skill with a normal request and accept its output
03Agents, subagents and workflowsFan work out to subagents, read their findings, then add a hook Claude cannot skip.
- Dispatch two reviewers in parallel from one request
- Open the Tasks pane and read what each agent found
- Turn findings into a fix and accept it
- Add a pre-commit hook so tests always run before a commit
04MCP and tool integrationAdd an MCP server, see its tools appear, and use one inside a task.
- Open Add connectors from the + menu
- Add a custom connector (any MCP server) by URL
- See the tools it exposes without writing any code
- Run a task that calls a tool and turns the result into work
Both tracksBest value
R1,800once
All eleven modules. For people who build tools and run the work.
- Developers track · 4 modules, hands-on
- Non-Developers track · 7 modules, hands-on
- Progress saved, certificate on completion
- Lifetime access and every update
- 14-day refund, one email
Questions
Questions developers ask
What is the difference between Claude skills, MCP and subagents?
Skills are instructions: how to do a task. MCP servers are tools: what Claude can reach, such as your database or an internal API. Subagents are workers: separate Claude sessions you dispatch for parallel or isolated work. Most real workflows use all three, and the Developers track teaches when each one is the right choice.
How do I create a custom Claude skill (SKILL.md)?
You write a SKILL.md file with a name, a description that tells Claude when to use it, and the procedure. The hard part is the description: most skills never trigger because it is vague. Module 2 of the Developers track covers this in depth, with evals that prove your skill fires when it should.
What does "hands-on in a simulator" mean?
The course runs inside a working replica of the Claude desktop app, in your browser. A guide tells you what to click or type, you do it, and the app responds the way the real one does. Nothing is real behind it, so you cannot break anything or spend anything, and every learner gets the same path. When you open the real app afterwards, you already know where everything is.
Do I need a Claude Pro or Max subscription to take this course?
The Developers track uses Claude Code, which needs a Claude Pro or Max plan or API access. The Non-Developers track works on any paid claude.ai plan, including Pro. The course price does not include a Claude subscription.
How long does it take to learn Claude Code or finish a track?
Each module is a 15 to 30 minute guided session inside the simulator. Most people finish a track in one afternoon and come back to replay the modules they use most.
How quickly will this Claude course go out of date?
Claude changes monthly, so the simulator and modules are revised as it does and you get every update for free, forever. Your progress carries over.
All questions on the pricing page. Something else? Email Ethan directly.