Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 55 minutes

• What Claude is and how Claude Code differs from standard chat interfaces
• The Claude product ecosystem: claude.ai, Claude Desktop, Claude Code (CLI), and their interrelationships
• Interface overview: navigating the Claude app, initiating coding sessions, and understanding the workspace
• Claude Code’s operational logic: the describe → plan → act → review cycle
• Understanding permissions: why Claude requests approval before creating files or executing code
• First build: instructing Claude to create a simple, styled webpage from a single-sentence description
• Refining results: adjusting elements 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 build a personalized “About Me” webpage by describing their preferences in plain English. They practice refining the output through iterative follow-up instructions.

Objective: Participants feel comfortable with the interface and have overcome initial interaction barriers.

Break — 10 minutes

Phase 2 — Creating Practical Solutions with Natural Language — 70 minutes

This segment forms the core of the morning. Participants complete four progressively complex tasks 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 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 transforms raw data into polished deliverables.
• Task 4 — Automation tool: Request that Claude 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 underlying processes: which files were created, what code was written, and how to interpret the output. Participants document their most effective prompts in a shared Prompt Playbook.

Break — 10 minutes

Phase 3 — Optimizing Interactions with Claude Code — 50 minutes

• The craft of effective prompting: distinguishing between specific and vague instructions
• Live demonstration: Side-by-side comparison of weak versus strong prompts applied to the same task
• Iteration and refinement: Requesting explanations of Claude’s choices, undoing changes, or exploring alternative approaches
• Working with uploaded files: Tasks 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 usage and costs: An overview of tokens, context windows, and subscription tiers
• Distinguishing when to use Claude Code versus standard Claude chat
• Guided exercise: Participants select a project from Phase 2 and extend it with two new features using a multi-step prompt chain. They then compare their initial and refined prompts to identify key differences.

Objective: Progress from basic functionality (“it works”) to consistent, high-quality results (“I can get great results reliably”).

Break — 10 minutes

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

This phase shifts the dynamic in the room. Instead of solo practice, the group builds together. The instructor guides the process, but participants drive the content by naming real problems from their own roles, suggesting prompt ideas, and debating trade-offs. The aim is to learn prompt judgment by observing how a skilled practitioner navigates uncertainty in real time.

Three workflow archetypes structure the session:

• Transform — Take input X and produce 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 careful manual review (e.g., a 40-page report, a survey spreadsheet, a contract)

Setup and context (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 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 originating participant can retain.

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

Reflection & sharing (10 min): Participants take a moment to note one prompting technique that surprised them, one adjustment they would make, and one pattern they are taking away. A brief group sharing session follows, with 3-4 participants speaking. 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 interface for connecting AI tools
• The value of MCP: Evolving Claude from a chat assistant into a central hub for connected workflows
• 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 demo: 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 for varying 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 go
• 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 a task to Claude that utilizes 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: Sources for new connectors, extensions, and community-built servers

Objective: Participants view Claude as a connective layer between all the services they already use, rather than just a coding tool.

Break — 10 minutes

Phase 6 — Capstone & Future Pathways — 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 generate a visual report
3. An interactive tool that solves a specific workflow problem (calculator, tracker, converter, quiz)
4. A connected workflow: Retrieve 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, assists with prompt refinement, and highlights standout examples to the group.

Showcase and wrap-up (20 min):

• 6-8 participants share their projects (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 — understanding what each unlocks and which fits specific use cases
• Best practices summary: 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 containing key prompting patterns, connector setup steps, and a curated list of useful MCP integrations