Migrating to Claude Code
For organisations adopting Claude Code, including teams moving from other AI coding tools.
Beyond the free material
The official courses and documentation are good. What they cannot do is answer your engineers' questions about your work. Our sessions are live and expert-led, and cover what to look for and how to roll Claude Code out across a team. In the Organisation package they are also tailored to your stack, and cover standards and administrator settings.
Recommended agendas
Each session opens with 5 minutes of welcome, then runs through its 10-minute topics, then questions. This is where we suggest starting. The final agenda is agreed after booking, when you can swap topics in from the whole catalogue, and you do not need to choose anything to enquire.
Essentials
Session 1: 90 minutes, for engineers
- Progressive disclosure: best practices for CLAUDE.md files and rules
- Context windows: what fills them and how to keep them clear
- Choosing models and effort
- How Claude Code works, and choosing a permission mode
- Plan first, then review and rewind
- Git and pull requests with Claude Code
- Coming from Copilot or Cursor
Then 15 minutes of Q&A.
Team
Session 1: 90 minutes, for engineers
- Progressive disclosure: best practices for CLAUDE.md files and rules
- Context windows: what fills them and how to keep them clear
- Choosing models and effort
- How Claude Code works, and choosing a permission mode
- Plan first, then review and rewind
- Git and pull requests with Claude Code
- Coming from Copilot or Cursor
Then 15 minutes of Q&A.
Session 2: 90 minutes, for engineers
- Skills and slash commands
- Hooks: guardrails that always run
- Asking well: prompts, context and course-correcting
- Exploring and debugging an unfamiliar codebase
- Tests as the feedback loop
- Claude Code in your IDE, desktop and browser
Then 25 minutes of Q&A.
Session 3: 90 minutes, for engineers
- MCP servers: connecting your tools and data
- Sub-agents, agent teams and parallel work
- Automating Claude Code: headless, CI, routines and /loop
- Code review with Claude Code
- Security reviews with Claude Code
Then 35 minutes of Q&A.
Organisation
Session 1: 90 minutes, for engineers
- Progressive disclosure: best practices for CLAUDE.md files and rules
- Context windows: what fills them and how to keep them clear
- Choosing models and effort
- How Claude Code works, and choosing a permission mode
- Plan first, then review and rewind
- Git and pull requests with Claude Code
- Coming from Copilot or Cursor
Then 15 minutes of Q&A.
Session 2: 90 minutes, for engineers
- Skills and slash commands
- Hooks: guardrails that always run
- Asking well: prompts, context and course-correcting
- Exploring and debugging an unfamiliar codebase
- Tests as the feedback loop
- Claude Code in your IDE, desktop and browser
Then 25 minutes of Q&A.
Session 3: 90 minutes, for engineers
- MCP servers: connecting your tools and data
- Sub-agents, agent teams and parallel work
- Automating Claude Code: headless, CI, routines and /loop
- Code review with Claude Code
- Security reviews with Claude Code
Then 35 minutes of Q&A.
Session 4: 60 minutes, for Staff+ engineers
- Layering CLAUDE.md and rules across repositories and teams
- Standards that enforce themselves: hooks and checks
- Shared skills, plugins and mods: ownership, review and versioning
- Reviewing AI-written code, defining done and measuring impact
Then 15 minutes of Q&A.
Session 5: 60 minutes, for administrators
- Managed settings and permissions policy for every developer
- Approving MCP servers, plugins and mods
- Spend limits, analytics and telemetry
- Data, privacy and sandboxing
Then 15 minutes of Q&A.
Standalone session
Session 1: 60 minutes, for engineers
- Progressive disclosure: best practices for CLAUDE.md files and rules
- Context windows: what fills them and how to keep them clear
- Choosing models and effort
- How Claude Code works, and choosing a permission mode
Then 15 minutes of Q&A.