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
- Day’s objectives, technical environment check, and introductions
09:15 – 10:00 — Module 1: AI Code Quality & the Plan–Execute–Review Principle
- The five key factors influencing outcomes: model selection, codebase context, tooling, prompt precision, and workflow design
- Why separating planning, execution, and review yields superior results compared to using a single prompt
- A decision framework to guide the rest of the session
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 these distinctions matter
- The agentic cycle: read, plan, act, verify
- Live demonstration: driving 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 — such as GitHub, databases, and internal APIs — while maintaining security boundaries
- Hands-on activity: configuring Claude Code and personalising your own setup
12:15 – 12:45 — Lunch Break
12:45 – 13:45 — Case 1: Writing Code with Claude Code
- Delegating implementation tasks with sufficient context and acceptance criteria
- Iterating on results: knowing when to accept and when to redirect
- Hands-on activity: implementing a real feature from start to finish
13:45 – 14:45 — Case 2: Doing Code Review with Claude Code
- Structuring a review delegation focused on security, design, and performance
- Multi-file review with traceability — understanding what changed, why, and what to verify
- Hands-on activity: reviewing actual code contributed by participants
14:45 – 15:45 — Case 3: Designing with Claude Code
- Generating architecture decisions and Architecture Decision Records (ADRs) from requirements
- Exploring design alternatives and identifying trade-offs
- Hands-on activity: designing a component or feature using Claude Code
15:45 – 16:15 — Recap & Q&A
- Summary of key takeaways and three concrete actions each participant commits to implementing
- Open Q&A session
Requirements
- Strong proficiency in at least one programming language
- Comfortability working within a terminal or command-line interface
- Fundamental Git knowledge (including commits, branches, and pull requests)
- A laptop with an active internet connection – a Claude Pro account is required (setup instructions will be provided upon registration)
7 Hours
