Skip to content

Identify Your AI Builder Stack

Introduction

This course transforms you from a Claude user into a Claude builder. That means working hands-on with a complete AI builder stack—the same tools and infrastructure that power modern AI-first operations.

This lesson sets expectations about what tools we'll use throughout the course. You're welcome to get a head start on setup, but Week 1 (Configure AI Builder Stack) will walk through detailed installation and configuration for everything listed here. Think of this as your shopping list and system check—by the end of this lesson, you'll know exactly what you need and whether your current setup is ready.

The AI Builder Stack isn't just a collection of tools. It's an integrated system where each component plays a specific role in how you build, deploy, and scale AI systems that work for you. Understanding this stack now will help you see how everything connects as we progress through the course.

Estimated Costs

Monthly Subscription Costs: - Claude Pro or Team: $20-30/month (required) - Wispr Flow: $15/month (optional, but recommended if using voice-to-text heavily) - All other tools: Free

Total minimum monthly cost: $20/month (Claude subscription only)

Setup Checklists

Before Week 1 Starts (Essential)

Complete these items before the first live session:

  • [ ] Claude Pro or Team subscription active
  • [ ] Operating system confirmed (macOS or Windows)
  • [ ] Admin access confirmed on your machine
  • [ ] Regional availability verified for Claude features

Note: Some Claude features may have regional constraints. Review the tools below to ensure they're available in your region.

By End of Week 1 (Setup Goals)

Week 1 will guide you through setting up these items. You're welcome to get a head start:

  • [ ] GitHub account created
  • [ ] Code editor downloaded (Cursor or VS Code)
  • [ ] Chrome browser installed
  • [ ] Claude Desktop App installed
  • [ ] Claude in Chrome extension installed
  • [ ] Claude Code CLI installed
  • [ ] Slack invite received and accepted
  • [ ] Agentic AI Registry created (Notion or alternative)

Required Tools Overview

1. Claude Subscription

What: Your primary AI workspace Which tier: Claude Pro ($20/month minimum) or Claude Team recommended Why: Access to Claude Sonnet/Opus 4.5, Projects feature, and higher usage limits When we use it: Every week—this is your command center Get started: Subscribe to Claude

Note: If you plan to use Claude Code heavily (Weeks 4-5), consider upgrading to Claude Max for significantly higher usage limits.

2. GitHub Account

What: Version control and code collaboration platform Cost: Free tier is sufficient Why: Essential for managing Skills, version control, and agentic coding workflow When we use it: Week 1 (setup), Week 2 (Skills deployment), Weeks 4-5 (Claude Code integration) Get started: Sign up for GitHub

What you'll need: - GitHub account created - Basic familiarity with repos (we'll cover what you need) - Able to create repos and commit files

3. Code Editor: Cursor or VS Code

What: Your code editing environment with AI assistance Which one: Cursor or VS Code Cost: Cursor has free tier; VS Code is free Why: Build and edit Skills, work with Claude Code, manage your Agentic AI Registry When we use it: Week 1 (Registry setup), Week 2 (Skills creation), Weeks 4-5 (agentic coding) Get started: Download Cursor or Download VS Code

Cursor vs VS Code: - Cursor: Built-in Claude integration, optimized for AI-assisted coding, best for Week 4-5 prototyping. I will also demonstrate examples in Cursor. - VS Code: More familiar if you already use it, requires Claude Code extension

4. Claude Desktop App

What: Desktop application for Claude Cost: Free (included with Claude subscription) Why: Deploy and run Skills locally, develop and test workflows, connect to local tools via MCP (Model Context Protocol), and use the Cowork feature for real-time collaboration

Note on MCP: MCP enables Claude to connect to your local applications and tools. You'll get the most value from this course if MCP integrations are available for the applications you want to use in your workflows and agents. When we use it: Throughout the course—Week 1 (setup), Week 2 (Skills deployment and testing), Week 3 (Subagents and workflow development), ongoing for workflow execution Get started: Download Claude Desktop

What you'll need: - Admin access to install software on your machine - macOS or Windows - Note: The Cowork feature is currently only available on macOS

What you'll do with it: - Deploy Skills to your local environment - Develop and run workflows that connect to your local files and applications - Test Skills and Subagents before sharing them - Connect to local tools through MCP integrations - Use the Cowork feature for real-time collaboration (macOS only)

5. Claude Code (CLI)

What: Command-line interface for agentic coding Cost: Free (usage counts against Claude subscription) Why: Autonomous coding agent that builds, tests, and iterates on your behalf When we use it: Weeks 4-5 (agentic coding workflow) Get started: Install Claude Code

