Claude Code for Non-Developers Training Course

Phase 1 — Introducing Claude Code — 55 minutes

• An overview of Claude and what distinguishes Claude Code from standard chat interfaces
• The Claude product ecosystem: claude.ai, Claude Desktop, and Claude Code (CLI), and how they interconnect
• Interface orientation: navigating the Claude app, initiating a coding session, and understanding the workspace
• Understanding Claude Code’s process: the describe → plan → act → review cycle
• Permission management: why Claude requests authorization before creating files or executing code
• Initial build: instructing Claude to create a simple styled webpage from a single-sentence description
• Refining results: issuing commands such as “make the header larger,” “change the color scheme,” or “add a navigation bar”
• Guided exercise: participants launch the Claude app, start a Claude Code session, and create a personalized “About Me” webpage by describing their requirements in plain English. They then practice refining 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 — Building 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: Request 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,” or “make it responsive.”
• Task 2 — Data analysis: Provide Claude with a sample CSV file and request it to summarize the data, identify trends, locate highest and lowest values, and generate a visual chart. This demonstrates how Claude writes and executes code on your behalf.
• 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 transforms raw data into polished deliverables.
• Task 4 — Automation tool: Ask 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 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 Workflows with Claude Code — 50 minutes

• The art of effective prompting: contrasting 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, 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 cost and usage: how tokens, context windows, and subscription tiers function
• 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 key differences.

Objective: Progress from mere functionality to consistently achieving high-quality results.

Break — 10 minutes

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

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

Three workflow archetypes structure the session:

• Transform — Convert input X to output Y (e.g., meeting notes → action items; raw data → summary email; customer feedback → themed report)
• Draft — Generate an initial version of content typically written from scratch (e.g., proposals, emails, job descriptions, social media posts)
• Analyze — Interrogate a document or dataset that lacks time for detailed review (e.g., a 40-page report, survey spreadsheet, or 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, pushbacks, and refinements. The instructor narrates every decision. The session concludes with a working prompt template for the participant whose problem was selected.

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 area for improvement, and one pattern to retain. A brief group share involves 3–4 voices. 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 plug system for AI tools
• The importance of MCP: Evolving Claude from a chat assistant into a connected workflow hub
• The Connectors Directory: Browsing and adding integrations directly from 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 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”

Guided exercise: Participants connect Claude to at least one service. Options are provided for varying 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 (a test URL is provided by the instructor)
• Option C: Install a Desktop Extension from the marketplace (for Claude Desktop users)

Participants then assign a task to Claude that utilizes the connected service—e.g., “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: Enable participants to view Claude as a connective layer between all their services, not just 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 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, or 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 the room, helps refine prompts, and highlights standout examples to the group.

Showcase and wrap-up (20 min):

• 6–8 participants share their builds (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 — what each unlocks and which suits specific use cases
• 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 detailing key prompting patterns, connector setup steps, and a curated list of useful MCP integrations