Skip to main content

Labs

One folder per lab. Each has INSTRUCTIONS.md (what to do) and checklist.md (what "done" looks like). Every lab starts with a table that says how long it takes, which preset the shop must be in, and what you need to have done before. Missed a lab? Each lab says how to catch up, so you can always join the next one.

LabModuleTimeShop preset
Lab 0 - Arrival0 - Arrival & Environment Check30 minclean
Lab 2 - Context2 - Context Engineering25 minclean
Lab 3 - Skills3 - Agent Skills25 minclean
Lab 4 - RobotCode4 - RobotCode for Agents25 minclean
Lab 5 - Prompt to green5 - Natural Prompt Automation & Debugging30 minclean
Lab 6 - MCP6 - Robot Framework MCP25 minclean
Lab 7 - Hooks and toolbelt7 - Hooks, Subagents & the CLI Toolbelt20 minbuggy
Lab 8 - Healing8 - Self-Healing Tests12 mindrift_and_bug
Lab 9 - CI9 - CI & Toolchain Integration15 minclean

Module 1 (the cold open) and Module 10 (wrap-up) have no lab.

Bonus labs​

Self-paced, for after the day. They are not part of the timetable. Bonus 1 and 2 build your own Robot Framework library or tool with an agent, and follow Building libraries and tools with an agent. Bonus 3 has you write subagents of your own for the workshop's suite, and builds on Labs 4 and 7.

LabChapterTimeShop preset
Bonus 1 - A libraryBuilding a library with an agentabout 2 hoursclean
Bonus 2 - A toolBuilding a tool with an agentabout 60 minclean
Bonus 3 - SubagentsSubagents for debugging and analysisabout 60 mindrift_and_bug

How a lab works​

  • Steps are either a command to run or a prompt to give your coding agent. Prompts are quoted in full: paste them as they are, so that everyone's agent gets the same input. Your agent's answer will still differ from your neighbour's. Comparing the two is part of the lesson.
  • Presets switch the shop between behaviours: clean, the drift stages and the planted-bug presets. Apply them only with the shop helper, uv run --no-sync python -m shop preset <name>. It works for the local shop and for your own space on the shared instance alike. The labs that change the preset reset it in their last step.
  • Claude Code, Codex and GitHub Copilot all work. Where they differ, a step shows a table with one column per agent. The facilitator demonstrates with Claude Code.
  • If your agent fails mid-lab, every lab links to a recorded walkthrough of the same lab among the transcripts. Follow along there, and rejoin at the next module.
  • After a lab, its reference shows what the rehearsal produced, why it is a good result, and the answers the debrief covers. Open it once you are done: it gives the answers away.
  • Stretch goals are for when you finish early. Nothing later depends on them.

Words you have not met before are in the glossary.