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

  • The five key factors influencing output quality: 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-making 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 command

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: building reusable slash-command workflows and event-driven automations
  • Sub-agents: how Claude Code internally manages parallel workloads through delegation
  • MCP: connecting external tools—including GitHub, databases, and internal APIs—while establishing security boundaries
  • Hands-on exercise: configuring Claude Code and personalizing your setup

12:15 – 12:45 — Lunch Break

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

  • Delegating implementation tasks with clear context and acceptance criteria
  • Ideally iterating on results: knowing when to accept outputs versus when to redirect the agent
  • Hands-on exercise: implementing a real feature end-to-end

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

  • Structuring review delegations across security, design, and performance dimensions
  • Multi-file reviews with full traceability—understanding what changed, why it changed, and what to verify
  • Hands-on exercise: reviewing actual code submitted by 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

  • Key takeaways and three concrete actions each participant commits to implementing
  • Open Q&A session


Requirements

  • Proven expertise in at least one programming language
  • Proficiency with terminal/command-line environments
  • Fundamental Git knowledge (commits, branches, pull requests)
  • A laptop with internet access—requires a Claude Pro account (registration instructions will be sent upon sign-up)
 7 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories