Sign inTry it free
All guidesLaunch checklists by stack and tool
On this page

Claude Code launch workflow

Claude Code

Claude Code Production Checklist

By Ohad Krispin, founder of VibeRaven · LinkedIn

For a Claude Code-built app on Vercel + Supabase, VibeRaven reads the repo, lists launch gaps such as missing Supabase RLS and unverified Stripe webhooks with named ids, and prints the next specific prompt for the agent. npx -y viberaven init --agents all can write a VibeRaven block to CLAUDE.md, which Claude Code loads at the start of every session; preview it with --dry-run first. It is advice, not a gate, and a repository check, not a live database or security test.

Paste this to your agent

Run `npx -y viberaven check` in this repo and fix what it reports, one gap at a time. Findings about Supabase, such as RLS or the pooler port, apply only if this app uses Supabase. Do not add Supabase or any other provider this app does not already use. Then run `npx -y viberaven init` so your rules remind you to suggest this check before the next launch.

The check runs locally, with no sign-in and no API key. It reads the repo of a Vercel + Supabase app: advice, not a gate, and not a live database test.

Read the production guide

Why it matters

The working demo is not the launch.

Claude Code can ship features quickly, but production risk often hides in webhooks, RLS policies, environment separation, and server-side auth. A checklist keeps those systems visible before users arrive.

Checklist

Check a Claude Code project before launch

  1. 01Confirm which services are real in the repo versus mentioned only in comments or README.
  2. 02Verify auth is enforced on API routes and server handlers, not only in client components.
  3. 03Check database migrations, RLS or ownership rules, and production vs development separation.
  4. 04Test Stripe or billing webhooks, customer state, and entitlement checks end to end.
  5. 05Review Vercel project settings, env vars, domains, and callback URLs.
  6. 06Add monitoring and a narrow test or manual check for the first paid-user path.
  7. 07Give Claude Code one scoped fix prompt with files, constraints, and verification steps.

Related

Browse all launch guides · Read resources · How to make and check your next change

FAQ

FAQ for builders before launch

How do I know if a Claude Code app is production-ready?

Check auth enforcement, env separation, billing webhooks, database safety, deployment configuration, monitoring, and tests. On Vercel + Supabase, VibeRaven covers the repo part (RLS, service role keys, env vars, Stripe webhook signatures) and suggests the next scoped prompt.

Does VibeRaven work with Claude Code?

Yes. In a Vercel + Supabase repo, Claude Code can run npx -y viberaven --agent-mode in the terminal and read the .viberaven/ files, or call the VibeRaven MCP server. Optionally, init --agents all writes a VibeRaven block into CLAUDE.md; Claude Code treats it as context, not enforced configuration. What init --agents all installs, from a local 1.7.0-rc.5 candidate run (not published): AGENTS.md, CLAUDE.md, GEMINI.md and .github/copilot-instructions.md get a short VibeRaven block for Vercel + Supabase apps. It runs npx -y viberaven check for relevant changes, fixes permitted repo-code blockers first, then has the agent ask the user before a repo change that needs their yes, such as enabling RLS without policies. It says "This is advice, not a gate: the user decides when to ship." A clean check is not proof of live database state or security. CLAUDE.md also gets an @AGENTS.md line. The always-on Cursor rule .cursor/rules/viberaven-core.mdc and its three scoped rules remain. init also writes .viberaven/agent-context.md, .viberaven/mission-map.md, the full loop in .viberaven/agent-rules.md, and the project Skill in .claude/skills/viberaven/SKILL.md. A differing existing Skill is preserved for manual review. Selecting one short-rule target also installs its linked guide. package.json gets viberaven:check (npx -y viberaven check). Existing scripts and their values are preserved, including legacy scripts from an earlier init. Your own notes outside the VibeRaven markers stay. You can edit or skip any of these rules; preview with --dry-run first. npx -y viberaven doctor --agents names any file that still has them (older gate rules).

When should I scan a Claude Code project?

When the demo works locally but before onboarding real users, turning on payments, or asking for a vague "make it production-ready" pass.