Context and harness engineering with Claude Code and Codex
In a training repository, scope an agent’s work, verify a fix and have a colleague rerun your checks.
Early bird
€700€1,000Standard price
per person
10 places per session
Product, design and operations roles
Become a Product Builder
Start with a business need and build a first tool with AI.
What you’ll take awayA prototype, a user test scenario and criteria for deciding what to do next.
Small business owners · No coding required
Everyday AI for small business owners
Use Claude Cowork to draft a quote, write a follow-up email and summarise documents from a practice case.
What you’ll take awayA reusable quote template and a checklist of the amounts and terms to review before sending.
How the advanced course works
Start with a real task
We choose a task from your team’s work and agree on the result everyone should be able to check.
Practise with checks
You scope the agent’s work, trigger a failure and review the proposed fix.
Repeat on a different task
You apply the method to another task, then hand your instructions and checks to a colleague.
Proposed workshop exercise
The test passes for the wrong reason
Expose the false positive
The test should verify that an invalid email is rejected. Because it accepts any error, a database timeout is enough to make it pass.
Review the agent’s proposed fix
The agent spots the permissive test, but its fix treats every case the same way. Specify the expected error and keep a valid case that must still pass.
Rerun against the version under review
Make the test fail on the wrong behaviour, verify that the valid case passes, and record results against the version you are reviewing.
5 ways to demonstrate your progress
I share my practice with experienced developers and technical leads who can read a repository, review a diff and diagnose a failing test. Together we choose a representative task and agree on what participants should be able to repeat.
01
Scope
You write a task with acceptance criteria and explicit limits on what the agent can do.
02
Verify
You check the result against the requirements and keep checks your team can rerun.
03
Explain
You explain your technical choices, the trade-offs and what remains uncertain.
04
Fix
You reproduce a failure, identify its cause and rerun the check after the fix.
05
Hand over
A colleague picks up the scenario using your configuration and notes. You record what they still need to proceed.
What your team can do on its own On a different task, scope the agent’s work, rerun the checks and explain the result. The handover is tested when a colleague picks up the case with the team’s instructions and notes.
I run training sessions and work with teams over time as they apply what they learn.
SME
Workshop on configuring Claude Code
10 participants
An interface review agent built with a developer, then added to the team’s shared plugin.
See the work involved
During the workshop
We looked at how a repository’s rules can guide code review. I also built an agent live with a developer to help them assess interfaces from screenshots.
Between sessions
A developer installed the shared configuration on several repositories. At the follow-up, they showed which commands Claude Code could not find, giving us a concrete issue to investigate.
Deliverable
The UI Designer agent we built during the workshop was added to the team’s shared Claude Code plugin.
Startup
Bootcamp on AI-assisted development
25 participants
Demonstrations, role-based workshops and exercises on team repositories, with a configuration memo for the backend team.
See the work involved
During the sessions
Across 4 days of training, I combined live demos with workshops by role. On day 1, I showed how adding project instructions changed the result of the same request.
Between training days
The exercises used the teams’ own repositories, including writing and testing Claude Code’s project instructions. At a later session, the backend team asked how to separate rules for reading code from rules for editing it.
Deliverable
I sent the backend team a configuration memo with an example file structure for separating shared instructions from rules specific to parts of the codebase.
Explore my work
Claude Code cheat sheet
Keep essential commands, shortcuts and settings close at hand during exercises.
Examples and prompts for working with documents, choosing access permissions and checking results. A resource for colleagues who do not write software.
Tell me about your team and a situation you want to work on. I’ll get back to you to discuss the need and choose a suitable format.
Contact me
Tell me about your team
Frequently asked questions
Do I already need to know Claude Code or Codex?
The advanced course assumes you can navigate a codebase, read a diff and diagnose a failing test. We agree on preparation based on your experience with agents.
What is the difference between team training and an open session?
For your team, I adapt the exercises to your tasks, tools and experience. Open sessions follow the advertised programme, and you can ask for the exact dates.