Introduction to Claude Code for Non-Developers Training Course

Phase 1 — Meeting Claude Code — 30 minutes

• An overview of Claude and the distinctions between Claude Code and standard chat interfaces
• Quick orientation: focusing on the Claude app (web or desktop) for today’s session, with the CLI and other platforms detailed in the reference card
• Interface walkthrough: initiating a coding session and navigating the workspace
• Understanding Claude Code’s process: the describe → plan → act → review loop
• Navigating permissions: understanding why Claude requests approval before creating files or executing code
• Your first creation: instructing Claude to generate a simple styled webpage from a single-sentence description
• Refining results: issuing commands such as “make the header larger,” “change the color scheme,” or “add a navigation bar”
• Guided exercise: participants will initiate a session and create a personalized “About Me” webpage, refining it through iterative instructions

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

Break — 7 minutes

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

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

• Task 1 — Interactive dashboard: Designing a styled dashboard with sample data, charts, and statistics. Practice providing design direction with prompts like “use a dark theme,” “add a sidebar,” or “make it responsive.”
• Task 2 — Data analysis: Providing a sample CSV file and asking Claude to summarize it, identify trends, detect highs and lows, and generate visual charts. This demonstrates Claude writing and executing code on your behalf.
• Task 3 — Automation tool: Building 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 will explain the underlying actions: 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 — Optimizing Claude Code Usage — 35 minutes

• The art of effective prompting: specific versus vague instructions
• Live demonstration: comparing weak and strong prompts side-by-side on the same task
• Iteration and refinement: asking Claude to explain choices, revert changes, or try alternative approaches
• Working with uploaded files: instructions such as “read this document and summarize it” or “convert this spreadsheet into a chart”
• Multi-step workflows: chaining requests to generate complex outputs
• Understanding cost and usage: an explanation of tokens, context windows, and subscription tiers
• Determining when to use Claude Code versus standard Claude chat
• Guided exercise: participants will expand one of their Phase 2 projects with a new feature using a multi-step prompt, then compare the initial and improved prompts to identify key differences

Objective: Progress from “it works” to achieving consistently excellent 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 integration system for AI tools
• The importance 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 installations (for Claude Desktop users)
• Live demonstration (single workflow): “Check my Google Calendar for tomorrow’s meetings and draft a preparation email for each”
• Guided exercise: participants will use their pre-connected service (or connect one live) to assign a task to Claude, such as “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, rather than just a coding tool.

Phase 5 — Capstone & Wrap-Up — 35 minutes

Capstone mini-project (25 min): Each participant selects one of the following scenarios:

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 that solves a real problem within their workflow
4. A connected workflow: retrieving data from the service connected in Phase 4, transforming it, and generating a final deliverable

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

Wrap-up (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 specific use cases
• Recommended resources: official documentation, Anthropic’s prompt engineering guide, and community channels
• Participants will leave with a reference card detailing prompting patterns, connector setup, and useful MCP integrations