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
  • The 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

  • Understanding how Claude Code differs from Copilot, Cursor, and chat-based tools — and why these distinctions matter
  • The agentic lifecycle: 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 guidelines, and team conventions
  • Skills and hooks: creating reusable slash-command workflows and event-driven automation
  • Sub-agents: understanding how Claude Code handles parallel work internally
  • MCP: connecting external tools — GitHub, databases, internal APIs — while establishing security boundaries
  • Hands-on exercise: configure Claude Code and customise your environment

12:15 – 12:45 — Lunch Break

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

  • Delegating implementation tasks by providing context and acceptance criteria
  • Iterating on results: determining when to accept or redirect output
  • Hands-on exercise: implement a real feature from start to finish

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

  • Structuring review delegations focused on security, design, and performance
  • Multi-file reviews with full traceability — understanding changes, rationale, and verification steps
  • Hands-on exercise: review actual code contributed by participants

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

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

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

  • Key takeaways and three actionable commitments each participant will make
  • Open Q&A session


Requirements

  • Proficiency in at least one programming language
  • Familiarity with terminal/command line operations
  • Foundational knowledge of Git (commits, branches, pull requests)
  • A laptop with internet access; a Claude Pro account is mandatory (registration details will be provided)
 7 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories