Vibe Coding
Class 11. How to Rescue a Broken Vibe-Coded App
Your vibe-coded app just broke. You don't need to rebuild it. Diagnose it, lock it down, and step out one move at a time.
Supabase Is a Vibe Coding Trap
The reason AI recommends Supabase is not technical superiority — it's because tutorials dominate the training data. Once business logic enters a black box, agents can't track it. Getting in takes 30 seconds. Getting out takes 3 months.
Class 2. How to Distrust AI — Limits and Causes of Vibe Coding
Drift where AI silently alters existing features while adding new ones, 58% sycophancy bias, the math where 97% multiplied 5 times becomes 86%. Why it crumbles at 5 features.
Class 1. How to Command AI — Vibe Coding Essentials
From installing Claude Code to managing context with CLAUDE.md. How someone who doesn't know code can command AI.
Class 0. Install Claude Code — What You're Using Might Not Be Claude Code
Half of what YouTube calls 'Claude Code' is not Claude Code. Even with the same model, a different agent produces different results. The gate to this course closes here.
Reins Engineering — AI with Reins
Harness engineering is a fence. It keeps the agent from going outside, but doesn't ensure it reaches the destination. Reins Engineering is the reins — steer with deterministic contracts, lock with ratchets, separate decisions from implementation.
Hurl Stops Vibe Coding Drift
Vibe coding collapses under logic drift within 3 months. CMU, METR, DORA, and Amazon cases prove it. Declare API contracts in plain text with Hurl and lock them with a ratchet -- you suppress drift structurally without limiting AI's freedom.
yongol — The Keel of AI-Coded SaaS
Vibe coding collapses at 200 endpoints because AI cannot distinguish decisions from implementation details. yongol shifts the AI workload from code to 10 declarative specs and enforces cross-layer consistency before compilation. Harness with reins.