6 intensive sessions, one hour each

What you get by the end of the workshop

The independent ability to build, maintain and deploy digital projects with Claude Code, without depending on an outside developer for every small change.

  • Independence in development: building a personal tool, website or automation from start to finish, and maintaining it over time
  • Confidence in your working environment: command of the terminal, files and version control (git) at the level everyday work requires
  • The right way to think about development tasks: breaking a complex problem into steps Claude can carry out, and checking that the result is correct
  • Extending what it can do through the ecosystem: using skills, plugins and connectors to give Claude abilities and access it doesn't have by default
  • Safety habits: understanding what is safe to run, how not to expose sensitive information, and how to roll back when something goes wrong

Workshop structure: what you gain in each session

Session 1 | Foundations: the terminal, the project and the safety rules

Getting to know the basic working world: what a terminal is, what a project folder is, and why Claude Code is different from a regular chat (it works directly on real files). Essential safety rules: what you can run without worry, when to stop and check, and how to keep sensitive information (API keys, passwords) out of the code. The session includes a first installation and running a simple task from start to finish.

Session 2 | Version control as a safety net

Getting to know git principles, only at the level you need: saving checkpoints ("commits"), and being able to roll back if something breaks. This is the key tool that makes trial and error safe. Practice: creating a new project, making changes, and actually practicing a rollback.

Session 3 | Leading a project, from planning to execution

How to break a big task (for example "build me an expense tracking tool") into clear stages that Claude can carry out one after another. Using plan mode before making significant changes, and communicating effectively with Claude when the result is not quite what you wanted. Practice: building a simple personal tool from start to finish.

Session 4 | Debugging, standing instructions and skills

How to read an error message without panicking, and how to pass it to Claude in a way that leads to a quick fix. Alongside that, how to give Claude standing instructions for a project so it remembers the context over time, and getting to know skills: ready made modules (official or community) that give Claude knowledge and working habits in a specific area, including the safety considerations of installing outside skills. Practice on a real bug in the project built in the previous session.

Session 5 | Connectors, plugins and going live

Connecting the project to external data sources and services through connectors (MCP), so Claude can access tools such as databases, cloud services and outside platforms directly. Getting to know plugins: ready made packages that extend Claude Code for specific tasks without building everything from scratch. To finish, deploying the project so it is reachable at a real web address.

Session 6 | An independent project: the closing session

Building a new project from scratch, one not discussed before, on your own, with guidance only through pointed questions, freely combining the tools you have learned (version control, skills, connectors). This is the session that makes sure the ability has truly stayed with you, and that you can apply it to a new idea without close guidance.

Throughout all the sessions, three standing principles are emphasized: checking every change before running it on a live system, the habit of saving a checkpoint before every experiment, and understanding that Claude is the tool that carries out the work, while responsibility for deciding what to build and why always stays with the person.

Who the workshop is for

The workshop is designed for people with a technical bent who want to move from "using AI tools" to "actually building", with no need for a formal development background. It is especially suited to:

Digital business owners who want to build and maintain internal tools | Product people and product managers who want to prototype ideas themselves | Analysts and data people interested in automating processes | Digital marketers who want to build landing pages and small tools themselves | Founders at the MVP stage who want to test an idea before hiring a developer | Technical support and IT people who want to expand their automation abilities | Teachers and technology instructors who want to pass on practical knowledge | Anyone who runs manual, repetitive work processes today and wants to turn them into independent digital tools

The intensive pace suits people who are already comfortable with basic technology concepts (files, software, the internet) and come motivated for fast, hands-on learning, without needing extended basic explanations about computing.