Curriculum
The full curriculum, hour by hour.
Nothing is held back for an upsell. This is the entire two days, written out, so you can decide before you pay rather than after.
Every program covers the same stack
- Claude CodeAgentic work in the terminal
- CoworkClaude across your daily surfaces
- Skills & MCPTeach Claude your tools
- Agent SDKProgrammatic agents
- Managed AgentsHosted, always-on
- The APIDirect model access
Outcomes
You leave running these.
Judge the curriculum by what still works a week later, not by how many topics it lists.
A Claude setup that matches how you actually work
Project instructions, memory, connectors, and a daily brief wired to your real accounts. Not a sandbox you abandon on Monday.
Something shipped, in the room
You leave day two with working software you built during the session, on your own repo, not a tutorial clone.
A credential tied to work, not attendance
The assessment asks you to build. Passing means you demonstrated the skill, which is the only kind of certificate worth showing anyone.
Day one
The Operator Day
Everything here applies to work you already do. No programming, no sandbox project.
Context is the whole game
- Why the same prompt gets wildly different results
- Project instructions that actually change behavior
- Memory: what to store, what to let go
Claude across your surfaces
- Connectors into the tools you already use daily
- Documents, spreadsheets, and inboxes as working material
- A daily brief that assembles before you sit down
Skills and MCP
- Teaching Claude your tools instead of describing them each time
- When a skill beats a longer prompt
- Build one live, against your own workflow
Day two
The Builder Day
You pick something from your own backlog. It gets built in the room, with help the moment you stall.
Claude Code on a real repository
- Setting up so the agent understands your codebase
- The instruction file, and what belongs in it
- Working in small verified loops instead of one big ask
Agents that run unattended
- The Agent SDK, and when it beats the chat surface
- Hosted agents and what they cost to run
- Guardrails, because unattended means unwatched
Ship it
- Debugging live, the part docs cannot teach
- Deploying what you built during the session
- What to do first on Monday
Before the cohort
A short portal gets everyone to the same starting line.
About an hour, self-guided, sent a week ahead. Accounts created, tools installed, one small warm-up build. It exists so day one is not spent watching twenty people run installers.
Dates
Live cohorts, real seats.
Every cohort is capped at 20 people. No countdown timers here, just the actual count.
September Cohort
Sep 15 – Sep 16, 2026
October Cohort
Oct 13 – Oct 14, 2026
November Cohort
Nov 10 – Nov 11, 2026
Now you know exactly what you are buying.
Two days, six blocks, applied to your own work throughout.
Next cohort: Sep 15 – Sep 16, 2026 · 4 of 20 seats left