Focus 01
Workflow first, prompt second
Feature work, refactors, bug triage and docs are mapped first. Prompt patterns come after the workflow is clear.
Claude Code workflows that survive a real week
Claude Code is a terminal coding agent from Anthropic. It works best when the team designs the workflow around it.
What this is
Tool focus: Anthropic Claude Code
Workshops on Claude Code for UK engineering teams: workflow design, review checks, MCP servers and review discipline.
Focus 02
Review checks and slash commands
Cheap checks, formatters and validators catch common mistakes. Slash commands cover the few recurring prompts worth standardising.
Focus 03
Background research with bounds
Research, audits, dependency scans and test triage stay bounded so the main session stays on the change.
Engagement
How the work runs
Read-only review
Repo, CI, and current developer workflow are mapped. We agree the first checks, commands, and MCP servers worth wiring up.
Workflow design
Workflow design, checks, slash commands, MCP short list and review patterns.
On the real repo
Real Claude Code sessions on agreed tasks. Checks run, diffs land in review.
Rollout window
Light coaching, an evaluation suite carried by the team, written rules of engagement, and a check-in to confirm the workflow holds in real weeks.
FAQ
Questions teams ask first
Claude Code lives in the terminal and reads the repository. The training is about workflow design and review discipline around an agent that has access to the codebase, not about prompt phrasing for a chat box.
Yes, where the team has a genuine internal tool worth surfacing. MCP server design has its own page; on the workshop we focus on wiring up servers that already exist or that the team can build in a day.
It is built for one. Read-only access first, named review gates, policy checks, and the M365 and identity layer underneath stays part of the engagement, not an afterthought.
Next step
Book a Claude Code workshop
Best for teams that already use a CLI seriously — git, Make, language toolchains. Less suited to teams who live entirely in a UI editor and want a one-click integration.