Course Outline
Phase 1 — Introduction to Claude Code — 55 minutes
- An overview of Claude and what distinguishes Claude Code from standard chat interfaces
- The Claude product ecosystem: understanding the relationship between claude.ai, Claude Desktop, and Claude Code (CLI)
- Interface walkthrough: navigating the Claude app, initiating a coding session, and comprehending the workspace
- How Claude Code operates: exploring the describe → plan → act → review cycle
- Understanding permissions: the rationale behind Claude’s requests before creating files or executing code
- Your initial build: instructing Claude to generate a simple styled webpage from a one-sentence description
- Refining results: issuing commands such as “increase the header size,” “change the color scheme,” or “add a navigation bar”
- Guided exercise: participants launch the Claude app, start a Claude Code session, and construct a personalized “About Me” webpage by describing their preferences in plain English. They practice refining outcomes through follow-up instructions.
Goal: Ensuring everyone is comfortable with the interface and has overcome the initial learning curve.
Break — 10 minutes
Phase 2 — Constructing Real Projects with Plain English — 70 minutes
This segment forms the core of the morning session. Participants complete four progressively complex tasks using only natural language prompts.
- Task 1 — Interactive Dashboard: Request Claude Code to create a styled dashboard displaying sample data with charts, statistics, and a clean layout. Practice providing design directions such as “use a dark theme,” “include a sidebar,” or “make it responsive.”
- Task 2 — Data Analysis: Provide Claude with a sample CSV file and ask it to summarize the data, identify trends, locate maximum and minimum values, and generate a visual chart. This demonstrates Claude’s ability to write and execute 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 develop a simple utility — for instance, a unit converter, quiz app, or budget calculator. This introduces the concept that Claude can build interactive tools, not just static pages.
Following each task, the instructor explains the behind-the-scenes 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 — Enhancing Productivity with Claude Code — 50 minutes
- The nuances of effective prompting: distinguishing between specific and vague instructions
- Live demonstration: a side-by-side comparison of weak versus strong prompts applied to the same task
- Iteration and refinement: asking Claude to explain its decisions, undo changes, or explore alternative approaches
- Handling uploaded files: commands like “read this document and summarize it” or “convert this spreadsheet into a chart”
- Multi-step workflows: chaining requests to create complex outputs (e.g., “first analyze this data, then build a dashboard from the results”)
- Understanding costs 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 before-and-after prompts to identify what drove the improvement.
Goal: Elevating proficiency from “it works” to “I can consistently achieve excellent results.”
Break — 10 minutes
Phase 4 — Personalizing Claude Workflows: Live Build Session — 60 minutes
This phase shifts the energy in the room. Rather than solo practice, the group engages in collective building. The instructor drives the technical process, but participants direct the content by naming real problems from their own jobs, suggesting prompt ideas, and debating tradeoffs. The objective is to learn prompt judgment by observing an expert navigate uncertainty in real time.
Three workflow archetypes structure this session:
- Transform — converting input X into output Y (e.g., meeting notes → action items; raw data → summary email; customer feedback → themed report)
- Draft — generating a first version of content you would normally write from scratch (proposals, emails, job descriptions, social media posts)
- Analyze — interrogating a document or dataset you lack the time to review thoroughly (a 40-page report, a spreadsheet of survey responses, a 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 while the room contributes prompt ideas, pushes back, and refines directions. The instructor narrates every decision. The session concludes with a working prompt template that the participant who submitted the problem keeps.
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 take a moment to write down one prompting technique that surprised them, one thing they would approach differently, and one pattern they will adopt. A quick group share follows — 3-4 voices, not everyone. The instructor connects these observations to the broader Prompt Playbook.
Phase 5 — Integrating Claude with Your Tools via MCP — 50 minutes
- What is MCP (Model Context Protocol)? The universal plug system for AI tools
- Why MCP matters: 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 installs for Claude Desktop requiring no configuration files
Live Demonstration: The instructor connects Claude to two services through the Connectors UI and demonstrates cross-tool workflows:
- “Check my Google Calendar for tomorrow’s meetings and draft a prep email for each one”
- “Read the latest updates from our project board and write a status summary”
- “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 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 begin
- Option B: Add a custom connector by pasting an MCP server URL (the instructor provides a test URL)
- Option C: Install a Desktop Extension from the marketplace (for Claude Desktop users)
Participants then task Claude with using the connected service — for example, “Read my recent emails about project updates and create a summary document.”
Key concepts covered:
- How connectors function: 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: where to discover new connectors, extensions, and community-built servers
Goal: Helping participants view Claude as a connective layer across all their existing services, rather than just a coding tool.
Break — 10 minutes
Phase 6 — Capstone & Next Steps — 65 minutes
Capstone Mini-Project (45 min): Each participant selects one scenario and builds it with Claude:
- A polished landing page or portfolio site for their team, project, or personal brand
- A data analysis pipeline: uploading a file, having Claude analyze it, and producing a visual report
- An interactive tool solving a real workflow problem (calculator, tracker, converter, quiz)
- 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 what they built (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: how to find and evaluate new connectors, extensions, and community servers
- Subscription plans: Free vs. Pro vs. Max — features unlocked and which fits which use case
- 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 containing key prompting patterns, connector setup steps, and a curated list of useful MCP integrations
Requirements
Requirements
Familiarity with
- Basic computer literacy: navigating file systems, utilizing web browsers, and installing software
- General awareness of AI assistant capabilities (e.g., casual use of ChatGPT, Gemini, or Claude is beneficial for context, though not mandatory)
Experience with
- No coding, programming, or terminal experience is required. This course is specifically designed for individuals who have never written code.
- No prior familiarity with Claude or other AI tools is necessary.
Technical Requirements
- Participants must bring a laptop (Mac, Windows, or Linux) equipped with a modern web browser.
- A stable internet connection is required.
- A Claude Pro subscription is needed for the session (a 1-month gift subscription is included with registration; setup instructions will be provided prior to the class).
- Claude Desktop is recommended but not mandatory; the web application at claude.ai is sufficient for all exercises.
- A Google account is recommended for the MCP connectors exercise (covering Gmail, Google Drive, and Google Calendar), although alternative connector options are available.
Target Audience
- Business professionals seeking to harness AI for productivity and automation
- Marketers, operations managers, and analysts aiming to automate repetitive tasks
- Founders and entrepreneurs looking to build prototypes without hiring developers
- Educators and researchers exploring AI-assisted workflows
- Anyone curious about Claude’s capabilities who lacks a technical background
Testimonials (1)
That i gained a knowledge regarding streamlit library from python and for sure i'll try to use it to improve applications in my team which are made in R shiny
