cd /news/ai-tools/i-built-a-claude-code-plugin-that-au… · home topics ai-tools article
[ARTICLE · art-138977] src=dev.to ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

I Built a Claude Code Plugin That Audits Vibe-Coded Apps for Production Readiness

A developer known as Taimoorkhan1122 released prod-readiness, a read-only Claude Code plugin that performs whole-repository production-readiness audits of AI-generated "vibe-coded" apps. The plugin uses an eight-lens, multi-agent design to flag issues such as broken Supabase RLS policies, committed API keys, untested Stripe webhook handlers, frontend-only auth, and missing rate limiting, writing its findings to a .readiness-audit/ directory. It installs via the Claude Code plugin marketplace and offers a sequential mode for machines that struggle with the full multi-agent run.

by read2 min views1 publishedSep 24, 2026

Vibe coding got us shipping in hours. Then the launches started breaking.

AI coding assistants are incredible at getting a working prototype on screen. What they're terrible at is the part that comes after: the quiet, boring, unglamorous work of making sure the thing is safe to put in front of real users. I've watched the same failure patterns repeat across AI-generated apps — broken Supabase RLS policies that leak one tenant's data to another, API keys committed straight into the repo, Stripe integrations that handle the happy path and fall over on webhooks and refunds, auth that lives in the frontend while the API trusts everyone, and public endpoints with no rate limiting at all.

The prototype works. Nobody checked whether it's safe to launch. That's the gap I built prod-readiness to fill.

prod-readiness is a Claude Code plugin that runs a read-only, whole-repository production-readiness audit. It answers one question: is this app safe to launch?

It works in three stages:

It's deliberately read-only. It never touches your code — it produces the audit trail under .readiness-audit/ and tells you what's wrong and where. There's also an optional local dashboard if you want to watch the audit run in your browser.

Keyword scanners catch secrets in code. They don't catch the structural stuff that actually kills launches: missing recovery paths, unsafe trust boundaries, untested webhook handlers, operational blind spots. The eight-lens design exists because production readiness is a systems question, not a grep question. Each lens looks at the same evidence from a different angle, the way a real review team would.

You only need Claude Code installed. Three commands:

/plugin marketplace add Taimoorkhan1122/prod-readiness
/plugin install prod-readiness@prod-readiness-marketplace
/reload-plugins

Then point it at any repo and run:

/prod-readiness:production-readiness-audit

If the idea of running a full multi-agent audit makes your laptop fans spin up, there's a sequential mode too:

/prod-readiness:production-readiness-audit sequential

This is early and I'm actively improving it. If you vibe-code apps — especially ones heading toward real users and real payments — run it and tell me what it missed. The findings that matter most are the ones I haven't thought of yet.

Repo: https://github.com/Taimoorkhan1122/prod-readiness — stars and issues both welcome.

── more in #ai-tools 4 stories · sorted by recency
── more on @claude code 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/i-built-a-claude-cod…] indexed:0 read:2min 2026-09-24 ·