# VibeRaven Agent Rules

VibeRaven is the Agent Context + Production Gate.

Add these rules to `AGENTS.md`, `CLAUDE.md`, or `.cursorrules`, or run:

```bash
npx -y viberaven init
```

Use dry-run first when you want to preview local rule changes:

```bash
npx -y viberaven init --dry-run
```

## Supported Instruction Files

Use `npx -y viberaven init --agents all` to install VibeRaven rules into supported agent instruction files:

- `AGENTS.md`
- `CLAUDE.md`
- `.cursor/rules/viberaven-core.mdc`
- `.cursor/rules/viberaven-supabase-rls.mdc`
- `.cursor/rules/viberaven-deploy.mdc`
- `.cursor/rules/viberaven-payments.mdc`
- `.cursorrules`
- `.github/copilot-instructions.md`
- `GEMINI.md`
- `.devin/rules/viberaven.md`
- `.windsurf/rules/viberaven.md`
- `.clinerules/viberaven.md`
- `.roo/rules/viberaven.md`
- `.junie/guidelines.md`
- `.rules`

Rules:

- When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, error handling, env vars, or provider dashboard checks come up, run `npx -y viberaven --agent-mode`.
- If VibeRaven prints `LOGIN_URL_READY`, open that exact URL for the user. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal alive while the user approves.
- Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context. If the tasklist says `CRITICAL GAPS DETECTED` or `PRODUCTION GATE NOT CLEAR`, fix one listed repo-code gap before deploying.
- Read `.viberaven/agent-summary.md` second for scan context.
- Read `.viberaven/launch-playbook.md` third for the full checklist.
- Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for the next focused fix.
- After one fix, run `npx -y viberaven --verify`.
- Before deploy or CI pass, run `npx -y viberaven --strict`.
- For Vercel + Supabase, run `npx -y viberaven audit --vercel-supabase`.
- Check Supabase RLS evidence, service role key exposure, and serverless database connection settings such as port 6543 instead of direct runtime port 5432.
- Do not claim provider dashboard checks are fixed by repo-code edits.
- For cleanup, only use `npx -y viberaven clean --plan`.