+
Vibe Coding Workshop · Day 2
AI Vibe
Coding Training
Coding Training
Full Stack · Antigravity · Supabase · Ship It
12 APRIL 2026
9:00AM – 6:00PM
aitraining2u.com
Go deeper — Supabase, MCP, local vibe coding, and deploy your own project.
2 / 9
Four layers, one goal — get your idea live on the internet.
3 / 9
Antigravity is your local vibe coding environment. Instead of building in a browser sandbox, you work on your own machine with full control.
You get real terminal access, real file systems, and real Git — the same tools professional developers use every day, powered by AI.
This is where prototyping becomes production-grade building.
"Browser tools are training wheels. Antigravity is the bike."
4 / 9
An open-source Firebase alternative. Auth, database, storage, and edge functions — all from one dashboard.
5 / 9
MCP (Model Context Protocol) is a standard way for AI tools to connect to external services. Think of it as USB ports for your AI — plug in any capability.
Skills are pre-built MCP connections that give your AI superpowers: browse the web, talk to APIs, read databases, and more.
Instead of writing integration code yourself, you describe what you want and the AI uses the right tool automatically.
"MCP turns your AI from a text generator into an action machine."
6 / 9
Good UX is invisible. When something feels right, users do not think about it — they just use it.
Focus on these fundamentals:
7 / 9
8 / 9
Present your build. Get group feedback. Leave with a personal 30-day AI roadmap.
"You walked in curious. You walk out dangerous."
9 / 9
Tell the AI what to automate in plain language. It generates a Playwright script. You run it.
Working Playwright script you can run immediately
Change the URLs, add more sites, or switch to data extraction
10 / 20
Copy these prompts. Modify for your use case. Run locally or on a schedule.
"Write a Playwright script that visits [URL], extracts the price of [product], and saves it with a timestamp to a CSV."
"Write a Playwright script that opens [URL], fills in [field names] with [values], and clicks Submit."
"Crawl [domain], collect all links, check each one returns HTTP 200, and log any 404s to a text file."
Tell AI: "The element loads dynamically. Add a waitForSelector with a 10s timeout before clicking."
Tell AI: "Add a realistic user-agent header and add random delays between actions (500–1500ms)."
Tell AI: "Add instructions to run this with a cron job every day at 9am on macOS."
Local: run with node script.js — Cloud: deploy to Render or a VPS for 24/7 runs.
11 / 20
Scrape public data automatically and push it to Google Sheets. No manual copy-paste ever again.
Competitor product prices & availability — daily into a Sheets dashboard
Ad copy examples, social proof snippets, campaign headline trends
Job postings from competitor companies — salary benchmarks & role trends
Listing prices, rental yields, or exchange rate movement — automated tracking
// Claude prompt
Write a Node.js script that:
1. Scrapes [URL] for [data field]
2. Appends each row to a Google
Sheet via the Sheets API
3. Timestamps every entry
4. Runs silently on a schedule
Public data only. Respect rate limits. Check the site's robots.txt before scraping. Don't hammer servers.
12 / 20
Non-AI-slop copy, SEO meta, schema markup, and Vercel deploy — the full marketer stack.
npm install -g vercel → vercel → vercel --prod. Your landing page is live in under 2 minutes.You understand the customer better than any developer ever will. That's your unfair advantage — put it in the prompt.
13 / 20
Google Apps Scripts, Sheets automations, and Playwright scheduling — the ops stack.
You know which processes are broken. That process knowledge is the hardest part — AI just needs you to describe it.
14 / 20
Marcus rotates to each person. Use the resource bank — it's all there. Ask for help when stuck.
If stuck: use the debug prompt card · Marcus is rotating · Resource bank is open
15 / 20
Final iteration pass. CI/CD for those ready. Your live URL must work end-to-end before demo day.
Live URL #3 — your personal project. Ready to present at demo day.
That's fine. Demo what you have. A half-built real thing beats a finished fake one.
16 / 20
Write one sentence. Draft one message. Start one thing. That's all it takes.
"I will use vibe coding to
[task] at
[company]
by [specific date]."
The tools don't expire. Your session, your code, your URLs — they're yours to keep and build on.
18 / 20
How vibe coding fits into real project work — real builds, real timelines, open Q&A.
Property search + AI valuation tool. Built and deployed in a weekend sprint. What AI helped with vs got in the way.
Document tracking dashboard for a law firm. Actual build time, prompt workflow, and what needed a real developer in the end.
Financial reporting automation. How prompting workflow evolved through 3 iterations before it worked reliably.
This is your time.
Ask anything about building, prompting, deploying, business use cases, or what you'd do differently on your own projects.
Vibe coding isn't magic. It's leverage. Your quality of thinking determines your quality of output. That hasn't changed.
19 / 20
The tools don't expire. The community doesn't close. Here's how to keep going.
Your sessions, code, and URLs are yours. Open them Monday and carry on from where you left off.
Ask questions, share builds, get feedback. The best prompts in the group come from people solving real problems.
Free, every week. New topics, live demos, and Q&A. Each one builds on what you've learned here.
Next cohort you'll be the one helping others debug. That's when it really clicks.
DM Marcus on LinkedIn or WhatsApp for questions anytime.
20 / 20