Skip to content
Hands-on, on your own codebase

Double what your engineers ship with AI agents.

I train your engineers on your own repositories to hand whole tickets to Claude Code, Cursor, Codex or Copilot. Same headcount, more shipped.

  • 1 to 4 days
  • On site or remote
  • English or German
Find your tool's course
Illustration: the same three engineers merge more pull requests once they work with AI agents, so output rises and the headcount stays flat.

Companies and training providers I have worked with

I deliver AI training for organisations and L&D providers.

Cegos Integrata

Cegos Integrata

Commissioned trainer for Cegos Integrata

NobleProg

NobleProg

AI coding workshops via an IT training provider active in 50+ countries

Innomotics

Innomotics

In-house AI training for engineering teams

financial.com

financial.com

In-house Cursor training for the engineering team

Digitality Agency

Digitality Agency

Training for the design team in using LLMs for coding work

Bots & People

Bots & People

Commissioned trainer for developer workshops

Code First Girls

Code First Girls

Course creator: a 3-month curriculum on AI and agentic tools

Nomad Summit

Nomad Summit

Conference speaker on AI tools, agentic development and developer workflows (2025)

Vertiv

Vertiv

On-site workshops in AI-assisted coding for engineering teams

Deutsche Telekom

Deutsche Telekom

Hands-on AI coding training for enterprise engineering teams

Your engineers have AI licences and mostly use them as autocomplete.

Output stays where it was until the team learns to hand whole tasks to agents. Then the same engineers can double what they ship.

Where the extra output comes from

Agents take six kinds of routine work off an engineer's week, and the hours they free go into shipping features.

Illustration: in an engineer's week with agents, the six kinds of work below take up far less of the week, and the time freed up goes into shipping more.

  • Feature work From ticket to tested code.
  • Code review A first pass on every pull request.
  • Tests The ones nobody had time to write.
  • Migrations and upgrades Carried through every file they touch.
  • Unfamiliar codebases Mapped before anyone edits a line.
  • Bugs From stack trace to proposed fix.

The team you have, shipping more each sprint.

What your engineers learn to hand over

Every exercise runs on your repositories, and I adapt the topics to your stack.

The core

Agentic development, shown in Claude Code

Hand an agent a whole ticket with its context, and keep several of them running while you review.

The engineer briefs the agent with a task and its context. The agent plans, edits the code and runs the tests, repeating until they pass, and reaches the issue tracker, documentation, databases and internal APIs through MCP. The engineer then reviews the change and merges it.
Engineer
Brief the task
Ticket plus context
Agent
Plan Edit code Run tests

Repeats until the tests pass

Connected via MCP
  • Issue tracker
  • Docs
  • Databases
  • Internal APIs
Engineer
Review
Merge
Taught in Claude Code Cursor Codex GitHub Copilot

Around the core

  • MCP and internal tools

    Agents that read your tracker, docs and databases

  • Parallel work with subagents

    Several agents, one engineer reviewing

  • Review and quality at volume

    Review and test habits that keep up with agent output

  • Rolling agents out across the team

    From a few enthusiasts to the whole team

Briefing leadership too? AI training for leadership teams

Taught by an engineer who studied people

Engineers listen to someone who ships code. Habits change with someone who knows why they formed.

Luka Breitig

Engineer and founder

6 years as co-founder and CTO

Tymeslot and In A Nutshell, my own products

Studied people

Top 2% nationally, in a master's in management

BSc Psychology

What clients said about the training

From engineering teams I trained to work with AI agents.

I worked closely with Luka as the topic sponsor for a workshop on integrating AI meaningfully into everyday development work.

He took the time to understand our participants' needs and adapted his approach to the tools and working environments available.

Participant feedback reinforced my own positive experience, with especially strong recognition of his subject expertise and the balance between theory and practice.

I wholeheartedly recommend Luka as a trainer to any team looking to build practical AI skills.

Marco Ochse

Marco Ochse

Senior Expert Security, Deutsche Telekom

LinkedIn profile
Deutsche Telekom

We had a Cursor AI training with Luka. He is a highly competent trainer who answered all our questions thoroughly and adapted the course to our needs and preferences. I highly recommend working with him!

Herbert Reiter

Herbert Reiter

CTO, financial.com

LinkedIn profile
financial.com

How a booking works

From first call to agents doing real work on your codebase.

  1. 01

    A call about your team

    You tell me about your stack and your backlog, and we look at how much agents can take on.

  2. 02

    Built around your backlog

    I rework the course around your repositories and real tickets your team has queued.

  3. 03

    Training on your codebase

    On site or remote, your team ends the training with agents already closing real tickets.

  4. 04

    Follow-up when you want it

    Once your team has worked with the agents for a while, you can book follow-up sessions.

Is this for your team?

Booked by a company for one engineering team, run on its own codebase.

A good fit

  • Backlog outgrowing the team
  • Hiring can't keep up with the roadmap
  • AI licences used as autocomplete
  • 5 to 30 engineers, depending on the course

