Introduction to Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 30 minutes

• An overview of Claude and the distinct features that set Claude Code apart from standard chat interactions
• Quick orientation: The session utilizes the Claude application (web or desktop); the CLI and other interfaces are detailed in the reference card
• Interface walkthrough: Initiating a coding session and navigating the workspace
• How Claude Code operates: The describe → plan → act → review cycle
• Understanding permissions: The rationale behind Claude’s requests before creating files or executing code
• First project: Instructing Claude to generate a simple styled webpage from 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 initiate a session and build a personalized “About Me” webpage, refining it through follow-up instructions

Objective: To ensure all participants have overcome the initial interaction barrier and feel comfortable with the interface.

Break — 7 minutes

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

Three progressively complex tasks performed exclusively through natural language prompts.

• Task 1 — Interactive dashboard: Designing a styled dashboard with sample data, charts, and statistics. Practicing design directives such as “use a dark theme,” “add a sidebar,” or “make it responsive.”
• Task 2 — Data analysis: Providing a sample CSV file and requesting Claude to summarize it, identify trends, pinpoint highs and lows, and generate a visual chart. This demonstrates Claude writing and executing code on the user’s 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 highlight the backend actions taken by Claude, including 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 Workflows with Claude Code — 35 minutes

• The art of effective prompting: Specific vs. vague instructions
• Live demonstration: A side-by-side comparison of weak and strong prompts applied to the same task
• Iteration and refinement: Requesting explanations for choices, undoing changes, or exploring 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 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 enhance one of their Phase 2 projects with a new feature using a multi-step prompt, then compare the before-and-after prompts to identify the key differences

Objective: To elevate skills from “it works” to “I can achieve excellent results consistently.”

Break — 7 minutes

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

Pre-class preparation: Participants received email instructions to connect Gmail or Google Drive prior to the session, ensuring classroom time is dedicated to utilizing the connection rather than authentication.

• What is MCP (Model Context Protocol)? The universal integration system for AI tools
• The significance of MCP: Transforming Claude from a chat assistant into a central hub for connected workflows
• The Connectors Directory: Browsing and adding integrations directly within the Claude application
• Desktop Extensions: One-click installations (available 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, such as “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: To help participants 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 of the following scenarios:

1. A polished landing page or portfolio site
2. A data analysis pipeline: Uploading a file, analyzing it, and generating a visual report
3. An interactive tool that solves a real-world problem in their workflow
4. A connected workflow: Retrieving data from the service connected in Phase 4, transforming it, and producing a deliverable

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

Conclusion (10 min):

• Next steps: Claude Code CLI for terminal users, the VS Code extension for developers, and Cowork for knowledge workers
• Subscription plans: Free vs. Pro vs. Max — detailing what each unlocks and the ideal use case for each
• 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