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 design
  • Rationale for separating planning, execution, and review phases over relying on a single prompt
  • A decision-making framework applicable throughout the day

10:00 – 10:45 — Module 2: From Autocomplete to Agent: The Claude Code Paradigm

  • Distinctions between Claude Code and tools like Copilot or Cursor, and why these differences matter
  • The agentic cycle: read, plan, act, and 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 guidelines, and team conventions
  • Skills and hooks: Building reusable slash-command workflows and event-driven automations
  • Sub-agents: Understanding how Claude Code internally delegates parallel work
  • MCP: Connecting external tools — GitHub, databases, internal APIs — while establishing security boundaries
  • Hands-on exercise: 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 appropriate context and acceptance criteria
  • Iterating on results: determining 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 Review with Claude Code

  • Structuring review delegations focusing on security, design, and performance
  • Multi-file review with traceability — tracking changes, understanding rationale, and identifying verification points
  • Hands-on exercise: Reviewing actual code from participants

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

  • Generating architecture decisions and Architectural 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

  • Summary of key takeaways and commitment to three concrete changes per participant
  • Open question-and-answer session
🔑ℹ️

Requirements

  • Substantial experience in at least one programming language
  • Proficiency in working within a terminal / command-line environment
  • Fundamental Git knowledge (commits, branches, pull requests)
  • Laptop with an internet connection — a Claude Pro account is mandatory (registration instructions will be provided)
 7 Hours

Related Categories