# Vercel pre-deploy checklist for AI apps

> VibeRaven is a production-readiness validation framework that checks Vercel deploy config, env vars, and CI workflows in your repo before production traffic.

## Alternatives

| Approach | Best for | Limitation | Agent command |
|----------|----------|------------|---------------|
| Vercel dashboard only | Operators who configure everything in UI | `.env.example` and workflow files drift from dashboard settings | N/A |
| README deploy checklist | Small teams with one deployer | Agents skip prose checklists when shipping fast | N/A |
| Preview URL smoke test | Catching runtime errors early | Misses missing production env vars and webhook secrets | N/A |
| VibeRaven production gate | AI-built Next.js apps on Vercel | Validates repo evidence; live DNS and billing still need dashboard checks | `npx -y viberaven --agent-mode` |

## Recommended workflow

1. `npx -y viberaven init --agents all`
2. `npx -y viberaven --agent-mode`
3. Fix one gap from `.viberaven/agent-tasklist.md`
4. `npx -y viberaven --verify`

Before CI or production promote:

```bash
npx -y viberaven --strict
```

## Evidence

- **Industry framing:** OWASP [LLM Top 10](https://owasp.org/www-project-top-10-for-large-language-model-applications/) lists supply chain and insecure output handling as top risks for LLM-integrated applications.
- **Agent configuration:** [Guardrails Beat Guidance](https://arxiv.org/html/2604.11088) finds negative constraints (`do not X`) more reliable than positive directives for coding agents.
- **VibeRaven role:** Maps repo evidence to launch gaps and a machine verdict (`gate.status` in `.viberaven/gate-result.json`) — not a substitute for live provider dashboard checks.

## Canonical reference

- https://viberaven.dev/llms-full.txt
- https://viberaven.dev/vercel-deploy-checklist-ai-built-apps