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
  • Why separating planning, execution, and review phases yields superior results compared to single-prompt approaches
  • A decision framework to guide the rest of the day

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

  • Understanding 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 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: how Claude Code manages parallel work internally
  • MCP: connecting external tools—such as GitHub, databases, and internal APIs—while establishing security boundaries
  • Hands-on: configure Claude Code and personalize your 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 results: knowing when to accept outputs 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 review delegations focusing on security, design, and performance
  • Multi-file review with traceability—understanding what changed, why, and what to verify
  • Hands-on: review actual code submitted by 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
  • 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

  • Proficiency in at least one programming language
  • Familiarity with terminal or command-line environments
  • Foundational knowledge of Git (including commits, branches, and pull requests)
  • A laptop with internet access—Claude Pro account required (registration instructions will be provided)
 7 Hours

Number of participants


Price per participant

Upcoming Courses

Related Categories