Skip to content
In-house team training

Cursor Training

Hands-on Cursor training that turns the editor your team already pays for into more shipped work: the right mode for each job, shared rules, and multi-file changes a colleague can review.

Rebuilt on your team's work

Starting point
New to AI agents
Length
1, 2 or 4 days
Delivery
On site, Remote, Hybrid
Group size
5 to 25 participants
See all courses

Run privately for your team, on dates and at a length that suit you.

Engineering teams and providers I have delivered AI training for

  • Cegos Integrata
  • NobleProg
  • Innomotics
  • financial.com
  • Frequentis
  • Vertiv
  • Deutsche Telekom

What your team will be able to do

Every module ends with something participants can repeat on Monday morning in their own work and tools, so the team gets more done without adding people.

  • Pick the right mode

    Pick the right mode for each job: Tab, inline edit, or the agent's Ask, Plan and Agent modes.

  • Teach it your conventions

    Write rules files that make Cursor follow your project's patterns, so its code looks like your team wrote it.

  • Change many files at once

    Drive a change that spans a dozen files and still have it arrive as something a colleague can review.

  • Read the diff properly

    Spot the plausible-looking edit that changes behaviour somewhere you were not looking.

  • Know what leaves your machines

    Set privacy and indexing options on purpose, so nobody has to guess what is sent to the model.

  • Agree one way of working

    Commit shared rules to the repository so a new joiner inherits the team's setup instead of inventing their own.

Is this course right for your team?

Who it is for

  • Developers who have Cursor open all day and suspect they are using a fraction of it.
  • Front-end and full-stack developers who work across many small files at once, where multi-file editing pays off fastest.
  • Team leads who want one agreed way of working in the editor for the whole team.

What to have ready

  • Cursor installed, signed in, and opened at least once before the day.
  • Day-to-day professional coding in a language your team ships.
  • A laptop that can check out a real repository, ideally one participants are allowed to break.

What the course covers

Most of the time goes on hands-on exercises. Module order and depth are set for your group before the first day.

70% hands-on
Module 1

Tab, inline edit and the agent modes

From 1 day
  • Tab completion: what it is good at, and the habit of accepting it too quickly
  • Inline edit for the change you can describe in a single sentence
  • Plan mode for work that spans several files, with the approach agreed before any code is written
  • Agent mode, and the point at which you stop watching every step
Module 2

Rules, indexing and context

From 1 day
  • Project rules that survive a refactor, and the ones that go stale within a week
  • What the codebase index contains, and when it misleads you
  • Pulling in external documentation so the answer is not two versions out of date
  • Choosing a model per task instead of leaving the default on everything
Module 3

Changes that span many files

From 2 days
  • Scoping a change so the set of files it touches is predictable before it runs
  • Checkpoints and rollback, set up before things go wrong
  • Running the suite as part of the loop instead of at the end of the afternoon
  • Rescuing a change that went sideways in file seven of twelve
Module 4

Reviewing what comes out

From 2 days
  • Reading a large diff for its intent first
  • Catching the edit that works but does not look like the rest of your codebase
  • Configuration, credentials and the files that should never be in scope
  • Saying no to a change that is quicker to rewrite than to correct
Module 5

Rolling it out across the team

From 4 days
  • Rules committed to the repository so everybody inherits the same setup
  • Seats, plans, and the numbers finance will ask for
  • Living with a team that has not all moved off their previous editor
  • Agreeing what would count as success before the rollout starts

Choose how far the team goes

Every length uses the same modules. A longer booking takes the team further through the same curriculum.

Essentials

1 day

Tab, inline edit and Agent with its modes, and how to teach Cursor your conventions. The day for a team that installed it and never left autocomplete.

Modules covered

  • Tab, inline edit and the agent modes
  • Rules, indexing and context

Core

2 days

Adds the multi-file work teams buy Cursor for, and the review habits that stop those changes from landing unread.

Modules covered

  • Tab, inline edit and the agent modes
  • Rules, indexing and context
  • Changes that span many files
  • Reviewing what comes out

Complete

4 days

Adds what a rollout needs: rules everyone shares, the licence and privacy decisions, and a way to tell afterwards whether it helped.

Modules covered

  • Tab, inline edit and the agent modes
  • Rules, indexing and context
  • Changes that span many files
  • Reviewing what comes out
  • Rolling it out across the team

We settle the length when we talk about your team, and it can still change afterwards.

Your team's version of this course

Your version runs in your repository: the rules files are written for your conventions, indexing is tuned to how your code is laid out, and the multi-file exercise is a change your team actually needs to make.

How a booking works

What gets adjusted

  • Depth of each module
  • Your tools, code or content
  • Group size and seniority mix
  • Length and how days are split
  • English or German
  • On site, remote or hybrid

How the training is delivered

On site

In your office, with the team in the room. Best for a first rollout.

Remote

Live over video, in shorter blocks across several days.

Hybrid

A day on site to start, then shorter remote sessions on real work.

Optional add-ons Certificate of participation

Every course runs privately for one team, on dates we agree together.

Does this match your team's work?

Every module can be rebuilt on your team's own work and tools. Tell me what the team works on and I will tell you what I would change.

Luka Breitig, AI agent trainer and software engineer
Your trainer

Luka Breitig

AI agent trainer and software engineer

I have trained engineering teams on Cursor, financial.com among them, and teach Claude Code and Copilot as well, so the course is clear about where Cursor is the better choice and where it is not.

  • Ships production software every day
  • Delivers in English and German
  • Speaker at Nomad Summit

What clients said about the training

From engineering teams I trained to work with AI agents.

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

Questions about this course

What teams ask before they book.

No, but they do need to be working developers. The day starts with the editor's own modes, so somebody who installed Cursor last week can follow it. What it does assume is that everyone in the room reads code critically, because that is where most of the value sits.

Yes, working on the day, so sort them out well before that morning. The free plan's limits are too tight for a full day of exercises. Once a date is agreed I send the exact plan requirements, and if procurement is slow at your end I will build the exercises around whatever access you can get in time.

Yes, and it is the difference between a demo and a course. Cursor behaves differently in a large existing codebase than in a fresh project, and that gap is most of what a team needs to see. Send me the stack in advance and the exercises are rebuilt against it.

Yes. Privacy mode, what indexing stores, and which settings your IT department should mandate have their own slot in the day. If the constraint means no company code at all, I bring a repository of comparable size and the exercises run against that instead.

Not much for the material, quite a lot for the room. The rules, review and multi-file thinking transfer directly, so nobody sits idle. If the split is roughly even, tell me beforehand and I will run the exercises so both editors get used and both groups stay at the keyboard.

Have a question about your team's setup?

Get more out of the team you already have

Tell me what your team works on and how it uses AI today. A few lines are enough. I reply myself, usually within a day, and if this course is the wrong one I will point you to the one that fits.

Download trainer profile

In English or German, on site, remote or hybrid.

Cursor Training

A few lines are enough