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 interfaces
• The Claude product ecosystem: relationships between claude.ai, Claude Desktop, and Claude Code (CLI)
• Interface navigation: exploring the Claude app, initiating coding sessions, and understanding the workspace
• Cognitive process of Claude Code: the describe → plan → act → review loop
• Permission management: understanding why Claude seeks approval before creating files or executing code
• Initial build: instructing Claude to generate a simple styled webpage from a single-sentence description
• Result iteration: adjusting elements such as headers, color schemes, and navigation bars
• Guided Exercise: Participants launch the Claude app, initiate a Claude Code session, and create a personalized "About Me" webpage by describing their preferences in plain English, refining results through follow-up instructions.

Objective: Ensure all participants are comfortable with the interface and have overcome initial interaction barriers.

Break — 10 minutes

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

This segment forms the core of the morning, where participants complete four increasingly complex tasks 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 directions such as "use a dark theme," "add a sidebar," and "ensure responsiveness."
• Task 2 — Data Analysis: Provide Claude with a sample CSV file and request data summarization, trend identification, extreme value detection, and visual chart generation. This demonstrates how Claude writes and executes code on behalf of the user.
• 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 highlights Claude's ability to transform raw data into polished deliverables.
• Task 4 — Automation Utility: Instruct Claude to build a simple utility like a unit converter, quiz app, or budget calculator. This introduces the concept of creating interactive tools rather than just static pages.

Following each task, the instructor explains the backend actions, including file creation, code generation, and output interpretation. Participants document their most effective prompts in a shared Prompt Playbook.

Break — 10 minutes

Phase 3 — Optimizing Workflows with Claude Code — 50 minutes

• Prompting best practices: distinguishing between specific and vague instructions
• Live demonstration: side-by-side comparison of weak versus strong prompts for identical tasks
• Refinement techniques: requesting explanations, undoing changes, or exploring alternative approaches
• File integration: instructing Claude to summarize documents or convert spreadsheets into charts
• Multi-step workflows: chaining requests to generate complex outputs, such as analyzing data and then building a dashboard from the results
• Cost and usage management: understanding tokens, context windows, and subscription tiers
• Decision-making: 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, then compare their initial and refined prompts to identify key differences.

Objective: Transition from basic functionality to consistently achieving high-quality results.

Break — 10 minutes

Phase 4 — Collaborative Workflow Development: Live Build Session — 60 minutes

This phase shifts the dynamic from individual practice to group collaboration. The instructor leads the process while participants guide the direction by sharing real-world job challenges, suggesting prompt ideas, and debating trade-offs. The aim is to develop prompt judgment by observing a skilled practitioner navigate uncertainties in real time.

The session is structured around three workflow archetypes:

• Transform — Converting input X into output Y (e.g., meeting notes to action items, raw data to summary emails, or customer feedback to themed reports)
• Draft — Generating initial versions of documents typically written from scratch, such as proposals, emails, job descriptions, or social media posts
• Analyze — Interrogating large documents or datasets that lack time for detailed review, such as lengthy reports, survey spreadsheets, or contracts

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 challenge and builds it live, incorporating prompt ideas, pushbacks, and refinements from the room. Every decision is narrated, culminating in a working prompt template that the originating participant can retain.

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

Reflection & Share-back (10 min): Participants reflect on one surprising prompting technique, one area for improvement, and one key takeaway. A brief group share follows, with 3-4 volunteers sharing insights. 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) as a universal integration system for AI tools
• The value of MCP: evolving Claude from a chat assistant into a connected workflow hub
• Connectors Directory: browsing and adding integrations directly within the Claude app
• Desktop Extensions: one-click installations for Claude Desktop that require no configuration files

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"
2. "Read the latest updates from our project board and write a status summary"
3. "Retrieve data from this connected service and generate a local report"

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) by clicking, authenticating, and proceeding
• Option B: Add a custom connector by pasting an MCP server URL (a test URL will be 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, such as "Read my recent emails about project updates and create a summary document."

Key concepts covered include:

• Connector mechanics: OAuth authentication, permissions, and the scope of access granted
• Access management: 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: Participants will view Claude as a connective layer integrating all their existing services, rather than just a coding tool.

Break — 10 minutes

Phase 6 — Capstone Project & Future Steps — 65 minutes

Capstone Mini-Project (45 min): Each participant selects one scenario and builds it using 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 (e.g., calculator, tracker, converter, or quiz)
4. A connected workflow: retrieving 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 the room to assist 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: exploring Claude Code CLI for terminal users, the VS Code extension for developers, and Cowork for knowledge workers
• MCP ecosystem navigation: finding and evaluating new connectors, extensions, and community servers
• Subscription tiers: understanding the differences between Free, Pro, and Max plans and matching them to 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