ServicesCoding agent tools
Claude Code training on your own code and tickets
Hands-on workshops in your repositories, built around tasks from your backlog, remote or on site in Germany and Poland, in English, German or Polish.
What the exercises train
- 1
Cutting a task to size
A scope the agent can complete and a reviewer can check
- 2
Choosing what context to give
The files, commands and conventions the task depends on
- 3
Deciding when to take over
Noticing a stuck session, then starting again or finishing by hand
- 4
Checking before the merge
Running the tests and reading through every change the agent made
Exercises based on common problems
Most problems with coding agents have one of three causes: the task is too large to review, the agent is missing context, or a change is merged without proper checks. We build the exercises around these causes and run them on your code.
Why the setup comes first
Training starts once the repository instructions and permissions exist, or runs while they are being written. In a repository with no build commands or approval rules, a workshop would teach people to work around the gaps, so we close them first.
The content changes from team to team. Engineers about to start with coding agents get different exercises from those for whom agents are already routine.
The parts of Claude Code we cover
Each exercise is a task taken from your backlog. We pick from the topics below to suit the team.
- Writing CLAUDE.md files: your actual build and test commands, plus the conventions reviewers check for
- Plan mode for changes across several modules, with someone reading the plan before any file is edited
- Permission rules that set what Claude Code may do freely, what it must ask about and what is blocked
- Subagents and Skills for repeated tasks, stored in the repository and looked after by an owner
- Hooks, so that your checks run on their own after every agent edit
- Unattended runs of Claude Code, and what has to be in place before them
Formats and length
You can book a single workshop for one team and one repository, or a series of shorter sessions that follows the rollout as it grows. A follow-up a few weeks later works through the questions your projects have raised in the meantime.
We set the length and group size with you in advance, to fit the team and the repository.
Where and in which language
We train online or at your offices in Germany or Poland, for example in Munich, Berlin, Cologne, Düsseldorf, Warsaw or Kraków. We teach in English, German or Polish.
For an on-site session, engineers need no more access than on an ordinary working day. Everyone uses their own computer and repositories, and nothing needs to be transferred to us.
What you take away
- Exercises and notes from each session
- Your repository instructions, with any changes we make to them together
How we measure the training
- The number of engineers in each team who still use Claude Code after a month
- Rework on pull requests the agent opens, before and after the training
- The tasks your teams now give to Claude Code, compared with the ones they still do themselves
Questions
Is there a certificate at the end?
No. The focus is practical work in your code, so we neither issue certificates nor prepare people for external exams.
Can we book the training on its own?
Yes, provided the setup is already there. Before we start, we look at the repository, because the exercises go better when the agent can run its build and tests.
Is there an open course we can join?
No. Each workshop is for a single team, in that team's repositories, and there is no public schedule.
Which languages do you train in?
Polish, German or English. The choice is the same for online and in-person sessions.
Related services
Claude Code consulting and rollout
Claude Code fitted to your codebase, permissions and review process, starting with one pilot team.
Coding agent adoption
Agents taken from a few pilot teams to the rest of engineering, with training and one shared setup.
Harness engineering
The setup that tells an agent how to build, test and change your code, kept in version control.
From the blog
Claude Code team instructions
How a team assigns owners to CLAUDE.md files and rules, reviews them, and retires entries that no longer change what Claude Code does.
Spec-driven development
How to write specs coding agents can follow, take one change from spec to merge, and choose between Spec Kit, OpenSpec, BMad, GSD and Kiro.
Talk to an engineer
Bring one piece of work you would like to improve. The call takes 30 minutes and needs no access to your systems or your data.
Booking runs on Google Calendar.
Prefer to write first? Leave your email and a few lines, and we reply with times.
Look for the draft in your email program
Send it from there, and an engineer replies in person with times for a 30-minute call. If no draft has opened, write to us at miki@cloudsail.com.