Get in Touch

Course Outline

09:00 – 09:15 — Welcome & Overview

  • Course objectives, technical setup verification, and participant 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 integration, prompt precision, and workflow design
  • The advantages of decoupling planning, execution, and review phases over relying on single-prompt interactions
  • A decision-making framework to guide participants throughout the day

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

  • Understanding the distinctions between Claude Code and tools like Copilot, Cursor, and chat-based assistants, and why these differences matter
  • The agentic lifecycle: read, plan, act, and verify
  • Live demonstration: executing a multi-file task from a single command

10:45 – 12:15 — Module 3: Setup & Personalisation: CLAUDE.md, Skills, Hooks, Agents & MCP

  • CLAUDE.md: defining project memory, architectural guidelines, and team conventions
  • Skills and hooks: building reusable slash-command workflows and event-driven automation scripts
  • Sub-agents: managing parallel internal delegation within Claude Code
  • MCP: integrating external systems — GitHub, databases, internal APIs — while maintaining security boundaries
  • Practical exercise: configure Claude Code and customize your personal environment

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
  • Refining outcomes: determining when to accept results versus when to provide corrective feedback
  • Practical exercise: build a complete feature from start to finish

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

  • Structuring review delegations focused on security, design integrity, and performance
  • Conducting multi-file reviews with full traceability — understanding changes, rationale, and verification steps
  • Practical exercise: review actual code submissions from fellow participants

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

  • Deriving architecture decisions and Architecture Decision Records (ADRs) from project requirements
  • Evaluating design alternatives and identifying potential trade-offs
  • Practical exercise: design a component or feature using Claude Code

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

  • Summary of key learnings and commitment to three actionable improvements for each participant
  • Open floor for questions and discussion


Requirements

  • Proficient experience in at least one programming language
  • Familiarity with terminal or command-line interfaces
  • Fundamental understanding of Git workflows (commits, branches, and pull requests)
  • Personal laptop with reliable internet access — a Claude Pro account is mandatory (access details provided upon registration)
 7 Hours

Number of participants


Price per participant

Upcoming Courses

Related Categories