Get in Touch

Course Outline

Phase 1 — Getting to Know Claude Code — 30 minutes

  • What Claude is, and what distinguishes Claude Code from standard chat interfaces
  • Quick orientation: we are using the Claude app today (web or desktop); the CLI and other interfaces are covered in the reference card
  • Interface tour: initiating a coding session and understanding the workspace
  • How Claude Code processes requests: the describe → plan → act → review loop
  • Understanding permissions: why Claude seeks approval before creating files or executing code
  • Your first build: instructing Claude to create a simple, styled webpage from a one-sentence description
  • Refining results: instructions such as “increase the header size,” “change the colour scheme,” or “add a navigation bar”
  • Guided exercise: participants initiate a session to construct a personalised “About Me” webpage, refining it through follow-up instructions

Objective: ensuring everyone surpasses the initial interaction hurdle and feels comfortable with the interface.

Break — 7 minutes

Phase 2 — Constructing Practical Items Using Plain English — 55 minutes

Three progressively complex tasks utilising only natural language prompts.

  • Task 1 — Interactive dashboard: a styled dashboard featuring sample data, charts, and statistics. Practice providing design direction: “apply a dark theme,” “include a sidebar,” or “ensure it is responsive.

  • Task 2 — Data analysis: provide a sample CSV file, and ask Claude to summarise the data, identify trends, locate highs/lows, and generate a visual chart. This demonstrates Claude writing and executing code on your behalf.
  • Task 3 — Automation tool: develop a simple utility — such as a unit converter, quiz app, or budget calculator. This introduces the concept that Claude can build interactive tools, not just static pages.

Following each task, the instructor highlights Claude’s behind-the-scenes actions: files created, code written, and how to interpret the output. Participants document their most effective prompts in a shared Prompt Playbook.

Break — 7 minutes

Phase 3 — Working Smarter with Claude Code — 35 minutes

  • The art of effective prompting: specific versus vague instructions
  • Live demonstration: side-by-side comparison of weak and strong prompts applied to the same task
  • Iterating and refining: asking Claude to explain decisions, undo changes, or attempt a different approach
  • Working with uploaded files: commands such as “read this document and summarise it,” or “convert this spreadsheet into a chart”
  • Multi-step workflows: chaining requests to construct complex outputs
  • Understanding cost and usage: how tokens, context windows, and subscription tiers function
  • When to use Claude Code versus standard Claude chat
  • Guided exercise: participants extend one of their Phase 2 projects with a new feature using a multi-step prompt, then compare the before-and-after prompts to identify what made the difference

Objective: advancing from “it functions” to “I can achieve excellent results consistently.

Break — 7 minutes

Phase 4 — Connecting Claude to Your Tools via MCP — 34 minutes

Pre-class: participants received emailed instructions to link Gmail or Google Drive prior to the session, allowing classroom time to focus on utilising the connection rather than authentication.

  • What is MCP (Model Context Protocol)? The universal plug-in system for AI tools
  • Why MCP matters: transforming Claude from a chat assistant into a connected workflow hub
  • The Connectors Directory: browsing and adding integrations directly from the Claude app
  • Desktop Extensions: one-click installations (for Claude Desktop users)
  • Live demonstration (one workflow): “Check my Google Calendar for tomorrow’s meetings and draft a preparation email for each one
  • Guided exercise: participants use their pre-connected service (or connect one live) to assign a task to Claude — e.g., “Review my recent emails regarding project updates and create a summary document
  • Key concepts: OAuth, permissions, managing tool access per conversation, security awareness, and locating new connectors

Objective: enabling participants to view Claude as a connective layer rather than solely a coding tool.

Phase 5 — Capstone & Conclusion — 35 minutes

Capstone mini-project (25 min): Each participant selects one scenario:

  1. A polished landing page or portfolio site
  2. A data analysis pipeline: upload a file, analyse it, and produce a visual report
  3. An interactive tool addressing a real problem from their workflow
  4. A connected workflow: extract data from the service linked in Phase 4, transform it, and produce a deliverable

The instructor circulates, assists with refining prompts, and showcases standout examples.

Conclusion (10 min):

  • Next steps: Claude Code CLI for terminal users, VS Code extension for developers, and Cowork for knowledge workers
  • Plans: Free versus Pro versus Max — understanding what each unlocks and which fits which use case
  • Recommended resources: official documentation, Anthropic’s prompt engineering guide, and community channels
  • Participants depart with a reference card covering prompting patterns, connector setup, and useful MCP integrations

Requirements

Requirements

An understanding of

  • Basic computer literacy: navigating files and folders, using a web browser, and installing applications
  • A general awareness of what AI assistants do (e.g., having casually used ChatGPT, Gemini, or Claude provides helpful context, but is not mandatory)

Experience with

  • No coding, programming, or terminal experience is required. This course is tailored for individuals who have never written a single line of code.
  • No prior familiarity with Claude or any other AI tool is necessary.

Technical requirements

  • Participants must bring a laptop (Mac, Windows, or Linux) equipped with a modern web browser
  • A stable internet connection
  • A Claude Pro subscription for the session duration (a 1-month gift subscription is included with course registration; setup instructions are provided prior to class)
  • Claude Desktop is recommended but not essential (the web application at claude.ai is sufficient for all exercises)
  • A Google account is recommended for the MCP connectors exercise (utilising Gmail, Google Drive, and Google Calendar), though alternative connector options are available

Audience

  • Business professionals aiming to leverage AI for enhanced productivity and automation
  • Marketers, operations managers, and analysts seeking to automate repetitive tasks
  • Founders and entrepreneurs interested in building prototypes without hiring a developer
  • Educators and researchers exploring AI-assisted workflows
  • Anyone curious about Claude’s capabilities who lacks a technical background

 4 Hours

Testimonials (1)

Related Categories