What you'll need: - Terminal/command line access - Comfortable running basic CLI commands (we'll teach what you need)

6. Google Chrome Browser

What: Browser for Claude in Chrome (browser automation) Cost: Free Why: Automate web tasks, extract data, fill forms, orchestrate multi-step processes When we use it: Week 3 (browser automation + Subagents) Get started: Download Chrome

What you'll need: - Chrome installed (not Brave, Edge, or other Chromium browsers) - Ability to install Chrome extensions

7. Claude in Chrome Extension

What: Browser extension that gives Claude control of Chrome Cost: Free beta (as of Jan 2025) Why: Enable Claude to interact with web pages, automate workflows, combine with Skills When we use it: Week 3 (browser automation) Get started: Install Claude in Chrome

What you'll need: - Admin permission to install Chrome extensions - We'll cover installation in Week 1

Wispr Flow (Voice-to-Text)

What: Voice-to-text application for hands-free input and dictation Why: Dramatically speed up writing, communication, and interaction with Claude through natural speech When we use it: Throughout the course—useful for any text input, documentation, or Claude interactions Cost: Varies by platform (check individual app pricing) Get started: Download Wispr Flow

What you'll use it for: - Dictating prompts to Claude - Writing documentation and course notes - Faster communication in Slack - Creating Skills and workflow descriptions - Any text input across your system

Alternatives: Use any voice-to-text solution you prefer—built-in OS dictation, or other third-party apps. Wispr Flow is recommended but not required.

Notion (Agentic AI Registry)

What: Your central repository for business processes, workflows, and AI building blocks Why: Track and organize all the Skills, Subagents, and automations you build throughout the course When we use it: Week 1 (Registry setup), ongoing throughout course Cost: Free tier works; paid tier if you want advanced features Get started: Sign up for Notion

What you'll store here: - Business processes you've decomposed - Workflows you've designed - Skills you've built - Subagents you've deployed - Automations you've created

Alternatives: Obsidian, Coda, Airtable—use what you prefer. We'll show Notion examples but principles apply anywhere.

Slack (Course Community)

What: Private course Slack workspace
Why: Peer collaboration, troubleshooting, sharing wins
When we use it: Throughout the course
Cost: Free (invite-only course workspace)

System Requirements

To participate fully in this course, you'll need:

  • Admin access to install software on your machine
  • Operating system: macOS or Windows
  • Internet connection: Reliable connection for live sessions and API calls
  • Disk space: ~2GB for tools, repos, and project files
  • Permissions: Ability to install browser extensions and CLI tools
  • Time commitment: Minimum 5 hours per week (includes two 90-minute live sessions plus hands-on building time)

Preview: What Happens in Week 1

Week 1 (Configure AI Builder Stack) provides detailed setup instructions for:

  1. Verifying Claude subscription and usage limits
  2. Setting up GitHub
  3. Configuring code editor (Cursor or VS Code) with Claude integration
  4. Installing Claude Desktop and connecting your first MCP tool
  5. Installing Claude in Chrome extension and testing browser automation
  6. Installing Claude Code CLI and verifying setup
  7. Creating your Agentic AI Registry structure in Notion
  8. Testing the full stack with a simple end-to-end workflow

You'll work through setup independently using the provided lessons and documentation. During live sessions, we'll troubleshoot any issues, answer questions, and ensure everyone's stack is working properly before we start building.

Why This Stack?

Every tool serves a specific purpose in your AI builder workflow:

  • Claude.ai → Your command center, where you interact with Claude
  • GitHub → Your version control system, where you manage and share Skills
  • Cursor/VS Code → Your editing environment, where you create and refine Skills
  • Claude Desktop → Your workflow development and execution environment, where you build, test, and run local workflows
  • Claude Code → Your autonomous coding agent, where ideas become prototypes
  • Claude in Chrome → Your automation layer, where you orchestrate web tasks
  • Wispr Flow → Your voice interface, where speech becomes text across your entire workflow
  • Notion (Registry) → Your organizational system, where you track everything you build

Together, these tools form a complete AI Builder Stack—the infrastructure you need to build, deploy, and scale AI systems that work for you.

Questions?

If you're uncertain about any of these tools or whether your setup will work, don't worry. Week 1 includes setup lessons for each tool, and we'll troubleshoot together during live sessions.

Common questions we'll address in Week 1: - "I don't have admin access—can I still participate?" - "Can I use a different code editor?" - "What if Claude in Chrome isn't available in my region?" - "I've never used GitHub—is that a problem?"

Come to Week 1 ready to configure your stack, and we'll make sure you're set up for success.