Slide 1 / 20
AIML@TU Meeting Link QR Code

Vibe Coding Workshop

October 24, 2025 · AIML@TU

Attendance Check-In

Attendance QR Code

Take 30 seconds to log your attendance so we can keep track of participation and follow up with resources.

Club Announcements

Before we dive into the vibes…

🎃
Root66 + WiCyS Halloween Party

Megan is sharing a quick rundown on the Root66 x WiCyS Halloween volunteer opportunity—hang tight after the announcements if you want the details on how to help.

Tonight's Spotlight

🎤 Megan has the info · 🎃 Shifts still open · 🧡 Support WiCyS Tulsa

✈️
Dallas Live From Sweden

Dallas is presenting at a global AI conference in Stockholm this week! Drop a shout-out in Discord, keep an eye out for his session recaps, and bring questions so we can debrief when he’s back.

Send Good Vibes

📸 Look for daily photo drops · 🧠 Ask about new research collabs · 🇸🇪 Cheer him on from Tulsa

Use arrow keys or spacebar to navigate the deck.

Root66 + WiCyS Halloween Party Deck

Full slide Megan will walk through tonight

Trouble viewing? Open the PDF in a new tab.

Last Meeting Recap

October 10 · Officer Welcome & Workshop Night

Highlights

  • Congrats to the newly elected 2025-26 leadership team 🎉
  • Shared the final Multi-Club Mashup run-of-show and booth assignments
  • GitHub quickstart: branching, pull requests, and Codespaces workflow
  • Mini vibe coding workshop featuring the Hurricane Escape challenge
  • Community wins: scholarships, hackathons, and Dean’s Lunch recap

Meet the 2025-26 Leadership Team

Your 2025-26 AIML@TU Officers

Dallas Elleman
Graduate President of AI
Joe Shymanski
Graduate President of ML
Ty Devito
Undergraduate President
Tim Flavin
Graduate Vice President
Maura Toney
Undergraduate Vice President
Jacob Brue
Graduate Secretary
Megan Brue
Undergraduate Secretary
Nouman Ahmed
Graduate Treasurer
Catherine Tsaowimonsiri
Undergraduate Treasurer
Jacob Regan
Graduate Director of Outreach
Megan Smith
Undergraduate Director of Outreach
Yasmina Bruton
Director of Marketing
Big thanks to our officers for keeping the vibes high and projects moving! 🎉
QR code instructions

VibeCoding Workshop

AIML Club @ The University of Tulsa · October 24, 2025

Presenter: Ty DeVito

Tonight’s vibe: bright colors, collaborative energy, and AI copilots that help us ship faster. Follow along as we explore the landscape, compare models, and get hands-on with the Gemini CLI.

Navigation tip: Intro → Landscape → Benchmarks → Setup → Try it

Use arrow keys or spacebar to navigate the deck.

What Is Vibe Coding?

Creative, team-based building with AI copilots

The Mindset

  • Start with a playful prompt, pair up, and let curiosity lead the build
  • Leverage AI tools for scaffolding so humans can focus on ideas and polish
  • Iterate in short loops: draft → review → refine → demo
  • Share your process, not just the finished product—teach the room what you learned

AI Ecosystem Powering the Vibes

  • OpenAI: ChatGPT + GPT-4o mini for rapid prototyping and natural-language coding support
  • Google (DeepMind): Gemini models and the Gemini CLI for multimodal experimentation
  • Anthropic: Claude 3.5 for thoughtful code reviews, planning, and safety guardrails
  • We mix-and-match these assistants so every team can find the right co-pilot for the task

Why VibeCoding For Beginners?

Lower the barrier, keep the learning

Starter Benefits

  • Kick the blank-page blues—AI drafts scaffolds so you can iterate immediately
  • Use copilots to explain code, surface edge cases, and suggest test ideas
  • Every session ends with something shipped, plus a diff you can study afterward

