Introduction to Claude Code for Non-Developers Training Course

Phase 1 — Introduction to Claude Code — 30 minutes

• Overview of Claude and the key distinctions between Claude Code and standard chat interfaces
• Orientation: Focusing on the Claude app (web or desktop) for this session; CLI and other interfaces are detailed in the reference materials
• Interface walkthrough: Initiating coding sessions and navigating the workspace
• The Claude Code logic: The describe → plan → act → review cycle
• Permission management: The rationale behind Claude requesting approval before file creation or code execution
• Initial build exercise: Instructing Claude to generate a simple, styled webpage based on a single sentence description
• Refining outputs: Iterative adjustments such as enlarging headers, altering color schemes, or adding navigation bars
• Guided practice: Participants launch a session to create a personalized “About Me” page, iterating on the design through follow-up prompts

Objective: To ensure all participants overcome initial barriers and feel at ease with the interface.

Break — 7 minutes

Phase 2 — Creating Real Solutions with Natural Language — 55 minutes

Three tasks of increasing complexity, executed entirely through natural language prompts.

• Task 1 — Interactive dashboard: Creating a styled dashboard with sample data, charts, and statistics. Practicing design direction prompts like “apply a dark theme,” “insert a sidebar,” or “ensure responsive design.”
• Task 2 — Data analysis: Uploading a sample CSV file to ask Claude for summaries, trend identification, peak/trough analysis, and visual chart generation. This demonstrates Claude's ability to write and execute code on your behalf.
• Task 3 — Automation utility: Developing a simple tool such as a unit converter, quiz app, or budget calculator. This highlights Claude's capacity to build interactive applications beyond static pages.

Following each task, the instructor examines the background actions: files generated, code produced, and interpreting outputs. Participants log their most effective prompts in a shared Prompt Playbook.

Break — 7 minutes

Phase 3 — Optimizing Interactions with Claude Code — 35 minutes

• Prompting mastery: Differentiating between specific and vague instructions
• Live comparison: Analyzing weak versus strong prompts applied to the same task
• Iteration and refinement: Requesting explanations for choices, reverting changes, or exploring alternative approaches
• File integration: Instructing Claude to summarize uploaded documents or convert spreadsheets into visual data
• Complex workflows: Chaining multiple requests to construct sophisticated outputs
• Resource management: Understanding tokens, context windows, and subscription tiers
• Tool selection: Determining when to use Claude Code versus standard Claude chat
• Guided practice: Participants enhance a Phase 2 project with a new feature using multi-step prompts, then analyze the impact of prompt adjustments

Objective: To evolve from “it works” to achieving consistent, high-quality results.

Break — 7 minutes

Phase 4 — Integrating Claude with Your Tools via MCP — 34 minutes

Preparation: Participants receive instructions to connect Gmail or Google Drive prior to the session, allowing class time to focus on utilizing the connection rather than setup.

• Understanding MCP (Model Context Protocol): The universal integration standard for AI tools
• The value of MCP: Transforming Claude from a chat assistant into a central hub for connected workflows
• Connector Directory: Discovering and adding integrations directly within the Claude app
• Desktop Extensions: One-click installations (for Claude Desktop users)
• Live demonstration (single workflow): “Review tomorrow's meetings on Google Calendar and draft preparation emails for each”
• Guided practice: Participants use their pre-connected service (or establish a live connection) to assign a task, e.g., “Summarize recent project update emails into a document”
• Core concepts: OAuth, permissions, managing access per conversation, security best practices, and locating new connectors

Objective: To perceive Claude as a connective layer for business processes, not solely a coding assistant.

Phase 5 — Capstone & Conclusion — 35 minutes

Capstone mini-project (25 min): Participants select one scenario:

1. A refined landing page or portfolio site
2. A data analysis pipeline: Uploading a file, analyzing it, and generating a visual report
3. An interactive tool addressing a specific workflow challenge
4. A connected workflow: Retrieving data from a Phase 4 service, processing it, and creating a final deliverable

The instructor provides support by circulating, refining prompts, and highlighting notable examples.

Conclusion (10 min):

• Next steps: Claude Code CLI for terminal users, VS Code extension for developers, and Cowork for knowledge workers
• Subscription plans: Comparing Free, Pro, and Max tiers, their respective capabilities, and ideal use cases
• Recommended resources: Official documentation, Anthropic's prompt engineering guide, and community forums
• Takeaways: Participants receive a reference card detailing prompting patterns, connector setup, and essential MCP integrations