Workshops · Claude Code workshop for teams

Your team gets faster with Claude Code without breaking quality

For development teams and their leads who want to use AI tools in a controlled, safe way with measurable benefit.

What you are dealing with

Everyone uses AI differently and results vary

Part of the team uses AI enthusiastically, part refuses it. Code gets written faster, but code review takes longer and bugs do not go down.

Nobody knows what may be sent to AI

There are no rules for sensitive data, keys and client code. Management worries about leaks, developers worry they are breaking rules.

You do not know whether it really makes the team faster

You pay for licences, but nobody measures the benefit. The feeling of speed may not match what actually reaches production.

Workshop agenda

The agenda is a proposal; we adjust it to your team and technologies before the workshop.

  1. Principles and limits: what an AI assistant can do in development, where it gets things wrong and why a person remains accountable for the code.
  2. Environment setup: a CLAUDE.md file with project rules, skills (repeatable procedures), MCP for connecting other tools, and permission settings.
  3. Workflow from ticket to merge request: how to turn a ticket into a plan, the plan into code changes, and the changes into a merge request ready for review.
  4. Testing and code review with AI: writing tests, reviewing other people’s changes, and how not to let a bug through just because the code looks tidy.
  5. Security and what not to send to AI: secret keys, personal data, client code, and how to handle them with rules and settings.
  6. Measuring the benefit: what to track so you see real speed-up, not just a feeling.
  7. Hands-on work in the team’s own repository: participants solve real tasks with the setup created during the day.

Format and preparation

The workshop takes one day and runs on-site at your premises or online. We recommend a group of up to 12 people so the trainer has time for everyone in the hands-on part. For larger teams we suggest several sessions.

Before the workshop there is an intro call, and participants receive installation and access instructions. If the hands-on part takes place in your repository, we agree in advance which parts of the code and which data the AI tool may access.

After the workshop you receive the materials, draft internal rules and a repository setup the team can keep using. If you want to manage the adoption of AI in development over the long term, the workshop is followed up by our Fractional CTO / AI lead service. You can read more on the topic in the article Claude Code in development teams.

What you get

  • One-day workshop tailored to your stack and processes
  • Your team's repository set up for Claude Code (CLAUDE.md, permissions, basic skills)
  • Draft internal rules for the safe use of AI
  • Recommended workflow from ticket to merge request
  • Proposal for measuring the benefit of AI in development
  • Workshop materials and a recording, if we agree on one

How it works

  1. 2–4 weeks before the workshop

    Intro call

    We discuss the team's make-up, technologies, processes and what you expect from the workshop.

  2. 1–2 weeks before the workshop

    Preparation

    Participants receive installation and access instructions. We choose the repository and tasks for the hands-on part.

  3. 1 day

    Workshop

    Principles and setup in the morning, work in the team's own repository in the afternoon.

  4. within 1 week after the workshop

    Follow-up

    We send the materials, the draft rules and recommended next steps.

Who it is for

  • Development teams that want to introduce AI tools in a controlled way
  • Teams that already use AI, but without shared rules
  • Engineering leads and CTOs who need to assess the benefits and risks
  • Companies that want results on their own code, not a generic talk

Who it is not for

  • People without programming experience who want AI for everyday office work
  • Teams whose company policy prohibits AI tools and is not going to change
  • Individuals looking for a public course with open dates

Why work with us

A trainer who works this way himself

Michal Czerník builds applications with AI-assisted development in Claude Code every day. The workshop is based on proven practice, not on the tool's documentation.

A team lead's perspective

He leads development teams and has experience in the CTO role. He also covers rules, accountability and measurement, which is what management cares about.

The full SDLC, not just writing code

Because he manages the full SDLC, the workshop also covers analysis, testing, code review and operations. AI does not become a shortcut that bypasses quality.

Frequently asked questions

Who is the workshop for?

The workshop is for development teams and their leads. Participants should program regularly; previous experience with AI tools is not required.

How large can the group be?

We recommend up to 12 people so the hands-on part works well. For a larger team we suggest several sessions.

Is the workshop on-site or online?

Both are possible. On-site, the hands-on part is more intensive; the online version suits teams spread across several locations.

Do we have to work with our own code at the workshop?

You do not have to, but we recommend it. If your own repository cannot be used, we prepare a sample project similar to yours.

Is the workshop only about Claude Code?

Claude Code is the main tool, but the principles apply to similar tools as well. The rules and workflow do not depend on a specific tool.

What are CLAUDE.md and MCP?

CLAUDE.md is a file in the repository with instructions and context for the AI assistant. MCP (Model Context Protocol) is a standard for connecting AI to other tools and data.

What do participants need to prepare in advance?

The tool installed, access to the repository and a valid account. We send exact instructions before the workshop.

Free consultation

Tell us what you are working on. We will get back to you and arrange a short call to see whether and how we can help.

A few sentences are enough: what you are solving and by when.

required