S1E2: StreamSaga - AI Coding rules; Google Antigravity; Supabase: Authentication

Описание: How to Tame AI Agents: Defining Rules & Supabase Auth (S1E2)

In this episode, we focus on control. While AI coding agents (like Google Antigravity) are powerful, they often go "rogue" if you don't give them strict instructions. Today, I show you how to build a scalable "AI Rules" Framework to force the agent to document its work, follow architectural patterns, and stop hallucinating utility functions.

We also finally start the backend implementation for StreamSaga, moving from mocks to real data. We set up Supabase Auth from scratch (including Twitch Login), establish our database connection, and debug the agent when it fails to update the architecture file.

What we covered:
Coding Rules Framework: Creating a `.agent/rules` file to standardize AI behavior (e.g., "Always consult `ARCHITECTURE.md` first").
Supabase Authentication: Implementing Sign Up, Sign In (Email + Twitch), and handling the auth callback flow.
Google Antigravity Workflows: Testing the new "Workflow" feature to automate documentation updates.
Architecture-Driven Development: Why maintaining a "Source of Truth" document is the only way to build complex apps with AI.

----

Project repo: https://github.com/Alirun/StreamSaga
Framework repo: https://github.com/Alirun/stream-fram...

----

00:00 Intro & Sound Check
05:12 Introducing the "Stream Framework"
11:59 Why You Need "Coding Rules" for AI Agents
17:51 Rule #1: Force an Implementation Plan
22:26 Rule #2: The Architecture Document (Crucial)
30:52 Preventing Hallucinations
37:11 Creating the ARCHITECTURE.md File Live
46:00 Setting Up .agent/rules in Google Antigravity
54:31 Implementing Supabase Auth (Replacing Mocks)
01:09:44 Securely Handling Env Variables with Agents
01:13:51 Reviewing AI-Generated Server Actions (Next.js)
01:17:05 Debugging Auth Flows & Confirm Emails
01:27:16 Setting Up Twitch Login Integration
01:39:49 The Agent Failed to Update Docs (Debugging Rules)
01:56:03 Creating a Custom "Update Architecture" Workflow
02:07:00 Wrap Up & Next Stream Plans