Introduction to Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 30 minutes

• Overview of Claude and what distinguishes Claude Code from standard chat interfaces
• Initial orientation: utilizing the Claude app (web or desktop); the CLI and other interfaces are detailed in the reference card
• Interface walkthrough: initiating a coding session and navigating the workspace
• Claude Code’s reasoning process: the describe → plan → act → review loop
• Permission management: understanding why Claude requests confirmation before creating files or executing code
• First build: instructing Claude to create a simple, styled webpage from a single-sentence description
• Refining results: giving instructions like “make the header bigger,” “adjust the color scheme,” or “add a navigation bar”
• Guided exercise: participants start a session and construct a personalized “About Me” webpage, refining it through iterative instructions

Objective: Ensure all participants overcome the initial interaction barrier and feel comfortable with the interface.

Break — 7 minutes

Phase 2 — Creating Real Projects with Plain English — 55 minutes

Three progressively complex tasks accomplished exclusively through natural language prompts.

• Task 1 — Interactive dashboard: A styled dashboard featuring sample data, charts, and statistics. Practice providing design direction: “apply a dark theme,” “add a sidebar,” or “make it responsive.”
• Task 2 — Data analysis: Provide a sample CSV and ask Claude to summarize it, identify trends, locate highs/lows, and generate a visual chart. This demonstrates Claude writing and executing code on your behalf.
• Task 3 — Automation tool: Build a simple utility—such as a unit converter, quiz app, or budget calculator. This introduces the concept that Claude can create interactive tools, not just static pages.

Following each task, the instructor explains Claude’s background actions: files created, code written, and how to interpret the output. Participants record their most effective prompts in a shared Prompt Playbook.

Break — 7 minutes

Phase 3 — Optimizing Workflows with Claude Code — 35 minutes

• The art of effective prompting: contrasting specific vs. vague instructions
• Live demonstration: a side-by-side comparison of weak and strong prompts for the same task
• Iteration and refinement: asking Claude to explain choices, revert changes, or adopt a different approach
• Handling uploaded files: “read this document and summarize it,” or “convert this spreadsheet into a chart”
• Multi-step workflows: chaining requests to produce complex outputs
• Cost and usage management: understanding tokens, context windows, and subscription tiers
• Determining when to use Claude Code versus standard Claude chat
• Guided exercise: participants extend a Phase 2 project with a new feature using a multi-step prompt, then compare before-and-after prompts to identify key differences

Objective: Progress from “it works” to “I can consistently achieve high-quality results.”

Break — 7 minutes

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

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

• Understanding MCP (Model Context Protocol): The universal plug system for AI tools
• The value of MCP: Transforming 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 installations (for Claude Desktop users)
• Live demo (single workflow): “Check my Google Calendar for tomorrow’s meetings and draft a prep 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 about 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, not merely 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: uploading a file, analyzing it, and producing a visual report
3. An interactive tool solving a real-world problem in their workflow
4. A connected workflow: pulling data from a service connected in Phase 4, transforming it, and generating a deliverable

The instructor will circulate to assist with prompt refinement and showcase notable examples.

Wrap-up (10 min):

• 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—what each unlocks and which fits specific use cases
• Recommended resources: official documentation, Anthropic’s prompt engineering guide, and community channels
• Participants will leave with a reference card covering prompting patterns, connector setup, and useful MCP integrations