Not a fit

  • A self-paced course for one person
  • For software built for you, see development.
  • Agents merging unreviewed code

How far is your engineering team with AI agents?

Nine quick questions, about three minutes, on setup, adoption, integration and results. You get a score for each area and the next step that fits where your team stands.

See where your team stands

Courses for engineering teams

Pick the tool your team already pays for, or start with AI Coding Training to choose one. I rebuild every booking around your stack.

New to AI agents

Claude Code Training

Ship real features with Claude Code: steer it with project instructions, keep its diffs reviewable, and set guardrails that hold up in a production codebase.

1, 2 or 4 days See the curriculum
New to AI agents

Cursor Training

Make your team fluent in Cursor: which mode to reach for, how to teach it your conventions, and how to keep a twelve-file change reviewable.

1, 2 or 4 days See the curriculum
New to AI agents

GitHub Copilot Training

Move a team past tab completion into Copilot's chat and agent surfaces, its role in code review, and the enterprise controls around all of it.

1, 2 or 4 days See the curriculum
New to AI agents

Codex Training

Hand engineering work over to Codex and get it back finished: task briefs, parallel runs, environment setup, and reviewing a change nobody watched being written.

1 or 2 days See the curriculum
New to AI agents

AI Coding Training

Choose one AI coding tool for the team, agree how everyone uses it, and run a rollout that shows the gain in output.

1, 2 or 4 days See the curriculum
Intermediate

Building AI Agents

Build agents that run real workflows in production, with the tools, tests and guardrails that keep them reliable.

2 or 4 days See the curriculum
Advanced

MCP Server Training

Build a working MCP server against your own systems, from the protocol up to auth and distribution.

1 to 2 days See the curriculum
Intermediate

Self-Hosted LLM Training

Run language models on your own infrastructure and serve them to the whole team, with the data staying inside the building.

1 or 2 days See the curriculum

Questions engineering leads ask

The ones that usually come up before a booking.

GitHub Copilot made its name with autocomplete, suggesting the next few lines as you type. In agentic coding you describe a goal, and an agent plans the approach, reads your codebase, writes code across several files, runs the tests and iterates on errors. Claude Code works this way, and so do the agent modes now built into Copilot, Cursor and Codex. For a team, that means scale, because one engineer can direct several pieces of work at once.

Doubling is the target the training is built around, and how close a team gets depends on its backlog. The gain comes from work an agent can carry end to end: well-specified features, tests, migrations, first-pass reviews and bug reproduction. A team whose backlog is full of that work gets closest; a team that mostly does research or architecture gains less. Tell me about your backlog and we can work out where your team sits.

Prompt engineering is the smallest part of it. The topics that matter now are agentic workflows with tools like Claude Code, running work in parallel with subagents, MCP integrations that connect agents to internal tools, AI-assisted code review, and finding your way round unfamiliar codebases. It should also cover how review and testing keep up once agents write more of the code, and run on the team's own codebase, so participants apply it the next morning.

Look for a trainer who ships production software with these tools every day. Claude Code is my main development environment, for client work and for my own products such as Tymeslot, an open-source scheduling platform. The exercises come from that work, including where agents fail and how to recover. Cegos Integrata, NobleProg and Code First Girls book me for exactly that.

Yes. I deliver every workshop in German (native) or English (fluent), and in bilingual teams participants can ask questions in either language. The exercises run on your team's own codebase and tools, so each one is a task from your team's own week. I run it remotely, on site at your offices, or as a mix of both.

I am happy to sign an NDA. Claude Code and similar agents send prompts and the code they read to the model provider, under the data terms of your plan. If code has to stay in your own cloud or under stricter terms, we can run Claude Code through Amazon Bedrock or Google Vertex AI, or with zero data retention. For code that cannot be used in the training at all, I bring a comparable practice repository.

Each participant needs working access on the day to the tool the course uses. It is worth arranging this a week ahead.

Between 5 and 30, depending on the course. Above about fifteen, I pair people up for the practical parts.

It depends on several things: the course, the size of the team, how long it runs, on site or remote, and how much preparation your codebase and tools need. Tell me about your team and we'll work out an offer that makes sense for both sides. You get the price in writing before anything is booked.

Your team keeps everything we set up during the training, including instruction files such as CLAUDE.md, agent settings and prompt libraries. Once the team has worked with the agents for a while, you can book follow-up sessions.

Something else on your mind?

Find out how much of your backlog agents can take on.

Tell me about your stack and your team, and I'll tell you which work agents can carry and which course fits. A few lines are enough.

I reply myself, usually within a day. In English or German, on site or remote.

Further reading

Articles on how agents work, for anyone deciding where to use them

When your AI turns against you: defending public chatbots from prompt injection

When your AI turns against you: defending public chatbots from prompt injection

20 May 2025
Luka Breitig

Users turned Bild.de's public chatbot against its own brand. I walk through the prompt-injection defences that keep a public chatbot working for you.