Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
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 outcomes: model selection, codebase context, tooling, prompt precision, and workflow design
- Why separating planning, execution, and review phases yields superior results compared to relying on a single prompt
- A decision framework to guide activities throughout the day
10:00 – 10:45 — Module 2: From Autocomplete to Agent: The Claude Code Paradigm
- Understanding how Claude Code differs from tools like Copilot, Cursor, and chat-based assistants—and why this distinction is crucial
- The agentic cycle: read, plan, act, verify
- Live demonstration: managing 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 rules, and team conventions
- Skills and hooks: Creating reusable slash-command workflows and event-driven automation
- Sub-agents: Understanding how Claude Code manages parallel work internally
- MCP: Connecting external tools (GitHub, databases, internal APIs) while establishing security boundaries
- Hands-on activity: Configuring Claude Code and customizing your personal setup
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 clear acceptance criteria
- Iterating on generated results: knowing when to accept output versus when to redirect the agent
- Hands-on activity: Implementing 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
- Performing multi-file reviews with full traceability—understanding what changed, why it changed, and what needs verification
- Hands-on activity: Reviewing actual code contributed by participants
14:45 – 15:45 — Case Study 3: Designing with Claude Code
- Generating architectural decisions and Architecture Decision Records (ADRs) from project requirements
- Exploring design alternatives and identifying potential trade-offs
- Hands-on activity: Designing a component or feature using Claude Code
15:45 – 16:15 — Recap & Q&A
- Summary of key takeaways and identification of three concrete actions each participant will commit to implementing
- Open question-and-answer session
Requirements
- Proficient experience in at least one programming language
- Comfort level working within a terminal or command-line environment
- Fundamental understanding of Git concepts (commits, branches, pull requests)
- A laptop with an internet connection. A Claude Pro account is required (detailed instructions will be provided upon registration)
7 Hours
Testimonials (1)
"I learned the potential of the tool and gained sufficient skills to start using it for my work right away
