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 interrelationships
• Interface walkthrough: navigating the Claude application, initiating a coding session, and understanding the workspace
• Understanding Claude Code’s logic: the describe → plan → act → review cycle
• Comprehending permissions: why Claude requests authorization before creating files or executing code
• Initial build: instructing Claude to generate a simple styled webpage based on a single-sentence description
• Refining outcomes: commands such as “make the header larger,” “modify the color scheme,” and “add a navigation bar”
• Guided exercise: participants launch the Claude app, initiate a Claude Code session, and construct a personalized “About Me” webpage by describing their requirements in plain English. They practice improving results through iterative follow-up instructions.

Objective: All participants should feel at ease with the interface and overcome the initial interaction barrier.

Break — 10 minutes

Phase 2 — Creating Practical Applications with Plain English — 70 minutes

This segment 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 directives such as “use a dark theme,” “add a sidebar,” and “make it responsive.”
• Task 2 — Data analysis: provide Claude with a sample CSV file and request it to summarize the data, identify trends, determine highest and lowest values, and generate a visual chart. This demonstrates how Claude writes and executes code on behalf of the user.
• Task 3 — Document generator: instruct 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: 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 highlights Claude’s background actions: the files created, the 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 Work with Claude Code — 50 minutes

• The art of effective prompting: distinguishing specific from vague instructions
• Live demonstration: side-by-side comparison of weak versus strong prompts applied to the same task
• Iteration and refinement: requesting Claude to explain its decisions, revert changes, or adopt alternative approaches
• Working with uploaded files: instructions like “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”)
• Understanding costs and usage: the mechanics of tokens, context windows, and subscription tiers
• Deciding 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 revised 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 — Your Claude Workflows: Live Build Session — 60 minutes

This phase shifts the energy of the session. Instead of individual practice, the group collaborates on building solutions. While the instructor leads the technical process, participants direct the strategy — identifying real-world problems from their professions, suggesting prompt ideas, and debating trade-offs. The aim is to cultivate prompt judgment by observing an expert navigate uncertainty in real time.

Three workflow archetypes structure this session:

• Transform — convert input X into 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 lack time for detailed review (e.g., a 40-page report, survey response spreadsheets, or contracts)

Setup and Context (10 min): The instructor introduces the three archetypes and explains the session dynamics. 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 every decision. The session concludes with a working prompt template that the contributing participant retains.

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

Reflection & Sharing (10 min): Participants take a moment to note one surprising prompting technique, one area for improvement, and one pattern to apply later. A quick group share follows — involving 3-4 participants. The instructor connects these observations to the broader Prompt Playbook.

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

• Definition of MCP (Model Context Protocol): The universal integration standard 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 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 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 for 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
• 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 uses per conversation
• Security awareness: connecting only to trusted services and reviewing tool permissions
• The MCP ecosystem: discovering new connectors, extensions, and community-built servers

Objective: Participants should view Claude as a connective layer between the services they already use, not merely a coding tool.

Break — 10 minutes

Phase 6 — Capstone & Future 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 a 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, and Cowork for knowledge workers
• The MCP ecosystem: finding and evaluating new connectors, extensions, and community servers
• Subscription plans: Free vs. Pro vs. Max — features unlocked and use-case fit
• 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 containing key prompting patterns, connector setup steps, and a curated list of useful MCP integrations