Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
09:00 – 09:15 – Welcome & Overview
- Objectives for the day, technical setup check, introductions
09:15 – 10:00 – Module 1: AI Code Quality & the Plan–Execute–Review Principle
- Five key factors that influence outcomes: model, codebase context, tooling, prompt precision, and workflow
- Why separating planning, execution, and review phases yields better results than relying on a single prompt
- A decision framework to guide the rest of the day
10:00 – 10:45 – Module 2: From Autocomplete to Agent: The Claude Code Paradigm
- How Claude Code differs from Copilot, Cursor, and chat-based tools — and why this distinction matters
- The agentic cycle: read, plan, act, verify
- Live demo: orchestrating a multi-file task from a single instruction
10:45 – 12:15 – Module 3: Setup & Personalisation: CLAUDE.md, Skills, Hooks, Agents & MCP
- CLAUDE.md: encoding project memory, architecture rules, and team conventions
- Skills and hooks: creating reusable slash-command workflows and event-driven automation
- Sub-agents: how Claude Code delegates parallel work internally
- MCP: connecting external tools — GitHub, databases, internal APIs — and establishing security boundaries
- Hands-on: configure Claude Code and personalise your own setup
12:15 – 12:45 – Lunch Break
12:45 – 13:45 – Case 1: Writing Code with Claude Code
- Delegating implementation tasks with context and acceptance criteria
- Iterating on results: when to accept output and when to redirect
- Hands-on: implement a real feature end-to-end
13:45 – 14:45 – Case 2: Doing Code Review with Claude Code
- Structuring a review delegation: security, design, performance
- Multi-file review with traceability — what changed, why, and what to verify
- Hands-on: review real code submitted by participants
14:45 – 15:45 – Case 3: Designing with Claude Code
- Generating architecture decisions and ADRs from requirements
- Exploring design alternatives and surfacing trade-offs
- Hands-on: design a component or feature with Claude Code
15:45 – 16:15 – Recap & Q&A
- Key takeaways and three concrete changes each participant commits to
- Open Q&A
Requirements
- Strong proficiency in at least one programming language
- Comfort with terminal or command-line interfaces
- Fundamental Git knowledge (commits, branches, pull requests)
- Laptop with internet access — a Claude Pro account is required (setup instructions will be provided upon registration)
7 Hours
