Postgres by prompt
Neon MCP provisions a real database. Drizzle ORM owns the schema. AI runs the migration.
Google sign-in
Neon Auth wires Google as the provider. The OAuth consent screen is your one human moment.
A real full-stack feature
A guestbook with sign-in, server actions, optimistic UI, and revalidation — built end-to-end in one class.
Learning objectives
By the end of this session, you should be able to:- Provision a production Postgres database and an auth system by prompt — Neon MCP creates the DB, Drizzle defines the schema, and Neon Auth wires Google login, all through one conversation.
- Recognise and execute the OAuth-consent manual moment — the one step the AI cannot do for you — without panicking or skipping ahead.
- Ship a full-stack feature end-to-end (signed-in visitors leaving messages on your site) in a single 2-hour class, even though you’ve written zero lines of server code.
Core topics
- What “going full-stack” actually means when AI writes the stack: a database, an auth layer, server actions, and a UI — all at once.
- Drizzle ORM as a type-safe schema definition the AI can reason about.
- Neon Auth — why it exists and why it’s the fastest path from “no login” to “signed-in users” for beginners.
- Env-var plumbing across three environments (local, preview, production) and why AI doing this is a superpower.
- The OAuth trust dance: why Google requires human consent and where the callback URL must match.
Tools introduced this week
Prerequisites: Complete Week 3 — Add an AI Clone first. The guestbook lives on the same
my-portfolio site you’ve been growing since Week 2.Download Week 4 PDF
Full lecture · 679 KB — Session plan, hands-on lab steps, OAuth troubleshooting.
Continue to Week 5
Image uploads with Vercel Blob