Level-Up Mindset

  • We treat AI as a teammate, not a cheat code—humans own specs and quality
  • Review the generated work, apply judgment, and keep your Git history clean
  • Build confidence faster by pairing curiosity with structured feedback

The VibeCoding Loop

Spec → change → test → diff → refine

Your Role

  • Define goals, guardrails, and acceptance tests before asking for help
  • Decide what “done” looks like and when to ship or iterate
  • Keep version control tight—commit in small, reviewable chunks

AI Copilot Role

  • Propose edits, run tools, summarize diffs, and surface blockers
  • Loop with you: implement → run checks → report → wait for approval
  • Great results come from clear prompts and fast feedback cycles

Quick Vocab Check (1/2)

Building a shared language

Core Terms

  • Terminal: Text-based interface where you run commands
  • CLI: Command-line tool you interact with inside the terminal
  • Directory: Your current folder; commands act on files inside it

Working Smoothly

  • Know where you are: use pwd (macOS/Linux) or cd (Windows)
  • Use ls/dir to list files before running AI-powered actions
  • Keep a scratch/notebook file for prompt ideas and TODOs

Quick Vocab Check (2/2)

Models, context, prompts

AI Concepts

  • Model: The AI brain (Gemini, Claude, GPT-5, etc.)
  • Context window: How much code/text it can “remember” per request
  • Prompt: Your instructions—include goals, constraints, and tests

Prompting Tips

  • Write like a mini spec: what to change, where, and why
  • Mention tooling allowed (tests, linters, build command)
  • Ask for a diff and short rationale before you approve writes

AI Landscape — The Big Players

Closed-source leaders + emerging challengers

Leading Platforms

  • OpenAI: GPT-5 & GPT-5 Thinking, Codex CLI integrations
  • Google DeepMind: Gemini 2.5 Pro & Flash, Gemini CLI
  • Anthropic: Claude 4 family (Opus/Sonnet) for thoughtful coding
  • xAI: Grok series focused on fast iterations

Why It Matters

  • Different strengths: reasoning, speed, cost, tooling support
  • APIs evolve quickly—watch launch notes and evals
  • Club goal: help you try multiple copilots and compare

Open-Source Models — Why Care?

Take control of your stack

Key Advantages

  • Privacy: run locally/offline when data must stay on your machine
  • Cost: pay for compute once vs. ongoing API fees
  • Customization: fine-tune to your domain or coding style

Models To Explore

  • OpenAI gpt-oss (20B/120B), Google Gemma 3 family
  • DeepSeek-R1 Distill for reasoning-heavy tasks
  • Qwen2.5 variations for multilingual/dev workflows
QR code instructions

Tonight’s Tool: Gemini CLI

Google’s command-line co-pilot for code, prompts, and media

Why We’re Using It

  • Lightweight interface to run prompts and iterate without leaving the terminal
  • Supports text, code, and image context—perfect for vibe coding mashups
  • Built-in project workspaces keep experiments organized per team

What You’ll Need

  • Gemini CLI installed (we’ll walk through it together)
  • No API key required—sign in with your Google account during auth
  • Optional: enable streaming mode for real-time output
  • Stay tuned—setup steps and starter commands are coming up next

Step 1 · Get Your Terminal Ready

Fresh laptop? Start here.

macOS

  • Press ⌘ + Space → type Terminal → Enter
  • Install Homebrew (needed for Node installs):
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
  • Follow prompts (press Return, enter password). Let it finish (takes a few minutes)
  • Confirm with brew --version; install Command Line Tools if macOS asks

Windows

  • Press Win + X → choose Terminal (Admin) or open Windows PowerShell
  • If SmartScreen warns, click More info → Run anyway
  • Optional: sign into the Microsoft Store once so winget is enabled for later
  • Check PowerShell version with $PSVersionTable.PSVersion (Windows 10/11 default is fine)

Step 2 · Install Node.js & npm

Core runtime + package manager

