Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

Launchworthy

A Claude Code skill that audits AI-built apps across five domains and produces a scored launch-readiness punch list with copy-paste fixes.

Wunderlandmedia · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add Wunderlandmedia/launchworthy

About this skill


name: launchworthy description: Production readiness audit that turns a demo into a real product. Built for apps shipped fast with AI coding tools (Lovable, Bolt, v0, Cursor, Claude Code). Auto-detects your stack and audits 5 domains (Frontend, Backend & Data, Auth & Security, Infrastructure, Operations), then produces a scored scorecard and a prioritized punch list with exact file paths and copy-paste fixes. Use before you go live, or on an app that is already live, when the user says "harden this", "is this production ready", "is this safe to launch", "will this survive real users", "audit my app", "turn this into a product", "production audit", "is my supabase secure", or wants to go from demo to production. argument-hint: "[path to your project root, e.g. ~/code/my-app]" license: MIT

launchworthy

A production readiness audit for apps built fast with AI. If you shipped something with Lovable, Bolt, v0, Cursor, or Claude Code and it works on your screen, this finds the gaps between "it works for me" and "real users are paying for this and nothing is on fire." It produces a scored scorecard and a prioritized punch list with specific file paths and exact fixes.

The framework is stack-agnostic. It auto-detects your framework and backend and adapts every check to what you actually use.

Who this is for

AI coding tools are great at making things that work in a demo. They are quiet about what only bites you in production: a Supabase table with row-level security turned off, an API key baked into your frontend bundle, no rate limit on the endpoint that calls a paid AI model, no backups, no idea whether a second user can read the first user's data. This audit surfaces exactly that, before a stranger finds it for you.

The 5 domains

The audit walks five domains. Each contains concrete checks with severity tags. The full check list lives in references/checklist.md.

#DomainThe question it answers
1Frontend & ExperienceWhat do users see when things go right, and when they break?
2Backend & DataDoes the engine hold up: APIs, database, jobs, and data flow?
3Auth & SecurityAre the wrong people kept out, and are the bills safe from abuse?
4Infrastructure & DeploymentCan you ship, roll back, and serve it fast and safely?
5Operations & RecoveryWill you know when it breaks, and can you survive it?

Instructions

The user must provide a path to their project root. If none is given, ask. Then run the steps below in order.

No emojis. No em dashes in output. Use severity tags: [CRITICAL], [HIGH], [MEDIUM], [LOW].

Be honest. If a check cannot be verified from code alone (does the live site leak a secret, can user A read user B's data), do not mark it passing. Mark it MANUAL CHECK NEEDED and demand evidence: the actual response, a DevTools screenshot, the query result. An audit the user self-certifies is worthless.


Step 1: Detect the Stack and Assess Scope

Read package.json (or requirements.txt, pyproject.toml, go.mod, etc.) and identify:

Framework: next (Next.js), @tanstack/react-start (TanStack Start, full-stack React on Vite), @sveltejs/kit (SvelteKit), svelte without kit (Svelte SPA on Vite), astro, @remix-run/* or React Router v7 (Remix), vite + react with none of the above (Vite React SPA, common from Lovable/Bolt/v0), express/fastify/hono (Node API), fastapi/flask/django (Python). Detection order matters: TanStack Start, SvelteKit, Astro, and many SPAs all depend on Vite, so check for the meta-framework package first before concluding it is a plain SPA. If none match, identify from the files and adapt.

Backend / data layer: @supabase/supabase-js (Supabase, RLS is the make-or-break check), firebase (Firebase, Security Rules are the make-or-break check), @prisma/client/drizzle-orm (SQL ORM), @directus/sdk/contentful/sanity/payload (headless CMS), raw pg/mysql2/mongodb (direct driver).

Host (infer, then confirm with the user): vercel.json/Next defaults (Vercel), netlify.toml (Netlify), wrangler.* (Cloudflare), Dockerfile (self-hosted container: Railway, Render, Fly, Coolify, a VPS), railway.json/render.yaml/fly.toml (that platform).

Maturity: Is there a .git dir, and how much history? Any tests, CI, error tracking already present? Is this pre-launch or already live with real users? Ask if unclear. It changes what "urgent" means.

Report: "Detected [framework] + [backend], hosted on [host]. This looks [pre-launch / already live]. Running the 5-domain production audit."


Step 2: Run the Audit

Read the full check list at references/checklist.md. For each domain, run every check that applies to the detected stack against the actual project files. Do not guess. A check that does not apply to this stack is skipped, not failed, and you say why you skipped it.

For anything you cannot verify from code, mark MANUAL CHECK NEEDED and give exact steps that produce evidence the user can paste back.


Step 3: Score Each Domain

  • PASS: all checks pass, or only [LOW] findings remain.
  • WARN: 1-2 [MEDIUM]/[HIGH] findings, nothing that causes data loss, a breach, or extended downtime.
  • FAIL: any [CRITICAL], or 3+ [HIGH] in the domain. Must be fixed before real users touch this.

Step 4: Build the Punch List

Group findings by urgency, not by domain. If the app is already live, treat "Fix Now" as "this is actively exposing you right now."

Fix Now (blockers): every [CRITICAL]; every [HIGH] in Auth & Security; anything where a real user could lose data, lose money, or read someone else's data.

Fix This Week (high priority): all remaining [HIGH]; no error tracking; no rate limit on AI/paid or auth endpoints; no connection pooling on serverless + SQL; white-screen states.

**Fix This Month (shoul

Read the complete source ↗