Get in Touch

Course Outline

09:00 – 09:15 — Welcome & Overview

  • Day’s objectives, technical setup verification, and introductions

09:15 – 10:00 — Module 1: AI Code Quality & the Plan–Execute–Review Principle

  • Five key factors influencing outcomes: model selection, codebase context, tooling, prompt precision, and workflow design
  • Why decoupling planning, execution, and review phases delivers superior results compared to single-prompt approaches
  • A decision-making framework to guide participants throughout 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 is critical
  • The agentic cycle: read, plan, act, verify
  • Live demonstration: executing a multi-file task via 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: building reusable slash-command workflows and event-driven automation
  • Sub-agents: understanding how Claude Code internally delegates parallel tasks
  • MCP: connecting external tools — GitHub, databases, internal APIs — while establishing security boundaries
  • Hands-on: configure Claude Code and customise your personal setup

12:15 – 12:45 — Lunch Break

12:45 – 13:45 — Case 1: Writing Code with Claude Code

  • Delegating implementation tasks with clear context and acceptance criteria
  • Iterating on generated results: knowing when to accept and when to redirect
  • Hands-on: implement a real feature from start to finish

13:45 – 14:45 — Case 2: Doing Code Review with Claude Code

  • Structuring a review delegation: focusing on security, design, and performance
  • Conducting multi-file reviews with traceability — tracking what changed, why, and what needs verification
  • Hands-on: review actual code submitted 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: design a component or feature using Claude Code

15:45 – 16:15 — Recap & Q&A

  • Key takeaways and three actionable changes each participant commits to implementing
  • Open Q&A session


Requirements

  • Strong proficiency in at least one programming language
  • Familiarity with terminal or command-line environments
  • Fundamental Git knowledge (including commits, branches, and pull requests)
  • A laptop with internet access — a Claude Pro account is mandatory (setup instructions will be provided upon registration)
 7 Hours

Related Categories