Get in Touch

Course Outline

09:00 – 09:15 — Welcome & Overview

  • Day’s objectives, technical configuration checks, and introductions

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

  • Five critical factors influencing outcomes: model selection, codebase context, tooling, prompt precision, and workflow
  • Why decoupling planning, execution, and review stages delivers superior results compared to single-prompt approaches
  • 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 distinguishes itself from Copilot, Cursor, and chat-based tools — and why this distinction is crucial
  • The agentic cycle: read, plan, act, verify
  • Live demonstration: executing 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: building reusable slash-command workflows and event-driven automation
  • Sub-agents: understanding how Claude Code internally delegates parallel tasks
  • MCP: connecting external tools — such as GitHub, databases, and internal APIs — while establishing security boundaries
  • Hands-on activity: configuring Claude Code and tailoring your personal setup

12:15 – 12:45 — Lunch Break

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

  • Delegating implementation tasks with clear context and acceptance criteria
  • Iterating on outputs: determining when to accept results and when to redirect
  • Hands-on activity: implementing a real feature from start to finish

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

  • Structuring review delegations covering security, design, and performance
  • Multi-file reviews with full traceability — understanding what changed, why, and what needs verification
  • Hands-on activity: reviewing actual code submitted by participants

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

  • Generating architectural decisions and Architecture Decision Records (ADRs) based on requirements
  • Exploring design alternatives and highlighting trade-offs
  • Hands-on activity: designing a component or feature using Claude Code

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

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

Requirements

  • Substantial experience with at least one programming language
  • Confidence operating within a terminal or command-line environment
  • Fundamental Git proficiency (including commits, branches, and pull requests)
  • A laptop with internet access — a Claude Pro account is mandatory (registration instructions will be provided)
 7 Hours

Number of participants


Price per participant

Provisional Upcoming Courses (Require 5+ participants)

Related Categories