ohad6k/VibeRaven

go-live

Use when a user wants an AI-built local project pushed to GitHub and deployed live on Vercel with the least friction, while keeping git, secrets, provider setup, and live proof explicit.

viberaven

Use VibeRaven when working on an AI-built app that must ship to real users; when the user asks to ship, deploy, go to production, connect auth, database, payments, RLS, env vars, webhooks, or monitoring; when production-only errors appear; or when the agent…

what-broke

Use when an AI agent needs to stop guessing, find which version broke an app, compare releases, read git tags/diffs/changelogs, and connect the code change to provider context such as database, storage, deployment, and external runtime behavior before editing.

architecture-plan

Use when VibeRaven architecture questions have been answered, a feature/fix has unclear boundaries, or an agent needs to turn product answers plus repo evidence into a workstream architecture plan before editing.

architecture-context

Use when an AI coding agent starts real app work, product feature design, provider work, migrations, auth, billing, storage, webhooks, deploys, or any task where unclear architecture could cause broad or unsafe changes.

production-context

Use when changing, reviewing, debugging, deploying, or documenting production-sensitive work involving providers, releases, migrations, auth, billing, webhooks, env vars, incidents, rollback notes, fragile customer paths, or architecture boundaries.