Get in Touch

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

  • Five key factors influencing outcomes: model selection, codebase context, tooling, prompt precision, and workflow
  • Why separating planning, execution, and review yields superior results compared to single-prompt approaches
  • A decision 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 Copilot, Cursor, and chat-based tools — and why this distinction is critical
  • 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 internally delegates parallel work
  • MCP: connecting external tools — GitHub, databases, internal APIs — and establishing security boundaries
  • Practical exercise: 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: knowing when to accept and when to redirect
  • Practical exercise: 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 it matters, and what to verify
  • Practical exercise: review real code from participants

14:45 – 15:45 — Case 3: Designing with Claude Code

  • Generating architecture decisions and Architectural Decision Records (ADRs) from requirements
  • Exploring design alternatives and identifying trade-offs
  • Practical exercise: design a component or feature using Claude Code

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

  • Key takeaways and three concrete changes each participant commits to implementing
  • Open Q&A session
🌲☁️

Requirements

  • Proficient experience in at least one programming language
  • Confidence working within a terminal or command-line environment
  • Fundamental Git knowledge (commits, branches, pull requests)
  • Laptop with internet connectivity — a Claude Pro account is required (registration instructions will be sent upon sign-up)
 7 Hours

Testimonials (2)

Related Categories