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 interactions
• The Claude product ecosystem: claude.ai, Claude Desktop, Claude Code (CLI), and their interrelationships
• Interface tour: navigating the Claude app, initiating a coding session, and understanding the workspace
• How Claude Code operates: the describe → plan → act → review loop
• Understanding permissions: the rationale behind Claude requesting confirmation before creating files or executing code
• Initial build: instructing Claude to create a simple styled webpage from a single-sentence description
• Iterating on results: requesting changes 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 results through follow-up instructions.

Objective: Ensure all participants feel comfortable with the interface and have overcome the initial interaction hurdle.

Break — 10 minutes

Phase 2 — Creating Real Projects with Plain English — 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: 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 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 can transform 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 explains the background actions taken by Claude, including files created, 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 art of effective prompting: specific versus vague instructions
• Live demonstration: Side-by-side comparison of weak and strong prompts applied to the same task
• Iteration and refinement: Asking Claude to explain its choices, undo changes, or try alternative approaches
• Working with uploaded files: Commands such as “read this document and summarize it” or “convert this spreadsheet into a chart”
• Multi-step workflows: Chaining requests to build complex outputs (e.g., “first analyze this data, then build a dashboard from the results”)
• Understanding costs and usage: How tokens, context windows, and subscription tiers function
• Determining when to use Claude Code versus standard Claude chat
• Guided exercise: Participants select one of their Phase 2 projects 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 contributing to improved results.

Objective: Progress from functional results to consistently achieving high-quality outcomes.

Break — 10 minutes

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

This phase shifts the dynamic of the room. Rather than solo practice, the group builds together. While the instructor leads, participants direct the process—naming real problems from their professional roles, suggesting prompt ideas, and debating trade-offs. The objective is to develop prompt judgment by observing an expert navigate uncertainty in real time.

Three workflow archetypes structure this session:

• Transform — Taking input X and producing output Y (e.g., meeting notes → action items; raw data → summary email; customer feedback → themed report)
• Draft — Generating an initial version of content typically written from scratch (e.g., proposals, emails, job descriptions, social media posts)
• Analyze — Interrogating documents or datasets that lack time for careful reading (e.g., a 40-page report, a survey spreadsheet, a contract)

Setup and framing (10 min): The instructor introduces the three archetypes and explains the session structure. 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 contributes prompt ideas, pushbacks, and refinements. The instructor narrates each decision. The session concludes with a working prompt template retained by the participant whose problem was addressed.

Live build #2 — Draft or Analyze workflow (20 min): The same format is applied to a different archetype and a different participant’s problem.

Reflection & share-back (10 min): Participants take a moment to note one surprising prompting technique, one aspect they would change, and one pattern they wish to retain. A brief group share follows, featuring 3-4 participants. 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 plug system for AI tools
• The significance 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 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 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)—click, authenticate, and proceed
• Option B: Add a custom connector by pasting an MCP server URL (the 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—e.g., “Read my recent emails regarding 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: Where to find new connectors, extensions, and community-built servers

Objective: Participants will view Claude as a connective layer between the services they already use, 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: Uploading a file, having Claude analyze it, and producing a visual report
3. An interactive tool solving a real workflow problem (calculator, tracker, converter, or 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 to assist with prompt refinement and showcases 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, Cowork for knowledge workers
• The MCP ecosystem: Finding and evaluating new connectors, extensions, and community servers
• Subscription plans: Free vs. Pro vs. Max—what each unlocks and which fits which use case
• Best practices recap: 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 containing key prompting patterns, connector setup steps, and a curated list of useful MCP integrations