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
• 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 Claude Code process: the describe → plan → act → review cycle
• Permission management: understanding why Claude requests approval before creating files or executing code
• Initial build: instructing Claude to create a simple, styled webpage from a one-sentence description
• Refining results: providing follow-up instructions such as “make the header larger,” “adjust the color palette,” 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, then refine the output through subsequent instructions.

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

Break — 10 minutes

Phase 2 — Creating Practical Solutions with Natural Language — 70 minutes

This segment forms the core of the morning session, where participants complete four tasks of increasing complexity using only natural language prompts.

• Task 1 — Interactive Dashboard: Request that Claude Code builds a styled dashboard displaying sample data with charts, statistics, and a clean layout. Practice providing design directions 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 summary of the data, identification of trends, extraction of highest and lowest values, and generation of a visual chart. This demonstrates how Claude writes and executes code on your behalf.
• Task 3 — Document Generation: Instruct 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: Ask 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 explains the backend processes: which files were created, what code was generated, and how to interpret the output. Participants document their most effective prompts in a shared Prompt Playbook.

Break — 10 minutes

Phase 3 — Optimizing Interaction with Claude Code — 50 minutes

• Effective prompting techniques: specific versus vague instructions
• Live demonstration: a side-by-side comparison of weak and strong prompts for the same task
• Iterative refinement: requesting explanations of Claude’s choices, undoing changes, or trying alternative approaches
• Utilizing uploaded files: commands 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., “analyze this data first, then build a dashboard from the results”)
• Understanding usage metrics: how tokens, context windows, and subscription tiers function
• Deciding 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 before-and-after prompts to identify the factors that improved the result.

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

Break — 10 minutes

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

This phase shifts the classroom dynamic from individual practice to group collaboration. The instructor leads the process, but participants drive the direction by identifying real problems from their own roles, suggesting prompt ideas, and debating trade-offs. The goal is to develop prompt judgment by observing an expert 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 → themed report)
• Draft — Generate an initial version of documents typically written from scratch (e.g., proposals, emails, job descriptions, social media posts)
• Analyze — Interrogate documents or datasets that are too time-consuming to read carefully (e.g., a 40-page report, survey spreadsheet, or contract)

Setup and Introduction (10 min): The instructor presents 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 a submitted problem and builds it live while the room suggests prompt ideas, objections, and refinements. The instructor narrates each decision. The session concludes with a working prompt template retained by the participant who submitted the problem.

Live Build #2 — Draft or Analyze Workflow (20 min): Same format, applying a different archetype to a different participant’s problem.

Reflection and Share-Back (10 min): Participants take a moment to note one surprising prompting technique, one area for improvement, and one key takeaway. A brief group share involves 3-4 participants. 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 framework 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 one.”
2. “Read the latest updates from our project board and write a status summary.”
3. “Retrieve data from this connected service and generate 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) — simple click, authenticate, and start using
• 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, 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 uses 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 should view Claude as a connective layer for their existing services, not merely 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 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 generate a visual report
3. An interactive tool that solves a real workflow problem (e.g., calculator, tracker, converter, quiz)
4. A connected workflow: Retrieve 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 highlights standout examples to the group.

Showcase and Wrap-Up (20 min):

• 6-8 participants share their creations (2-3 minutes each)
• Future pathways: Claude Code CLI for terminal users, VS Code extension for developers, Cowork for knowledge workers
• The MCP ecosystem: Discovering and evaluating new connectors, extensions, and community servers
• Subscription plans: Free vs. Pro vs. Max — understanding what each unlocks and which suits different use cases
• Best practices recap: Reviewing 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 featuring key prompting patterns, connector setup steps, and a curated list of useful MCP integrations