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 objectives, technical setup verification, 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 decoupling planning, execution, and review yields superior results compared to relying on a single prompt
- A decision-making framework to guide the remainder of the day
10:00 – 10:45 — Module 2: From Autocomplete to Agent: The Claude Code Paradigm
- How Claude Code differs from tools like Copilot and Cursor, as well as chat-based assistants — and why this distinction is critical
- The agentic cycle: read, plan, act, verify
- Live demonstration: 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, architectural rules, and team conventions
- Skills and hooks: creating reusable slash-command workflows and event-driven automation
- Sub-agents: understanding how Claude Code delegates parallel work internally
- MCP: connecting external tools — such as GitHub, databases, and internal APIs — while establishing security boundaries
- Hands-on exercise: configuring Claude Code and personalising your setup
12:15 – 12:45 — Lunch Break
12:45 – 13:45 — Case Study 1: Writing Code with Claude Code
- Delegating implementation tasks with adequate context and acceptance criteria
- Iterating on generated results: knowing when to accept output and when to redirect
- Hands-on exercise: implementing a real feature end-to-end
13:45 – 14:45 — Case Study 2: Conducting Code Reviews with Claude Code
- Structuring review delegations across security, design, and performance dimensions
- Conducting multi-file reviews with full traceability — understanding what changed, why, and what to verify
- Hands-on exercise: reviewing actual code contributed by participants
14:45 – 15:45 — Case Study 3: Designing with Claude Code
- Generating architectural decisions and Architecture Decision Records (ADRs) from requirements
- Exploring design alternatives and identifying trade-offs
- Hands-on exercise: designing a component or feature using Claude Code
15:45 – 16:15 — Recap & Q&A
- Key takeaways and three concrete actions each participant commits to implementing
- Open floor for questions and answers
Requirements
- Substantial experience in at least one programming language
- Comfort with working in a terminal or command-line environment
- Basic proficiency with Git (commits, branches, and pull requests)
- Laptop equipped with internet access — a Claude Pro account is required (instructions will be provided upon registration)
7 Hours
Testimonials (1)
"I learned the potential of the tool and gained sufficient skills to start using it for my work right away
