Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 55 minutes

• An overview of Claude and the distinct features of Claude Code compared to standard chat interfaces
• The Claude product ecosystem: claude.ai, Claude Desktop, Claude Code (CLI), and their interrelationships
• Interface navigation: exploring the Claude app, initiating a coding session, and understanding the workspace
• The thought process of Claude Code: the describe → plan → act → review cycle
• Understanding permissions: the rationale behind Claude requesting confirmation before creating files or executing code
• First build: instructing Claude to create a simple, styled webpage from a single-sentence description
• Iterating on results: refining outputs with instructions 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 build a personalized “About Me” webpage by describing their needs in plain English. They practice refining the output 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 Real Projects with Plain English — 70 minutes

This segment 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, 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 a data summary, trend identification, extraction of highest and lowest values, and generation of 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 showcases Claude's ability to transform 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 that Claude can create interactive tools, not just static pages.

Following each task, the instructor highlights the background actions performed by Claude: the files created, the 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 Workflow with Claude Code — 50 minutes

• The craft 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
• Iterating and refining: Asking Claude to explain its decisions, undo changes, or explore alternative approaches
• Working with uploaded files: Requests such as “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 cost and usage: An explanation of tokens, context windows, and subscription tiers
• Distinguishing when to use Claude Code versus standard Claude chat
• Guided exercise: participants select one of their Phase 2 projects and expand it with two new features using a multi-step prompt chain. They then compare their previous and refined prompts to identify key differences.

Objective: Transition from “it works” to “I can consistently achieve high-quality results.”

Break — 10 minutes

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

This phase changes the dynamic in the room. Instead of individual practice, the group builds together. While the instructor guides the process, participants direct the focus — identifying real problems from their jobs, suggesting prompt ideas, and discussing tradeoffs. The aim is to learn prompt judgment by observing a skilled practitioner navigate uncertainty in real time.

The session is structured around three workflow archetypes:

• Transform — Convert input X to output Y (e.g., meeting notes → action items; raw data → summary email; customer feedback → thematic 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 detailed reading (e.g., 40-page reports, survey 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 problem and builds it live, with the room contributing prompt ideas, feedback, and refinements. The instructor narrates every decision. The session concludes with a working prompt template that the submitting participant retains.

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

Reflection & share-back (10 min): Participants reflect on one surprising prompting move, one alternative approach, and one pattern they will take away. A brief group share follows (3-4 participants). The instructor links these observations to the broader Prompt Playbook.

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

• Understanding MCP (Model Context Protocol): The universal integration 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 within 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 to suit 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 is provided by the instructor)
• Option C: Install a Desktop Extension from the marketplace (for Claude Desktop users)

Participants 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 nature 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 perceive Claude as a connective layer for all existing services, rather than just a coding tool.

Break — 10 minutes

Phase 6 — Capstone Project & Next Steps — 65 minutes

Capstone mini-project (45 min): Each participant selects one scenario and builds it using 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 specific workflow problem (calculator, tracker, converter, 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 circulates among participants, assisting with prompt refinement and showcasing standout examples to the group.

Showcase and wrap-up (20 min):

• 6-8 participants present their creations (2-3 minutes each)
• Future pathways: Claude Code CLI for terminal users, VS Code extension for developers, and 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