Get in Touch

Course Outline

09:00 – 09:15 — Welcome & Overview

  • Setting the day's objectives, verifying technical setup, and participant 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 integration, prompt precision, and workflow structure
  • Why decoupling planning, execution, and review phases yields superior results compared to relying on a single prompt
  • A decision-making framework to guide the rest of the session

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

  • Understanding how Claude Code differs from tools like Copilot and Cursor, and why this distinction is critical
  • The agentic workflow: read, plan, act, and verify
  • Live demonstration: executing a multi-file task initiated by 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: Building reusable slash-command workflows and event-driven automation
  • Sub-agents: How Claude Code internally manages and delegates parallel tasks
  • MCP (Model Context Protocol): Connecting external tools—such as GitHub, databases, and internal APIs—while maintaining robust security boundaries
  • Hands-on activity: Configuring Claude Code and customizing your personal workspace

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 output and when to redirect the agent
  • Hands-on activity: implementing a real-world feature from start to finish

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

  • Structuring a review delegation focusing on security, design integrity, and performance
  • Conducting multi-file reviews with full traceability — understanding changes, rationale, and verification steps
  • Hands-on activity: reviewing actual code submitted by participants

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

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

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

  • Summary of key takeaways and three actionable commitments each participant will make
  • Open floor for questions


Requirements

  • Proficient experience in at least one programming language
  • Comfort working within a terminal or command-line interface
  • Fundamental Git knowledge (including commits, branches, and pull requests)
  • A laptop with active internet access — a Claude Pro account is required (setup instructions will be provided upon registration)
 7 Hours

Number of participants


Price per participant

Upcoming Courses

Related Categories