Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 55 minutes

• An 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 respective roles
• Interface walkthrough: navigating the Claude app, initiating a coding session, and familiarizing with the workspace
• Cognitive processes of Claude Code: the describe → plan → act → review cycle
• Permission management: understanding why Claude seeks approval before creating files or executing code
• First build experience: instructing Claude to create a simple, styled webpage based on a single-sentence description
• Iterating on outputs: requests such as "enlarge the header," "modify the color palette," or "add a navigation bar"
• Guided exercise: Participants launch the Claude app, start a Claude Code session, and build a personalized "About Me" webpage by describing their requirements in plain English. They practice refining outcomes through subsequent instructions.

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

Break — 10 minutes

Phase 2 — Developing Practical Solutions with Natural Language — 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 guidance such as "apply a dark theme," "include a sidebar," or "ensure responsiveness."
• Task 2 — Data Analysis: Provide a sample CSV file to Claude and request it to summarize the data, identify trends, locate peak and trough values, and generate 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 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 Utility: Request Claude to build a simple utility, such as a unit converter, quiz application, or budget calculator. This introduces the concept that Claude can create interactive tools, not just static pages.

Following each task, the instructor explains the backend processes: files created, code written, and how to interpret the output. Participants document their most effective prompts in a shared Prompt Playbook.

Break — 10 minutes

Phase 3 — Optimizing Interactions with Claude Code — 50 minutes

• Prompting techniques: the difference between specific and vague instructions
• Live demonstration: comparing weak and strong prompts for the same task side-by-side
• Iteration and refinement: requesting explanations of choices, reverting changes, or trying alternative approaches
• Handling uploaded files: commands 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")
• Cost and usage management: understanding tokens, context windows, and subscription tiers
• Choosing between Claude Code and standard Claude chat
• Guided exercise: Participants select one Phase 2 project and extend it with two new features using a multi-step prompt chain. They then compare their initial and refined prompts to identify the factors that improved the outcome.

Objective: Transition 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 shifts the dynamic of the room. Rather than individual practice, the group builds together. The instructor guides the process, but participants direct the content by naming real problems from their jobs, suggesting prompt ideas, and debating trade-offs. The goal is to learn prompt judgment by observing a skilled professional navigate uncertainty in real time.

The session is structured around three workflow archetypes:

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

Setup and Framing (10 min): The instructor introduces the three archetypes and explains the session mechanics. Participants submit real workflow challenges from their roles 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 group suggests 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, and a different participant's problem.

Reflection & Sharing (10 min): Participants take a moment to note one surprising prompting technique, one aspect they would improve, and one pattern they will apply moving forward. A brief group sharing session follows with 3-4 contributors. The instructor links 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 (no configuration files required)

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

1. "Check my Google Calendar for tomorrow's meetings and draft a preparation email for each"
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"

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) — a simple click, authenticate, and go process
• Option B: Add a custom connector by pasting an MCP server URL (provided by the instructor for testing)
• Option C: Install a Desktop Extension from the marketplace (for Claude Desktop users)

Participants then assign a task to Claude utilizing the connected service — for example, "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: discovering new connectors, extensions, and community-built servers

Objective: Participants will 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 solving a real workflow problem (calculator, tracker, converter, or 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 present their builds (2-3 minutes each)
• Future paths: 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 — what each unlocks and which suits 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