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 suite: claude.ai, Claude Desktop, Claude Code (CLI), and their interrelationships
• Interface overview: navigating the Claude app, initiating a coding session, and familiarizing with the workspace
• Claude Code's logic: the describe → plan → act → review cycle
• Permission management: understanding why Claude requests confirmation before creating files or executing code
• Initial project: instructing Claude to generate a simple styled webpage from a single sentence
• Iterative refinement: adjusting elements such as header size, color scheme, and adding navigation bars
• Guided exercise: Participants open the Claude app, start a Claude Code session, and build a personalized “About Me” webpage by describing their desired features in plain English, practicing refinements through follow-up instructions.

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

Break — 10 minutes

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

This section forms the core of the morning session, where participants complete four progressively complex tasks 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 such as “use a dark theme,” “add a sidebar,” or “make it responsive.”
• Task 2 — Data analysis: Provide a sample CSV file to Claude and request a data summary, trend identification, highest and lowest values, and a visual chart. This demonstrates how Claude writes and executes code on the user's behalf.
• Task 3 — Document generation: Ask Claude to read a data file and generate a formatted report, such as a sales summary, project status update, or meeting recap. This highlights Claude's ability to transform raw data into polished deliverables.
• Task 4 — Automation utility: Instruct Claude to build a simple utility like 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 clarify the background actions: files created, code written, and how to interpret the output. Participants will document their most effective prompts in a shared Prompt Playbook.

Break — 10 minutes

Phase 3 — Optimizing Interaction with Claude Code — 50 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 exploring alternative approaches
• Handling uploaded files: Instructing Claude to summarize documents or convert spreadsheets into charts
• Multi-step workflows: Chaining requests to construct complex outputs (e.g., “first analyze this data, then build a dashboard from the results”)
• Understanding costs and usage: Insights into tokens, context windows, and subscription tiers
• Distinguishing when to use Claude Code versus standard Claude chat
• Guided exercise: Participants extend one of their Phase 2 projects with two new features using a multi-step prompt chain, then compare their initial and refined prompts to identify key improvements.

Objective: Transition from “it works” to consistently achieving high-quality results.

Break — 10 minutes

Phase 4 — Collaborative Workflows: Live Build Session — 60 minutes

This phase shifts the group's energy from individual practice to collective construction. While the instructor leads, participants direct the process by naming real challenges from their roles, suggesting prompt ideas, and debating trade-offs. The aim is to develop prompt judgment by observing an experienced professional navigate uncertainty in real time.

The session is structured around three workflow archetypes:

• Transform — Convert input X into output Y (e.g., meeting notes to action items; raw data to summary emails; customer feedback to themed reports)
• Draft — Generate initial versions of documents typically written from scratch (proposals, emails, job descriptions, social media posts)
• Analyze — Interrogate documents or datasets that lack time for detailed review (40-page reports, survey response spreadsheets, contracts)

Setup and framing (10 min): The instructor introduces the three archetypes and explains the session mechanics. 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 challenge and builds it live, incorporating prompt ideas, pushbacks, and refinements suggested by the room. The instructor narrates every decision, concluding with a working prompt template for the participant whose problem was addressed.

Live build #2 — Draft or Analyze workflow (20 min): Same format, applying a different archetype to another participant's challenge.

Reflection & share-back (10 min): Participants note one surprising prompting move, one aspect they would improve, and one pattern they will retain. A brief group share follows, with 3-4 participants contributing. The instructor connects these observations to the broader Prompt Playbook.

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

• Introduction to MCP (Model Context Protocol): The universal integration system for AI tools
• The value 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 requiring no configuration files

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 to accommodate different 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 (a test URL will be provided by the instructor)
• Option C: Install a Desktop Extension from the marketplace (for Claude Desktop users)

Participants will then assign Claude a task utilizing the connected service, such as, “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: Participants will view Claude as a connective layer between their existing services, rather than just a coding tool.

Break — 10 minutes

Phase 6 — Capstone & Future Directions — 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 will circulate to help refine prompts and showcase standout examples to the group.

Showcase and wrap-up (20 min):

• 6-8 participants share their creations (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
• Subscription plans: Free vs. Pro vs. Max — understanding what each tier unlocks and which fits specific use cases
• Best practices recap: Reviewing the most effective Prompt Playbook patterns from 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