Introduction to Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 30 minutes

• An overview of what Claude is and how Claude Code differs from standard chat interfaces
• Quick orientation: the course uses the Claude app (web or desktop) for today’s session; the CLI and other interfaces are detailed in the reference card
• Interface tour: initiating a coding session and understanding the workspace
• How Claude Code operates: the describe → plan → act → review cycle
• Understanding permissions: why Claude seeks confirmation before creating files or executing code
• First build exercise: asking Claude to create a simple styled webpage based on a single-sentence description
• Refining results: instructions such as “make the header larger,” “change the color scheme,” or “add a navigation bar”
• Guided exercise: Participants start a session and build a personalized “About Me” webpage, refining the output through follow-up instructions

Objective: Ensure everyone overcomes the initial interaction barrier and feels comfortable with the interface.

Break — 7 minutes

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

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

• Task 1 — Interactive dashboard: Create a styled dashboard with 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 it, identify trends, find high and low points, 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.

After each task, the instructor highlights Claude’s backend 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: specific versus vague instructions
• Live demo: Side-by-side comparison of weak versus strong prompts for the same task
• Iterating and refining: Asking Claude to explain choices, undo changes, or try alternative approaches
• Working with uploaded files: Commands 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: How tokens, context windows, and subscription tiers function
• 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 pre- and post-prompts to identify key differences

Objective: Progress from “it works” to “I can consistently achieve excellent 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 before the session, allowing classroom time to focus on utilizing the connection rather than authentication.

• What is MCP (Model Context Protocol)? The universal integration system for AI tools
• The importance 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 — for example, “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, rather than 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 real problem within their workflow
4. A connected workflow: pulling data from the service connected in Phase 4, transforming it, and producing a deliverable

The instructor circulates to assist with prompt refinement and showcases outstanding examples.

Conclusion (10 min):

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