Skip to content
Training course
Beginner to Advanced Tailored to your team

Cursor Training

A hands-on course for teams working in Cursor: the four ways it edits code, the rules that make it follow your conventions, and the review habits a multi-file change needs.

Level
Beginner to Advanced
Length
1, 2 or 4 days
Delivery
On site, Remote, Hybrid
Group size
5 to 25 participants
See all courses

Booked privately for your team. Dates and length are agreed when you book.

What your team will be able to do

Every module ends with something participants can repeat on Monday morning, in your codebase and against your conventions.

Pick the right mode

Choose between tab completion, inline edit, composer and agent mode instead of using whichever one you learned first.

Teach it your conventions

Write rules files that make Cursor follow your project's patterns rather than the average of everything it was trained on.

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 quietly changes behaviour somewhere you were not looking.

Keep control of the source

Set the privacy and indexing options deliberately, so you know what leaves your machines and what does not.

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.

Curriculum

Built around hands-on work rather than slides. The running order and the depth of each module are adjusted to the group before delivery.

70% hands-on
1

The four ways Cursor edits code

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
  • Composer for work that spans several files at once
  • Agent mode, and the point at which you stop watching every step
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 actually contains, and when it is quietly misleading 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
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, used before things go wrong rather than after
  • 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
4

Reviewing what comes out

From 2 days
  • Reading a large diff for intent rather than working through it line by line
  • 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
5

Rolling it out across the team

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

How long you book it for

Every length is drawn from the same modules. A longer booking is more of the course, not a different one.

Essentials

Beginner

1 day

The four ways Cursor edits code, and how to teach it your conventions. The day for a team that installed it and never left autocomplete.

Modules covered

  • The four ways Cursor edits code
  • Rules, indexing and context

Core

Intermediate

2 days

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

Modules covered

  • The four ways Cursor edits code
  • Rules, indexing and context
  • Changes that span many files
  • Reviewing what comes out

Complete

Advanced

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

  • The four ways Cursor edits code
  • Rules, indexing and context
  • Changes that span many files
  • Reviewing what comes out
  • Rolling it out across the team

Not sure which one fits? The intake call settles it, and the length can still change afterwards.

Built around your team

No two runs of this course are the same

The curriculum above is a starting point, not a syllabus. Before anything is booked I find out where your team actually stands, then rebuild the course around that. A team already running agents daily spends its two days somewhere completely different from one that installed the tool last week.

  1. Step 1

    Intake call

    A call before anything is agreed: what your team already uses, what has gone wrong so far, and what you need them doing differently afterwards.

  2. Step 2

    Stack review

    Language, framework, review process, CI. Exercises are rebuilt against your repository so nothing in the room is hypothetical.

  3. Step 3

    Curriculum reshaped

    Modules get dropped, deepened or added. You see the adjusted outline and sign it off before the date is fixed.

  4. Step 4

    Delivery and follow-up

    We run the course, then check in once the team has applied it to real work and the awkward questions have surfaced.

What gets adjusted

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

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 rather than everyone discovering it separately.

What participants need beforehand

  • 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.

How the training is delivered

Same material either way. The format changes how much of it lands in the first week.

On site

I come to your office and work with the team in the room. Usually the most effective option for a first rollout, because the sideways questions get answered as they come up.

Remote

Delivered live over video in focused blocks rather than one long day, with shared screens and hands-on exercises on your own work.

Hybrid

A day on site to get everyone moving, followed by shorter remote sessions once the team is applying it to real work and hitting real friction.

Optional add-ons Certificate of participation

There is no public schedule. Every course is booked privately for a single team, and we agree the dates together.

Luka Breitig, software engineer and AI coding trainer
Your trainer

Luka Breitig

Software engineer and AI coding trainer

I train engineering teams to work with AI coding tools, and I use the same tools to ship production software every week. The material comes out of building things, not out of a slide deck.

Before going freelance I spent six years as technical co-founder of a marketing agency, responsible for everything technical from automation infrastructure to coordinating a freelancer network. That is why the courses spend as much time on review, guardrails and rollout as they do on prompting.

  • Ships production software every week
  • Delivers in English and German
  • On site across Europe, or remote
  • Speaker at Nomad Summit, Chiang Mai

Trusted by teams & training providers

I deliver AI training for some of Europe's leading organisations and L&D platforms.

Cegos Integrata

Cegos Integrata

Commissioned trainer via leading European L&D provider

NobleProg

NobleProg

AI coding workshops via one of the world's largest IT training marketplaces

Innomotics

Innomotics

In-house AI training for engineering teams

Bots & People

Bots & People

Commissioned trainer for developer workshops

Code First Girls

Code First Girls

Course creator — 3-month AI & agentic tools curriculum

Nomad Summit

Nomad Summit

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

Vertiv

Vertiv

In-house AI-assisted coding training for engineering teams

Questions about this course

The things teams ask before booking. If yours is not here, ask me directly.

No, but they do need to be working developers. The day starts with the editor's own modes rather than with what an agent is, 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, and working on the day rather than being sorted out that morning. The free tier runs out partway through the first multi-file exercise. 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 very differently in a large existing codebase than in a fresh project, and that difference 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 are a scheduled part of the day rather than an aside. 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 rather than one group watching the other work.

Five to twenty-five. Below five the comparison exercises stop working, because half their value is watching how differently two people drive the same tool. Above fifteen I pair people up so nobody spends the day watching somebody else's screen.

Yes, in English or German. Materials are written in English because the editor's own interface and documentation are, and translating those terms tends to make them harder to look up afterwards. A German set is available on request.

Still not sure whether this is the right fit for your team?

Book this training for your team

Tell me the size of the group, the codebase they work in, and roughly when you want to run it. I will come back with a proposal.

Download trainer profile

Delivered in English or German, on site across Europe or remotely.