Introduction to Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 30 minutes

• Defining Claude and distinguishing Claude Code from standard chat interactions
• Quick orientation: Today’s focus is the Claude app (web or desktop); the CLI and other interfaces are detailed in the reference card
• Interface overview: Initiating a coding session and understanding the workspace
• Claude Code's reasoning process: The describe → plan → act → review cycle
• Understanding permissions: Why Claude seeks confirmation before creating files or executing code
• First build: Instructing Claude to create a simple styled webpage from a single-sentence description
• Refining results: Adjustments such as “make the header bigger,” “change the color scheme,” or “add a navigation bar”
• Guided exercise: Participants initiate a session and build a personalized “About Me” webpage, refining it through follow-up instructions

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

Break — 7 minutes

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

Three progressively complex tasks executed using only natural language prompts.

• Task 1 — Interactive dashboard: Design 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: Upload a sample CSV file and ask Claude to summarize it, identify trends, find 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 the background actions performed by Claude: 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 craft of effective prompting: Comparing specific versus vague instructions
• Live demonstration: A side-by-side comparison of weak and strong prompts applied to the same task
• Iteration and refinement: Requesting explanations of choices, undoing changes, or trying alternative approaches
• Working with uploaded files: Tasks such as “read this document and summarize it” or “convert this spreadsheet into a chart”
• Multi-step workflows: Chaining requests to construct complex outputs
• Understanding costs and usage: How tokens, context windows, and subscription tiers function
• Deciding when to use Claude Code versus standard Claude chat
• Guided exercise: Participants extend a Phase 2 project by adding a new feature using a multi-step prompt, then compare before-and-after prompts to identify key differences

Objective: Advance 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: Participants received email instructions to connect Gmail or Google Drive prior to the session, ensuring class time is spent utilizing the connection rather than handling authentication.

• Understanding MCP (Model Context Protocol): The universal connection system for AI tools
• The significance 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 demonstration (one 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: Enable participants to view Claude as a connective layer, not just 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 specific problem in their workflow
4. A connected workflow: Pulling data from the service connected in Phase 4, transforming it, and producing a deliverable

The instructor circulates, assists with prompt refinement, and highlights standout examples.

Conclusion (10 min):

• Next steps: Claude Code CLI for terminal users, VS Code extension for developers, Cowork for knowledge workers
• Plans: Free vs. Pro vs. Max—what each tier unlocks and which suits specific use cases
• Recommended resources: Official documentation, Anthropic’s prompt engineering guide, and community channels
• Participants receive a reference card covering prompting patterns, connector setup, and useful MCP integrations