Session #2:

Building Blocks Overview

45 minutes | Understanding the Tools

The Toolchain

Today you'll work with:

  • Git - Saves versions of your work
  • GitHub - Stores your code online
  • Cursor - AI editor that speaks human language
  • Render - Hosts your game on the internet
  • MCP - Connects Cursor to external tools

You'll speak to Cursor. Cursor orchestrates the rest.

Part 1: Understanding Git (15 min)

What is Git?

Think of it as "Track Changes" for code.

  • Save snapshots of your work as you build
  • Undo mistakes without losing everything
  • See what changed and when

The Four Key Concepts

1. Repository (Repo)

  • A folder that contains your entire project
  • Lives on GitHub so it's backed up

2. Commit

  • A saved snapshot of your work
  • Like clicking "Save Version" in Google Docs
  • Includes a message: "Added lobby feature"

3. Branch

  • A separate timeline to try new things
  • Main branch = production (what's live)
  • Feature branch = experimental work

4. Pull Request (PR)

  • "Hey, review my changes before merging"
  • Moves code from feature branch → main branch
  • Safety check before going live

Hands-On: Create Your Repository (10 min)

Everyone do this now:

  1. Go to github.com
  2. Click "New repository"
  3. Name it: simon-game-training
  4. Set to Public
  5. Do NOT initialize with README
  6. Click "Create repository"

Verification:
You should see an empty repo with setup instructions.

Don't follow those instructions - we'll use Cursor instead.

Part 2: Understanding Render (10 min)

What is Render?

It takes your code and makes it live on the internet.

  • You'll get a URL: your-game.onrender.com
  • Anyone can visit and play
  • Automatically rebuilds when you update code

Why Do We Need It?

Your laptop → The Internet

Right now, your game only runs on your laptop.

Render:

  • Hosts your frontend (what players see)
  • Hosts your backend (game logic, multiplayer sync)
  • Gives you a shareable link

By 5pm, you'll text your friends the link and they can play.

Hands-On: Render MCP Setup (10 min)

Step 1: Get Your Render API Key

  1. Go to render.com (you should already have an account)
  2. Click your profile → Account Settings
  3. Scroll to API Keys
  4. Click "Generate New Key"
  5. Copy the key (you won't see it again!)

Step 2: Configure Cursor

  1. Open Cursor
  2. Go to Settings → MCP
  3. Click "Add Server"
  4. Select "Render"
  5. Paste your API key
  6. Click "Save"

Step 3: Verification

In Cursor, open the chat and type:

"Show me my Render services"

Expected response:
"You have no services yet" or an empty list.

If you see this → MCP is working!

You're Ready to Build

What you now have:

  • ✅ Empty GitHub repo (version control ready)
  • ✅ Cursor connected to Render (deployment ready)
  • ✅ Understanding of the toolchain

Next up:
We start building the context - the brain of your game.

Text