Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 55 minutes

• Overview of Claude and the distinctions between Claude Code and standard chat interfaces
• The Claude product ecosystem: claude.ai, Claude Desktop, Claude Code (CLI), and their interrelationships
• Interface tour: navigating the Claude app, initiating a coding session, and understanding the workspace
• Claude Code’s logic: the describe → plan → act → review loop
• Understanding permissions: why Claude requests confirmation before creating files or executing code
• First build: instructing Claude to generate a simple styled webpage from a single-sentence description
• Refining results: commands like "make the header bigger," "change the color scheme," or "add a navigation bar"
• Guided exercise: Participants open the Claude app, start a Claude Code session, and create a personalized "About Me" webpage by describing their requirements in plain English. They practice refining the outcome through follow-up instructions.

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

Break — 10 minutes

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

This section forms the core of the morning session. Participants complete four tasks of increasing complexity using only natural language prompts.

• Task 1 — Interactive dashboard: Instruct Claude Code to build a styled dashboard displaying sample data with charts, statistics, and a clean layout. Practice providing design direction: "use a dark theme," "add a sidebar," or "make it responsive."
• Task 2 — Data analysis: Provide Claude with a sample CSV file and request a data summary, trend identification, extreme value detection, and visual chart generation. This demonstrates Claude's ability to write and execute code on your behalf.
• Task 3 — Document generator: Ask Claude to read a data file and produce a formatted report—such as a sales summary, project status update, or meeting recap. This illustrates how Claude transforms raw data into polished deliverables.
• Task 4 — Automation tool: Request that Claude build a simple utility, such as a unit converter, quiz app, or budget calculator. This introduces the concept of building interactive tools, not just static pages.

Following each task, the instructor explains the background processes: which files were created, what code was written, and how to interpret the output. Participants record their most effective prompts in a shared Prompt Playbook.

Break — 10 minutes

Phase 3 — Enhancing Efficiency with Claude Code — 50 minutes

• The art of effective prompting: specific versus vague instructions
• Live demonstration: Side-by-side comparison of weak and strong prompts applied to the same task
• Iteration and refinement: Asking Claude to explain choices, undo changes, or try alternative approaches
• Working with uploaded files: Tasks like "read this document and summarize it" or "convert this spreadsheet into a chart"
• Multi-step workflows: Chaining requests to create complex outputs (e.g., "first analyze this data, then build a dashboard from the results")
• Understanding cost and usage: How tokens, context windows, and subscription tiers function
• Determining when to use Claude Code versus standard Claude chat
• Guided exercise: Participants select a Phase 2 project and extend it with two new features using a multi-step prompt chain. They then compare their pre- and post-prompts to identify the factors driving improved results.

Objective: Progress from "it works" to "I can consistently achieve excellent results."

Break — 10 minutes

Phase 4 — Your Claude Workflows: Live Build Session — 60 minutes

This phase elevates the energy in the room. Instead of individual practice, the group builds together. The instructor leads, but participants direct the process—naming real problems from their own roles, suggesting prompt ideas, and debating tradeoffs. The aim is to develop prompt judgment by observing a skilled navigator manage uncertainty in real time.

Three workflow archetypes structure the session:

• Transform — Take input X and produce output Y (e.g., meeting notes → action items; raw data → summary email; customer feedback → themed report)
• Draft — Generate an initial version of content typically written from scratch (proposals, emails, job descriptions, social posts)
• Analyze — Interrogate documents or datasets that lack the time for careful reading (e.g., a 40-page report, survey response spreadsheets, contracts)

Setup and framing (10 min): The instructor introduces the three archetypes and explains the session structure. Participants submit real workflow challenges from their jobs via a shared document or chat.

Live build #1 — Transform workflow (20 min): The instructor selects one submitted problem and builds it live while the room offers prompt ideas, pushbacks, and refinements. The instructor narrates every decision. The session concludes with a working prompt template retained by the participant whose problem was solved.

Live build #2 — Draft or Analyze workflow (20 min): Same format, different archetype, addressing a different participant’s problem.

Reflection & share-back (10 min): Participants take a moment to note one surprising prompting move, one area for improvement, and one pattern to take away. A quick group share follows—3-4 voices, not everyone. The instructor connects these observations to the broader Prompt Playbook.

Phase 5 — Integrating Claude with Your Tools via MCP — 50 minutes

• What is MCP (Model Context Protocol)? The universal plug-in 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 from the Claude app
• Desktop Extensions: One-click installations for Claude Desktop (no configuration files required)

Live demo: The instructor connects Claude to two services through the Connectors UI and demonstrates cross-tool workflows:

1. "Check my Google Calendar for tomorrow’s meetings and draft a prep email for each one"
2. "Read the latest updates from our project board and write a status summary"
3. "Pull data from this connected service and build a local report from it"

Guided exercise: Participants connect Claude to at least one service. Options are provided for varying comfort levels:

• Option A: Connect a pre-built connector from the directory (e.g., Gmail, Google Drive, or a demo service) — click, authenticate, and proceed
• Option B: Add a custom connector by pasting an MCP server URL (instructor provides a test URL)
• Option C: Install a Desktop Extension from the marketplace (for Claude Desktop users)

Participants then assign Claude a task utilizing the connected service—e.g., "Read my recent emails about project updates and create a summary document."

Key concepts covered:

• Connector mechanics: OAuth authentication, permissions, and the scope of access granted
• Managing tool access: Enabling, disabling, and controlling which connectors Claude can use per conversation
• Security awareness: Connecting only to trusted services and reviewing tool permissions
• The MCP ecosystem: Locating new connectors, extensions, and community-built servers

Objective: Enable participants to view Claude as a connective layer between all services they already use, rather than just a coding tool.

Break — 10 minutes

Phase 6 — Capstone & Next Steps — 65 minutes

Capstone mini-project (45 min): Each participant selects one scenario and builds it with Claude:

1. A polished landing page or portfolio site for their team, project, or personal brand
2. A data analysis pipeline: Upload a file, have Claude analyze it, and produce a visual report
3. An interactive tool that solves a real workflow problem (calculator, tracker, converter, quiz)
4. A connected workflow: Pull data from a connected service, transform it, and produce a deliverable (e.g., "read my calendar for next week and build a visual schedule")

The instructor circulates to assist with prompt refinement and showcases standout examples to the group.

Showcase and wrap-up (20 min):

• 6-8 participants share what they built (2-3 minutes each)
• Next steps: Claude Code CLI for terminal users, VS Code extension for developers, Cowork for knowledge workers
• The MCP ecosystem: Finding and evaluating new connectors, extensions, and community servers
• Plans: Free vs. Pro vs. Max — what each tier unlocks and which fits which use case
• Best practices recap: The Prompt Playbook patterns that proved most effective during the session
• Recommended resources: Official documentation, community channels, and Anthropic’s prompt engineering guide
• Participants receive a reference card containing key prompting patterns, connector setup steps, and a curated list of useful MCP integrations