macOS

  • Run brew install node (installs both Node.js and npm)
  • Alternative: download the macOS LTS .pkg installer from https://nodejs.org and follow the wizard
  • Restart Terminal, then verify:
    node -v and npm -v
  • Version numbers (e.g., v20.x) mean you’re ready for the next step

Windows

  • Option A: download the Windows LTS installer from https://nodejs.org, ensure “Add to PATH” stays checked, then run it
  • Option B: winget install OpenJS.NodeJS.LTS
  • Close & reopen Terminal, verify with node -v and npm -v
  • No versions? Re-run the installer or confirm PATH includes AppData\\Roaming\\npm

Step 3 · Install Gemini CLI

Grab the tool from npm

macOS

  • Run npm install -g @google/gemini-cli
  • Approve the password prompt if it appears
  • Verify install with gemini --help
  • Permission issues? Try brew doctor or manage Node via nvm

Windows

  • Open Terminal/PowerShell (Admin if needed)
  • Run npm install -g @google/gemini-cli
  • Allow SmartScreen/antivirus prompts; verify with gemini --help
  • If blocked, adjust execution policy (Set-ExecutionPolicy RemoteSigned) or ensure npm is on PATH

Step 4 · Sign In

Authenticate the CLI with your Google account

macOS

  • Run gemini from any folder (Terminal)
  • Type /auth and press Enter
  • Browser opens → sign in with your Google account → copy the code
  • Paste the code back into Terminal and wait for the “Authenticated” message

Windows

  • Launch gemini in Windows Terminal/PowerShell
  • Run /auth and log in with Google when Edge opens
  • If the callback is blocked, use the headless URL shown in the CLI and paste the code manually
  • Confirm the CLI prints “Authenticated” before moving on

Step 5 · Launch Your First Mission

Set the folder, then let Gemini drive

macOS

  • cd ~/code/demo-project (clone something small if you need a repo)
  • Run ls to double-check you’re in the right folder
  • Inside gemini, paste:
    Refactor utils/date.js to avoid moment.js, add ISO parsing, and write Jest tests. Respect existing style. Show a diff before saving.
  • Watch the plan, approve edits, and ask for clarifications if something looks off
  • Run npm test before committing to confirm everything passes

Windows

  • cd C:\Users\<you>\code\demo-project (clone a repo if you need one)
  • Use dir to confirm the files you expect are there
  • Try:
    Identify flaky test in tests/auth.spec.ts; stabilize it and explain root cause. Keep changes minimal. Propose a test naming convention.
  • Ask for a diff + rationale before approving writes; iterate if needed
  • Re-run your test command (e.g., npm test) and stage the clean diff when satisfied

Let's Build Something Ridiculous! 🎮

Today's Vibe Coding Challenge

🦖 TU Dino Game: "Hurricane Escape!" 🌪️

Build a Chrome dino-style game where Hurricane (TU's mascot)
jumps over homework assignments and dodges pop quizzes!

🏃‍♂️

Hurricane Runs!

Auto-running mascot
Jump with spacebar

📚

Dodge Obstacles

Homework stacks
Pop quiz papers

🏆

High Score

Leaderboard
Share on GitHub!

📖 Essential Resources

💡 Pro Tips for Vibe Coding

  1. Start with a clear description of what you want
  2. Use AI to generate boilerplate, focus on logic
  3. Iterate quickly - "make it work, then make it good"
  4. Review AI code - understand what it generates
  5. Have fun and experiment!

Ready to start? Let's collaborate! 🚀

🎮 Get the Starter Code

Thank You!

See you in two weeks — same time, same place

🙌

Grateful for the energy you brought today

Next Meetup:
Friday, November 7, 2025 · 12:00 PM – 1:00 PM
Graves Commons, Rayzor Hall · Food: TBD
💬

Share wins in Discord

🧪

Try a fresh Gemini mission

🤝

Bring a friend next time

Keep the vibes going—drop your prompt ideas and demos, and tag us when you ship something wild!

Safe travels, good luck on projects, and stay curious. ✨
Use arrow keys or spacebar to navigate