Skip to content
In-house team training

Claude for Designers Training

Let Claude take the research synthesis, interface copy and handoff specs, so your designers spend their week on the decisions only they can make.

Rebuilt on your team's work

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

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

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.

  • Synthesise research faster

    Get from a pile of interview transcripts to themes you can defend, with the quotes still attached.

  • Write the interface copy

    Draft and iterate the words inside the product, which are usually the last thing anybody gets time for.

  • Explore more options

    Explore more directions than the deadline used to allow, and tell which are worth putting in front of anyone.

  • Stay inside your design system

    Work it against your design system, so the output reuses your existing components.

  • Hand off cleanly

    Turn a design into something an engineer can build from, including the states nobody remembered to draw.

  • Keep your own taste

    Recognise the competent, average, forgettable answer, which is reliably the first one it will offer you.

Is this course right for your team?

Who it is for

  • Product and UX designers who suspect they should be using this and have been unconvinced by what they have seen so far.
  • User researchers sitting on more interview material than they will ever have time to read.
  • Design leads who need one shared answer for how their team uses AI, including where it does not.

What to have ready

  • Daily work in a design tool; which one it is does not matter.
  • A laptop with your usual design setup already on it.
  • A real project in flight, ideally one with messy research sitting behind it.

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.

75% hands-on
Module 1

What it does for design work

From 1 day
  • Where it helps, where it wastes an afternoon, and how to tell which early
  • Giving it your product context once instead of re-explaining it every time
  • Working from research documents, specifications and screenshots
  • What it cannot see about your product, and what that does to the output
Module 2

The design work itself

From 1 day
  • Interviews and survey data into themes you can defend to a stakeholder
  • Labels, empty states, errors, and the sentences nobody has time to write
  • Generating directions worth reviewing rather than twelve near-identical ones
  • Working inside your own components and tokens instead of inventing new ones
Module 3

Getting it built

From 2 days
  • Standing up something clickable to test an interaction rather than describe it
  • Specifications that answer the questions engineers come back with
  • Design tokens, and the awkward gap between your file and the codebase
  • Asking what a change would cost to build before the review rather than after it
Module 4

Judgement and critique

From 2 days
  • Reviewing generated work with the same eye you would use on a junior's
  • Why the first answer is always the average one, and what to do about that
  • Contrast, focus order, and the accessibility claims worth checking yourself
  • The parts of the work to keep entirely, and being able to say why

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

A day on the design work Claude does well, run on a project of your own.

Modules covered

  • What it does for design work
  • The design work itself

Core

2 days

Adds the handoff to engineering and the critical half of the job: what to reject, and how to keep the output looking like your product.

Modules covered

  • What it does for design work
  • The design work itself
  • Getting it built
  • Judgement and critique

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 works with your research notes, your design system and your product's voice. Variants are explored inside your own components, and the handoff module follows the way your designers and engineers already work together.

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

The seminar series on Claude I run for cimdata includes Claude Design, and as a software engineer I sit at the other end of the handoff this course prepares designers for.

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

Questions about this course

What teams ask before they book.

No. Plenty of designers have tried a chat window, been unimpressed and stopped. The day starts by showing why that experience is the normal one, and what changes once the tool has your project context in front of it.

Yes, as far as they work today, which is less far than the demos suggest. The handoff module in the two-day booking covers what moves between a design file and a codebase and what still needs a person. Tell me your setup and I will tailor that part to it.

No, and I would not run it if it were. It moves the tedious half of the work, the transcripts and the empty-state copy, so the judgement half gets more of the week. The critique module in the two-day booking is there because the tool has no taste and your team does.

It makes the course more useful rather than less. A design system gives the tool something concrete to work inside, which is the whole difference between output that fits your product and output that looks like a template. Send it over beforehand and the exercises get built around it.

If they want to build working tools beyond the design file, vibe coding is the better fit. This course stays with design work itself: research, copy, variants inside your design system and the handoff to engineering.

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.

Claude for Designers Training

A few lines are enough