LaunchReadyKit

A launch audit you run inside Claude Code

Know what's broken before you launch.

LaunchReadyKit is a pack of 41 agents you install into Claude Code. Type /launch-check and they audit your app's security, database, payments and SEO, then hand you a score and a list of what to fix.

Get the kitSee a sample report

440 checks · read-only, your code isn't changed · one-time payment

The problem

Your app looks finished. Is it really ready?

Everything can work when you click through it and still fail on launch day. The problems that hurt most are the ones no demo shows: who else can reach the data, what happens when a payment arrives twice, what still points at your laptop.

Your app

  • Login works
  • Checkout works
  • Dashboard works
  • Users can upload files

What LaunchReadyKit finds

  • Admin API trusts client-provided role
  • Webhook accepts duplicate events
  • Production callback points to localhost
  • Uploaded files are publicly readable

Audit workflow

One command. Five steps.

The check finds the problems and proves them. Nothing in your code changes until you ask for the fix.

/launch-check

Reads your code

  1. 01

    Discover

    Maps your project: framework, database, login, payments and every server route.

  2. 02

    Audit

    Specialist checkers inspect each area in parallel. Nothing is changed.

  3. 03

    Verify

    Serious findings are re-opened at the cited line. False alarms are removed.

/launch-fix

Changes your code

  1. 04

    Fix

    You run the fix command. Problems are fixed worst first, and you review the changes.

/launch-check

Reads your code

  1. 05

    Re-check

    A new check shows what is fixed, what is new and what is still open.

Coverage

440 checks across everything that breaks on launch day.

  • Security

    81 checks

    Leaked keys, login, access control, injection, headers, dependencies.

    • Secret key in client code
    • Record readable by changing an ID
    • Route works without login

  • Production

    62 checks

    Environment settings, error handling, deploy config, safe releases, domain and email delivery.

    • Callback points to localhost
    • Build errors hidden by config
    • Errors reported nowhere

  • Payments

    62 checks

    Checkout, webhooks, subscriptions, refunds, billing kept in sync and the pricing page.

    • Price comes from the browser
    • Webhook signature not verified
    • Cancelled plan keeps access

  • Database

    70 checks

    Access rules, storage buckets, migrations, backups, slow queries and account deletion.

    • Table readable by anyone
    • Private files in a public bucket
    • Migration drops a column

  • SEO

    43 checks

    Titles, sitemap, robots.txt, canonical addresses, link previews, structured data.

    • Site hidden from search engines
    • Default page title
    • No preview image

  • Accessibility

    18 checks

    Labels, contrast, keyboard use and layouts that work on phones.

    • Form field without a label
    • Text too faint to read
    • Button unreachable by keyboard

  • Analytics

    7 checks

    Whether visits, signups and purchases are measured on launch day.

    • Purchases not tracked
    • Tracking before consent
    • No signup event

  • AI

    19 checks

    Prompt injection, AI tools that act without permission checks, AI search readiness.

    • AI tool deletes any record
    • Browser chooses the model
    • Site unreadable to AI search

Also covered: legal pages, page speed and the landing page itself.See all checks by area →

What's inside

A whole launch team, in plain files you can read.

41
Agents
72
Skills
63
Commands
440
Checks

See all 41 agents →See all 63 commands →

The report

Every finding tells you where, why and how to fix it.

No vague warnings. Each problem comes with the file and line, what could happen to you or your users, and the change that closes it.

claude · my-app

/launch-check

Launch score39/ 100DON'T SHIP

2 critical2 high6 medium0 low

  1. 1.

    [critical] Admin API trusts client-provided role

    app/api/admin/users/route.ts:42

    Fix: Read the role from the session on the server and refuse the request when it is not an admin.

  2. 2.

    [critical] Uploaded files are publicly readable

    supabase/migrations/0004_storage.sql:11

    Fix: Make the bucket private and hand out short-lived signed links to the file's owner.

Read the full example report · 10 problems

How it works

Three steps, start to finish.

