Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 55 minutes

• An 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 relationships
• Interface orientation: navigating the Claude app, initiating coding sessions, and understanding the workspace
• The operational logic of Claude Code: the describe → plan → act → review loop
• Permissions management: understanding why Claude requests confirmation before creating files or executing code
• Initial build: instructing Claude to create a simple styled webpage based on a one-sentence description
• Iterating on outcomes: applying directives such as “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 create a personalized “About Me” webpage by describing their requirements in plain English. They practice refining the output 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 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. 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, detection of highest and lowest values, and the generation of a visual chart. This demonstrates how Claude writes and executes code on your 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 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 explains the backend actions: which files were created, what code was written, and how to interpret the output. Participants record their most effective prompts in a shared Prompt Playbook.

Break — 10 minutes

Phase 3 — Advanced Techniques with Claude Code — 50 minutes

• The craft of effective prompting: the impact of specific versus vague instructions
• Live demonstration: A side-by-side comparison of weak and strong prompts applied to the same task
• Iteration and refinement: Asking Claude to explain its choices, revert changes, or adopt a different approach
• Utilizing uploaded files: Instructions such as “read this document and summarize it” or “convert this spreadsheet into a chart”
• Multi-step workflows: Chaining requests to construct complex outputs (e.g., “first analyze this data, then build a dashboard from the results”)
• Cost and usage management: 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 the factors that improved the outcome.

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 shifts the classroom dynamic. Instead of individual practice, the group builds together. While the instructor guides the process, participants drive the direction by naming real problems from their jobs, suggesting prompt ideas, and debating trade-offs. The aim is to cultivate prompt judgment by observing a skilled professional navigate uncertainty in real time.

Three workflow archetypes structure this session:

• Transform — Convert input X to output Y (e.g., meeting notes to action items; raw data to a summary email; customer feedback to a thematic report)
• Draft — Generate an initial version of content typically written from scratch (e.g., proposals, emails, job descriptions, social media posts)
• Analyze — Interrogate documents or datasets that require detailed review (e.g., a 40-page report, a survey spreadsheet, 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 professional 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, critiques, and refinements. The instructor narrates every decision. The session concludes with a working prompt template, which the participant who submitted the problem retains.

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

Reflection and sharing (10 min): Participants spend time writing down one surprising prompting technique, one improvement they would make, and one key takeaway. A brief group share (3-4 participants) follows, during which 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 connection system for AI tools
• The importance of MCP: Transforming 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 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 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) — involving simple clicks and authentication
• 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:

• Connector mechanics: OAuth authentication, permissions, and the scope 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: Enable participants to view Claude as a connective layer between their existing services, rather than just a coding tool.

Break — 10 minutes

Phase 6 — Capstone & Future Directions — 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 workflow problem (e.g., 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 moves among participants, assists 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)
• Next steps: Claude Code CLI for terminal users, VS Code extension for developers, and Cowork for knowledge workers
• The MCP ecosystem: Discovering 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 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