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 ecosystem: claude.ai, Claude Desktop, Claude Code (CLI), and their interrelationships
• Interface orientation: navigating the Claude app, initiating coding sessions, and understanding the workspace
• Claude Code’s reasoning process: the describe → plan → act → review cycle
• Permissions management: understanding why Claude requests approval before file creation or code execution
• Initial build: instructing Claude to generate a simple styled webpage from a single-sentence description
• Refining outputs: commands such as “make the header larger,” “modify the color scheme,” or “include a navigation bar”
• Guided exercise: Participants launch the Claude app, begin a Claude Code session, and create a personalized “About Me” webpage by describing their requirements in plain English, practicing result refinement through follow-up instructions.

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

Break — 10 minutes

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

This section forms the core of the morning session. Participants will complete four increasingly complex tasks using solely natural language prompts.

• Task 1 — Interactive dashboard: Instruct Claude Code to develop 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 summary of the data, identification of trends, extraction of highest and lowest values, and generation of a visual chart. This demonstrates Claude’s ability to write and execute code on your 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: Request Claude to build a simple utility like a unit converter, quiz app, or budget calculator. This introduces the capability of Claude to create interactive tools rather than just static pages.

Following each task, the instructor explains the backend actions: files created, code written, and output interpretation. Participants record their most effective prompts in a shared Prompt Playbook. 

Break — 10 minutes

Phase 3 — Optimizing Claude Code Usage — 50 minutes

• The art of effective prompting: distinguishing between specific and vague instructions
• Live demonstration: side-by-side comparison of weak and strong prompts for the same task
• Iteration and refinement: requesting explanations of choices, reverting changes, or exploring alternative approaches
• Processing 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”)
• Cost and usage metrics: understanding tokens, context windows, and subscription tiers
• Deciding when to use Claude Code versus standard Claude chat
• Guided exercise: Participants extend a Phase 2 project with two new features using a multi-step prompt chain, then compare before-and-after prompts to identify key differences.

Objective: Transition from basic functionality to consistent, high-quality results.

Break — 10 minutes

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

This phase shifts the session's dynamic. Rather than individual practice, the group collaborates. The instructor facilitates while participants drive the process — identifying real job-related problems, suggesting prompt ideas, and discussing trade-offs. The aim is to cultivate prompt judgment by observing skilled navigation of uncertainty in real time.

The session is structured around three workflow archetypes:

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

Setup and Context (10 min): The instructor introduces the three archetypes and outlines 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, incorporating prompt ideas, pushbacks, and refinements from the room. Every decision is narrated. The session concludes with a working prompt template for the participant whose problem was addressed.

Live Build #2 — Draft or Analyze Workflow (20 min): Similar format, applied to a different archetype and a different participant’s challenge.

Reflection and Sharing (10 min): Participants record one surprising prompting tactic, one alternative approach they would take, and one pattern to retain. A brief group discussion follows (3-4 participants), with the instructor linking observations to the broader Prompt Playbook.

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

• MCP (Model Context Protocol) explained: The universal connection system for AI tools
• The importance of MCP: Evolving Claude from a chat assistant to a connected workflow hub
• 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 through the Connectors UI and illustrates 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. “Retrieve data from this connected service and generate a local report”

Guided exercise: Participants connect Claude to at least one service. Various 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) — select, authenticate, and proceed
• Option B: Add a custom connector by pasting an MCP server URL (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:

• Connector mechanics: OAuth authentication, permissions, and access grants
• Managing tool access: Enabling, disabling, and controlling connector usage per conversation
• Security considerations: Connecting only to trusted services and reviewing tool permissions
• MCP ecosystem: Locating new connectors, extensions, and community-built servers

Objective: Participants will view Claude as a connective layer between all their existing services, not merely a coding tool.

Break — 10 minutes

Phase 6 — Capstone Project & Future Steps — 65 minutes

Capstone mini-project (45 min): Each participant selects a 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 addresses a real workflow challenge (calculator, tracker, converter, or quiz)
4. A connected workflow: Retrieving data from a connected service, transforming it, and generating 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 Conclusion (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, and Cowork for knowledge workers
• MCP ecosystem: Discovering and evaluating new connectors, extensions, and community servers
• Subscription plans: Free vs. Pro vs. Max — understanding features and appropriate use cases
• Best practices review: Recapping 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 detailing key prompting patterns, connector setup steps, and a curated list of useful MCP integrations