Claude Code for Non-Developers Training Course

Phase 1 — Introducing Claude Code — 55 minutes

• An overview of what Claude is and how Claude Code differs from standard chat interactions
• The Claude product ecosystem: claude.ai, Claude Desktop, Claude Code (CLI), and the relationship between these components
• Interface navigation: exploring the Claude app, initiating a coding session, and understanding the workspace
• Understanding Claude Code’s logic: the describe → plan → act → review cycle
• Permission management: understanding why Claude requests approval before creating files or executing code
• Initial project: instructing Claude to create a simple styled webpage from a single-sentence description
• Iterating on results: refining outputs with instructions such as “make the header bigger,” “change the color scheme,” or “add a navigation bar”
• Guided exercise:  Participants will open the Claude app, start a Claude Code session, and build a personalized “About Me” webpage by describing their requirements in plain English. They will then practice refining the result through subsequent instructions.

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

Break — 10 minutes

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

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

• Task 1 — Interactive dashboard:  Request Claude Code to build a styled dashboard displaying sample data with charts, statistics, and a clean layout. Participants will practice providing design direction, such as “use a dark theme,” “add a sidebar,” or “make it responsive.”
• Task 2 — Data analysis:  Provide Claude with a sample CSV file and request it to summarize the data, identify trends, locate extreme values, and generate a visual chart. This demonstrates Claude’s ability to write and execute code on the user's 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:  Instruct Claude to 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.

Following each task, the instructor will explain the underlying actions: which files were created, the 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 Workflows with Claude Code — 50 minutes

• The art of effective prompting: distinguishing between specific and vague instructions
• Live demonstration: a side-by-side comparison of weak versus strong prompts applied to the same task
• Iteration and refinement: requesting explanations of choices, undoing changes, or trying 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 generate complex outputs (e.g., “first analyze this data, then build a dashboard from the results”)
• Understanding costs and usage: an overview of tokens, context windows, and subscription tiers
• Distinguishing when to use Claude Code versus standard Claude chat
• Guided exercise:  Participants will select a project from Phase 2 and extend it with two new features using a multi-step prompt chain. They will then compare their pre- and post-improvement prompts to identify key differences.

Objective: To progress from merely getting it to work to consistently achieving high-quality results.

Break — 10 minutes

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

This phase shifts the dynamic from individual practice to group collaboration. While the instructor guides the process, participants drive the direction by identifying real-world problems from their jobs, suggesting prompt ideas, and debating trade-offs. The aim is to cultivate prompt judgment by observing a skilled practitioner navigate uncertainty in real time.

The session is structured around three workflow archetypes:

• Transform — converting input X into output Y (e.g., meeting notes to action items, raw data to a summary email, or customer feedback to a themed report)
• Draft — generating an initial version of content typically written from scratch (e.g., proposals, emails, job descriptions, or social media posts)
• Analyze — interrogating documents or datasets that are too time-consuming to read thoroughly (e.g., a 40-page report, survey responses, or a 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, with the room contributing prompt ideas, feedback, and refinements. The instructor narrates every decision. The session concludes with a reusable prompt template for the participant who submitted the problem.

Live build #2 — Draft or Analyze workflow (20 min):  Following the same format, this build focuses on a different archetype and a different participant’s challenge.

Reflection & share-back (10 min):  Participants take a moment to note one surprising prompting technique, one improvement they would make, and one pattern they are taking away. A brief group share follows, with 3-4 participants speaking. 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 that require no manual configuration

Live demo:  The instructor connects Claude to two services using 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 will 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) — simple 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 — for example, “Read my recent emails about project updates and create a summary document.”

Key concepts covered include:

• Connector mechanics: OAuth authentication, permissions, and the scope of access granted
• Managing tool access: enabling, disabling, and controlling which connectors Claude can use in specific conversations
• Security best practices: connecting only to trusted services and reviewing tool permissions
• The MCP ecosystem: sources for finding new connectors, extensions, and community-built servers

Objective: To help participants view Claude as a connective layer between the services they already use, rather than just a coding tool.

Break — 10 minutes

Phase 6 — Capstone & Future 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: uploading a file, having Claude analyze it, and producing a visual report
3. An interactive tool that solves a real problem in their workflow (e.g., calculator, tracker, converter, or quiz)
4. A connected workflow: pulling data from a connected service, transforming it, and producing a deliverable (e.g., “read my calendar for next week and build a visual schedule”)

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

Showcase and wrap-up (20 min):

• 6-8 participants share their builds (2-3 minutes each)
• Next steps: exploring the Claude Code CLI for terminal users, the VS Code extension for developers, and Cowork for knowledge workers
• The MCP ecosystem: strategies for finding and evaluating new connectors, extensions, and community servers
• Subscription plans: comparing Free, Pro, and Max tiers to determine the best fit for specific use cases
• Best practices recap: reviewing the most effective Prompt Playbook patterns demonstrated 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