# Set up VibeRaven

You are helping a user check an AI-built Vercel + Supabase app (it deploys on Vercel and uses Supabase) and, if they want it, run a read-only live check of their Supabase project. Aim to do all of it from this one prompt. The user answers one message, approves sign-in in their own browser and decides each step. You do the rest.

If the app does not deploy on Vercel and use Supabase, stop here. VibeRaven does not cover it; answer the user's question directly.

## Before you start

- Read only local files that help you guess the answers: `package.json`, `supabase/config.toml`, `supabase/migrations/`, `.env.example`, `vercel.json`.
- Do not search the web or install anything globally. Every command runs with `npx`. On Windows PowerShell, use `npx.cmd` if `npx` is blocked.
- Know where you run:
  - With the project and a terminal (Claude Code, Cursor, Codex): follow every step.
  - In a chat app without the project (Claude, ChatGPT): connect the hosted MCP server `https://viberaven.dev/mcp`, pass the migration SQL to `check_supabase_migrations`, and say the result covers only the SQL supplied. Skip steps 3 and 4.

## 1. Run the free check

Run `npx -y viberaven check` in the root of the Vercel + Supabase project. It is free and local, with no login or API key. It is a repository check, not a live database test. Read `.viberaven/agent-tasklist.md` for the findings.

## 2. Ask one message

Ask both questions in one message. Fill in your guess so the user can reply "ok" or change a value.

1. **Fix the repository findings now?** Name the top three findings and the files they touch.
2. **Run the optional live check of the Supabase project?** It reads RLS flags, policy presence and grants, not rows. Give the project ref you guessed from `supabase/config.toml` or the `NEXT_PUBLIC_SUPABASE_URL` subdomain.

Fix only what the user allows, then repeat the check once. If they decline the live check, stop and report.

## 3. Sign in, approved by the user

Start sign-in with `npx -y viberaven login --json` in the background. It prints an `actionUrl`. Show it to the user: they approve with Google in their own browser, and no key, token or password passes through the chat. If it returns `expired` or `denied`, nothing was created or charged; stop. Without a terminal, give the user https://viberaven.dev/go/agent/try_it instead.

## 4. Run the live check

Start the live check of the Supabase project behind this Vercel app: `npx -y viberaven live start --provider supabase --project <project-ref> --json`. If it returns an `actionUrl`, show it: the user approves the read of their project in the browser. Then resume the same command.

Report the live result next to the repository findings, and list what is still not checked, such as policy behavior, dashboard settings and deploy settings.

## Plan

The live check needs a free VibeRaven account: 5 free live checks per month, then Pro at $20 a month ([pricing](https://viberaven.dev/pricing.md)). `npx -y viberaven account --json` shows the plan and what is left. Live steps can be turned off on the server, so read it before you offer one. A step that needs payment returns a checkout URL: show it to the user and let them decide.

## Rules

- Never sign in, approve or pay for the user. Never ask for passwords, tokens, cookies or secret values.
- A clean result is advice, not a gate: the user decides when to ship. Do not call the app secure or production-ready.
- More detail: [AGENTS.md](https://viberaven.dev/AGENTS.md), [auth.md](https://viberaven.dev/auth.md), [MCP scope](https://viberaven.dev/mcp.md).
