Introduction to Claude Code for Non-Developers Training Course

Phase 1 — Introducing Claude Code — 30 minutes

• An overview of Claude and what distinguishes Claude Code from standard chat interfaces
• Quick orientation: focus on the Claude app (web or desktop) for the day; CLI and other interfaces are detailed in the reference card
• Interface walkthrough: initiating a coding session and navigating the workspace
• Claude Code’s thinking process: the describe → plan → act → review cycle
• Permissions: understanding why Claude requests confirmation before creating files or executing code
• First build: instructing Claude to generate a simple styled webpage from a single-sentence description
• Iterating on results: requesting changes such as "enlarge the header," "adjust the color scheme," or "add a navigation bar"
• Guided exercise: participants initiate a session to create a personalized "About Me" webpage, refining it through subsequent instructions

Objective: Ensure all participants overcome the initial interaction hurdle and feel at ease with the interface.

Break — 7 minutes

Phase 2 — Creating Practical Applications with Plain English — 55 minutes

Three tasks of increasing complexity, completed exclusively using natural language prompts.

• Task 1 — Interactive Dashboard: Create a styled dashboard featuring sample data, charts, and statistics. Practice providing design direction such as "use a dark theme," "add a sidebar," or "make it responsive."
• Task 2 — Data Analysis: Provide a sample CSV file and ask Claude to summarize data, identify trends, locate highs and 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 illustrates that Claude can build interactive tools, not just static pages.

Following each task, the instructor will explain the backend actions taken by Claude: files created, code written, and how to interpret the output. Participants will document their most effective prompts in a shared Prompt Playbook.

Break — 7 minutes

Phase 3 — Enhancing Efficiency with Claude Code — 35 minutes

• The art of effective prompting: distinguishing between specific and vague instructions
• Live demonstration: a side-by-side comparison of weak versus strong prompts for the same task
• Iterating and refining: asking Claude to explain decisions, revert changes, or try alternative approaches
• Working with uploaded files: tasks like "read this document and summarize it" or "convert this spreadsheet into a chart"
• Multi-step workflows: chaining requests to produce complex outputs
• Understanding costs and usage: insights into tokens, context windows, and subscription tiers
• Determining when to use Claude Code versus standard Claude chat
• Guided exercise: participants expand a Phase 2 project with a new feature using a multi-step prompt, then compare the before-and-after prompts to identify key differences

Objective: Transition from "it works" to consistently achieving high-quality results.

Break — 7 minutes

Phase 4 — Integrating Claude with Your Tools via MCP — 34 minutes

Pre-class: Participants received instructions to connect Gmail or Google Drive prior to the session, allowing class time to focus on utilizing the connection rather than handling authentication.

• What is MCP (Model Context Protocol)? The universal connection system for AI tools
• The value of MCP: evolving Claude from a chat assistant into a connected workflow hub
• The Connectors Directory: browsing and adding integrations directly within the Claude app
• Desktop Extensions: one-click installation options for Claude Desktop users
• Live demonstration (single 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., "Read 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: Participants will view Claude as a connective layer rather than just a coding tool.

Phase 5 — Capstone Project & Conclusion — 35 minutes

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

1. A polished landing page or portfolio site
2. A data analysis pipeline: uploading a file, analyzing it, and producing a visual report
3. An interactive tool solving a specific problem in their workflow
4. A connected workflow: retrieving data from the service connected in Phase 4, transforming it, and generating a deliverable

The instructor will circulate to assist with prompt refinement and highlight exceptional examples.

Wrap-up (10 minutes):

• Next steps: Claude Code CLI for terminal users, VS Code extension for developers, and Cowork for knowledge workers
• Subscription plans: Free vs. Pro vs. Max — understanding what each tier offers and which suits specific use cases
• Recommended resources: official documentation, Anthropic’s prompt engineering guide, and community channels
• Participants will take away a reference card detailing prompting patterns, connector setup, and useful MCP integrations