Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 55 minutes

• An overview of Claude and what distinguishes Claude Code from standard chat interfaces
• The Claude product suite: claude.ai, Claude Desktop, Claude Code (CLI), and their interrelationships
• Interface tour: navigating the Claude app, initiating a coding session, and familiarizing oneself with 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 generate a simple styled webpage from a single-sentence description
• Refining results: issuing commands such as “make the header bigger,” “change the color scheme,” 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 then practice improving 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 Solutions with Plain English — 70 minutes

This section forms the core of the morning. 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: “use a dark theme,” “add a sidebar,” “make it responsive.”
• Task 2 — Data analysis: Provide Claude with a sample CSV file and request a summary, trend identification, 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 generator: Ask Claude to read a data file and generate a formatted report—such as a sales summary, project status update, or meeting recap. This illustrates how Claude can convert 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 concept that Claude can create interactive tools, not just static pages.

Following each task, the instructor clarifies the behind-the-scenes actions: the files created, the code written, and how to interpret the output. 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: contrasting specific versus vague instructions
• Live demonstration: A side-by-side comparison of weak versus strong prompts for the same task
• Iteration and refinement: Asking Claude to explain its choices, revert changes, or adopt different approaches
• Utilizing uploaded files: “Read this document and summarize it,” “Convert this spreadsheet into a chart”
• Multi-step workflows: Chaining requests to generate complex outputs (“First analyze this data, then build a dashboard from the results”)
• Cost and usage awareness: Understanding tokens, context windows, and subscription tiers
• Determining 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 initial and refined prompts to identify key improvements.

Objective: Progress from “it works” to “I can consistently achieve excellent results.”

Break — 10 minutes

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

This phase elevates the energy in the room. Rather than working solo, the group builds collectively. The instructor leads, but participants make the decisions—identifying real problems from their jobs, suggesting prompt ideas, and discussing trade-offs. The aim is to develop prompt judgment by observing a skilled practitioner navigate uncertainty in real time.

Three workflow archetypes structure the session:

• Transform — Take input X to produce output Y (e.g., meeting notes → action items; raw data → summary email; customer feedback → themed report)
• Draft — Generate an initial version of items typically written from scratch (proposals, emails, job descriptions, social media posts)
• Analyze — Interrogate documents or datasets that lack the time for detailed review (e.g., a 40-page report, a spreadsheet of survey responses, 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 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 each decision. The session concludes with a working prompt template, which the submitting participant retains.

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

Reflection & share-back (10 min): Participants pause to note one surprising prompting move, one alternative approach they might take, and one key pattern to take away. A brief group share follows—featuring 3-4 voices rather than everyone. The instructor links these observations to the broader Prompt Playbook.

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

• What is MCP (Model Context Protocol)? The universal interface system for AI tools
• The significance 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”
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) — click, authenticate, and proceed
• 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 — for example, “Read my recent emails about project updates and create a summary document.”

Key concepts covered:

• Connector mechanics: OAuth authentication, permissions, and the access being 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 integrating all their existing services, 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 that solves a real workflow problem (calculator, tracker, converter, 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 highlights standout examples to the group.

Showcase and wrap-up (20 min):

• 6-8 participants share their builds (2-3 minutes each)
• Future paths: 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
• Plans: Free vs. Pro vs. Max — what each tier unlocks and which suits specific use cases
• Best practices recap: 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 featuring key prompting patterns, connector setup steps, and a curated list of useful MCP integrations