Claude training topics
Focused guides for teams comparing workshops, adoption programs, governance models, MCP workflows, and practical AI coding habits.
Each guide covers one operating habit behind a successful Claude rollout: choosing the right tool, writing repository rules, reviewing AI-generated changes, setting team conventions, and keeping humans in control of architecture and security. They are written for engineering leads and teams who want a repeatable way of working, and every guide maps to a hands-on module we teach on your own codebase.
- Claude Code vs Cursor vs Codex CLI for teams
- Claude Code delegation: subagents, skills
- Claude Code team conventions and hooks
- Claude Code CLI workflow: hooks and MCP
- Claude Code MCP servers: what to add first, and team rules
- Agentic coding workshops for engineering teams
- Safe AI coding practices for development teams
- AI code review habits for generated code
- How can platform and infrastructure teams use shared Claude Code agent workflows?
- UK AI coding workshops for engineering teams
- Claude Code MCP training for engineering teams
- Claude Code hooks training for engineering teams
- Claude Code review training for engineering teams
- Claude Code plan mode training for engineering teams
- Claude Code best practices training for engineering teams
- Claude Code course for engineering teams
- Claude Code enterprise training for engineering teams
Have you tried these?
Run the change on one branch. The methodology puts that in Review: an engineer still owns the merge. Training is the team version of that step.
Want a practical team program?
Turn these Claude topics into a hands-on workshop for your own codebase, review flow, and adoption goals.
Where does your team stand?
Each team member completes the proficiency matrix individually. You receive a PDF with the team baseline and a recommended next step.
Assess your team