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 choice, codebase context, tooling, prompt precision, and workflow
  • Why separating planning, execution, and review phases 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

  • 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 guidelines, and team conventions
  • Skills and hooks: creating reusable slash-command workflows and event-driven automation
  • Sub-agents: how Claude Code internally delegates parallel tasks
  • MCP: connecting external tools (GitHub, databases, 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: determining when to accept and when to redirect
  • Hands-on: implementing a real feature from start to finish

13:45 – 14:45 – Case 2: Performing Code Review with Claude Code

  • Structuring review delegations across security, design, and performance dimensions
  • Conducting multi-file reviews with traceability – understanding what changed, why, and what to verify
  • Hands-on: reviewing actual code contributed by participants

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

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

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

  • Key takeaways and three concrete action items each participant commits to implementing
  • Open Q&A session
🌟

Requirements

  • Proven proficiency in at least one programming language
  • Comfort with terminal/command line environments
  • Foundational Git knowledge (commits, branches, pull requests)
  • A laptop with internet access and an active Claude Pro account (registration instructions will be provided)
 7 Hours

Number of participants


Price per participant

Upcoming Courses

Related Categories