63 commands. You only need three.

Full check, 0-100 score, SHIP or DON'T SHIP verdict, fix list. `/launch-check quick` checks only security, database and payments

All security checks

All database checks, plus production checks that `/launch-check` does not run (see below). `/launch-database basic` skips them

All payment checks, plus production checks that `/launch-check` does not run (see below). `/launch-payments basic` skips them

All legal checks

All SEO checks

All speed, mobile and accessibility checks

All reliability checks, plus production checks that `/launch-check` does not run (see below). `/launch-reliability basic` skips them

Fixes the problems found, worst first. Add `all`, a severity such as `critical`, or check IDs such as `KEY-01` to choose what to fix

Shows the last report; `/launch-report html` exports a page to share

Current score and history

Day-by-day plan to get ready for launch

Leaked keys in code, config files and build output

Keys and `.env` files still recoverable from old commits

Login, sessions, password reset, routes that work without logging in

Attempt limits, and paid services (AI, email, SMS) anyone can run up

Can users reach each other's data? Are admin features protected?

File type and size limits, safe storage, private files

SQL injection, command injection, cross-site scripting

Security headers, CORS, debug leaks in production

Vulnerable, fake or outdated packages

Prompt injection, AI tools without permission checks, leaked instructions

Row-level security, views and database functions

Supabase Storage: private files that are public, files anyone can overwrite

Firestore, Realtime Database and Storage rules

Connection, user rights, encryption, pooling, indexes, constraints

Missing migrations, changes that would destroy data, seed scripts

Can users delete their account and get their data? Is everything removed?

Backups, plan risks, uptime monitoring

Queries in loops, lists with no limit, filtering in code, deep paging, slow search, no query timeout

Balances and stock that lose updates, missing transactions, coupons used twice, unsafe retries, deleted data that comes back

Pooler settings that crash queries, too many connections, migrations that lock tables, raw database errors shown to users

Checkout, subscriptions and refunds (Stripe, Dodo Payments, Lemon Squeezy, Polar, Paddle)

Signature verification, duplicates, missing events

Does the pricing page match what is charged and delivered?

Events applied out of order, renewals matched to nobody, trial and past-due users handled wrong, double billing, access cut too early on cancel, no resync after a missed webhook

Charges sent twice, provider lists read one page only, unpinned API version, no payment event log, swallowed payment errors

Titles, descriptions, canonical addresses, robots.txt, not-found pages

Link previews on X, LinkedIn, WhatsApp, Slack

Can ChatGPT, Claude and Perplexity read and describe the site?

Oversized and badly loaded images

Phone layout, tap targets, forms

Labels, contrast, keyboard use

Error handling and logging

Missing or unsafe environment variables

Build settings, host limits, scheduled jobs, rollback

HTTPS, redirects, callback addresses, email delivery records

Calls with no timeout, background work the host drops, retry storms, lost jobs, cron jobs that run twice, in-memory state, no graceful shutdown, memory that keeps growing

Caches that show one user's page to another, database changes that break the running version, open tabs that break after a deploy, no off switch for risky features

Reviews the landing page as a first-time visitor

Are visits, signups and purchases measured?

Writes a privacy policy from what the code really collects

Writes terms of service that fit the product

Writes a refund policy

Removes the need for a cookie banner, or adds a working one

Generates a sitemap and robots.txt

Adds structured data (JSON-LD)

Installs error tracking

Installs analytics and the key events

Launch posts for X and Reddit in your voice

Product Hunt taglines, description, first comment, schedule

Launch-day checklist tailored to your project

Finds the right command for what you want to do

Choose and save how much checks spend: `economy`, `standard` or `deep`, or `ask` to be asked every time

Checks the install. Use it when a command is missing or not working