LaunchReadyKit installs into your project and runs inside Claude Code. There is no dashboard to learn: you type a command and read the result.

  1. 1

    Buy

    Pay once. You are invited to the private repository on GitHub.

  2. 2

    Install

    One npx command, from your project folder. Nothing global.

  3. 3

    Check

    Type /launch-check in Claude Code. You get a score, a verdict and a fix list.

your-project · bash

$ npx -y github:launchreadykit/LaunchReadyKit setup

✔ LaunchReadyKit 0.3.0 installed into your-project/.claude

✔ 41 agents, 72 skills, 63 commands

› Next: restart Claude Code in this project and run /launch-check

See every step and every file it adds

Compared

LaunchReadyKit vs checking it yourself.

Both end with an app that has been checked before launch. One is a command. The other is days of reading, and a lot you would already have to know.

Finding leaked keys

Kit/check-secrets and /check-git-history

YourselfSearching every file and old commit by hand

Checking who can reach whose data

Kit/check-access, 14 checks on every route

YourselfReading each route and guessing what an attacker would try

Database rules that hold

Kit/check-supabase, /check-firebase

YourselfLearning row-level security first

Payments that cannot be cheated

Kit/launch-payments, 62 checks

YourselfTesting every webhook case yourself

Legal pages

Kit/write-privacy, /write-terms, written from your code

YourselfA template that does not match your app

SEO and link previews

Kit/launch-seo, 49 checks

YourselfA checklist from a blog post

Knowing what to fix first

KitA score, a verdict and an ordered list

YourselfA long list with no order

Fixing it

Kit/launch-fix, worst first

YourselfOne by one, hoping nothing else breaks

Proving the fix worked

KitRun the check again: fixed, new, still open

YourselfNever quite sure

Time to a first result

KitMinutes

YourselfDays

Pricing

Launch your app with fewer surprises.

The price goes up in steps as people buy. Early buyers pay the least.

Founding price

Save $40

$9$49one-time

10 of 10 seats left at this price

  • All 440 checks
  • All 41 agents and 63 commands
  • Fix and re-check commands
  • All future updates included
  • No subscription, no renewals
  • Use it on all your own projects

Pay once, keep it forever. All sales are final: refund policy.

How the price rises

  1. FoundingNow

    First 10 buyers

    $9

  2. Early

    Next 10 buyers

    $19

  3. Launch

    Next 10 buyers

    $29

  4. Regular

    Everyone after

    $49

When a step is full it closes for good. Nobody who paid more will see it reopen.

Requires Claude Code. One payment, no subscription. Tax may be added at checkout, depending on your country.

FAQ

Questions.

What does LaunchReadyKit check?

440 checks across security, database, payments, production setup, legal pages, SEO, speed, accessibility, analytics and AI features. You get a score from 0 to 100, a verdict, and a list of what to fix first, written in plain language.

Does it modify my code?

Not when it checks. A launch check only reads your project. Fixes happen only when you run the separate fix command, and you review every change it makes.

Which apps does it work with?

It is built for web apps written in JavaScript or TypeScript: Next.js, React, Vue, Nuxt, Svelte, Astro and Node servers. On other stacks the general checks still run, and the report tells you that support is partial. It installs into your project's .claude folder with one command and runs inside Claude Code, so nothing in your app has to change first.

Is my source code uploaded?

Not to us. LaunchReadyKit has no server and receives nothing. It runs inside your own Claude Code session, which handles your code the same way it does for any other task, and the reports are saved in your project.

What happens after I fix issues?

Run the check again. It shows the new score and tells you what is fixed, what is new and what is still open since the last run.

Can I get a refund?

No. LaunchReadyKit is a digital product that you get access to right away, so all sales are final, except where the law in your country requires a refund. The checks, agents, commands and an example report are all open on this site, so you can see what you get before you buy.

/launch-check

Find the problems before your users do.

Install the kit into Claude Code, type one command, and get a score and a list of what to fix. Pay once, use it on every project you own.

Get the kitSee a sample report

41 agents · 440 checks · read-only audit · one-time payment