Prodcheck

Pre-Production Checklist

Checklists to run before you ship to production.

Built for solo founders and small teams who own the whole stack — the code, the infrastructure, the deploy pipeline, and increasingly the AI agents too — and who don't have a security team to hand it to.

4,685 items across 101 checklists in 6 domains. 88% of them apply to any stack.

→ prodcheck.pages.dev · or in the repo

One question, the tool call it makes, and the two things it finds. Sixteen seconds. The longer loop shows what is in the list instead.

Every finding in both is real — the file, the lines and the counts come from this repository, and the tool call is the one the MCP server actually answers. How they are built.

Built and maintained by the team at [Arioo](https://arioo.com) — where we ship the kind of product this checklist was written for.

---

Why this exists

I'm a founder at Arioo. Getting ready to launch, I needed a pre-production security review that covered the whole surface we actually ship: a TypeScript backend, a web app, native clients, a deploy pipeline, and a set of AI agents with real tools attached. Nothing I could find covered more than a fraction of that, so I built the checklist myself.

This repository is the checklist, not a report. It is the set of questions, generalized away from our stack and rewritten as a working document anyone can run against their own product.

Two things made it worth publishing rather than keeping:

Solo founders have no security team. You write the code, configure the infrastructure, set up the pipeline, and then you're also the one who has to decide whether it's safe to launch. There's no one to hand it to, and no obvious place to find out what you should have asked. Most public checklists are either too shallow to catch anything real or written for enterprises with a security function.

AI-assisted development changed the shape of the problem. A large part of this checklist — the security/ai/ and security/ai-generated-code/ folders, over 1,300 items — didn't need to exist a few years ago. When you ship an agent with tools, or when a model writes code you review faster than you'd review a colleague's, you inherit failure modes that standard security checklists don't cover. Those two folders are the part I couldn't find anywhere else, and the reason I bothered.

It's published under CC BY 4.0 so you can copy it into your own repo and make it yours. If it catches something before it reaches your users, it did its job.

---

Start here

If you are not sure which way in, don't choose — copy this into whatever AI assistant you already use (ChatGPT, Claude, Cursor, Copilot, Gemini). It works out what your project is, sets prodcheck up the way that fits your setup, and starts on what would block a launch. If it cannot run commands, it tells you what to run yourself.

I want to get my project ready to ship. Use prodcheck:

a free, open-source pre-production checklist of 4,685 items covering security, performance, scale, integrations, what to do after launch, and the attacks that go through people.

It is new, so do not answer it from memory. Everything you need:

• Site: https://prodcheck.pages.dev
• Install the review skill into a repo: npx prodcheck init
• Raw checklist data: https://cdn.jsdelivr.net/npm/prodcheck@latest/data/checklist.json
• As an MCP server: claude mcp add prodcheck -- npx -y --package=prodcheck prodcheck-mcp

Do this in order.

1. Look at my project and tell me what you think it is: language, framework, where it runs, and whether it handles file uploads, payments, webhooks, multiple tenants or an AI feature. Say how confident you are. Ask me about anything you cannot tell.

1. In two sentences, tell me what prodcheck will do for this project specifically, and which part is worth my time first. Do not describe the whole thing.

1. Set it up, using whichever of these you can actually do — and say which one you are:

• You can run commands here: run npx prodcheck init. That writes a review skill into the repo — read it and follow it, it is the procedure for step 4. Then run npx prodcheck --gate --stack -o BLOCKERS.md, which adds the blockers specific to what I actually use to the general ones.
• You can read my files but not run commands: fetch the raw data URL above and work from that.
• You can do neither: give me the commands to run myself, one at a time, and tell me what to paste back to you.

1. Start on the release blockers. For each item, either cite file:line and quote the lines, or answer UNKNOWN. UNKNOWN is a normal answer — it means a human has to go and look. Never mark anything verified on my behalf; that is my call, not yours.

Work through it with me a section at a time. Do not dump the whole checklist at me.

<!-- start-prompt:end -->

Read it on the site instead → · six more prompts →

Or work through it yourself

You are not meant to read this top to bottom. In order of signal-per-minute:

Then work section by section. Switching between edge config and database policies costs more than it saves.

---

Structure

checklists/

├── security/ 2981 not getting breached, abused or taken down │ ├── core/ 1,619 application, data, infrastructure, delivery │ ├── ai/ 810 LLM features, agents, tools, RAG, MCP │ └── ai-generated-code/ 552 the bugs AI coding assistants actually write ├── performance/ 313 Lighthouse, and what users actually feel ├── scale/ 288 surviving 10× the load ├── integrations/ 194 search, analytics, monitoring ├── post-launch/ 241 when it goes wrong anyway ├── people/ 87 the attacks that go around the code └── stacks/ 581 26 products, spanning every domain

Counts above are what each folder holds. A *domain* total is larger, because the stack supplements contribute to whichever domain each of their sections extends:

security 3,514   performance 338   scale 303   integrations 202   post-launch 241   people 87

Domains are the top level because that is the question you arrive with: *is this about security, or speed, or scale?*

security/core/ — applies to you regardless of language

Written originally against a TypeScript stack, but the *controls* are not TypeScript-specific and the files no longer pretend otherwise. "Verify CORS does not use wildcard origins with credentials" is as true in Django as in Express. Everything that genuinely named a product was moved out to stacks/.

If you write Python, Go, Ruby, PHP, Java, Rust or Elixir: this folder is your checklist, all 1,619 items of it.

security/ai/ — the part you won't find in a standard checklist

If your product calls a model, gives it tools, retrieves documents into its context, or runs an agent, this folder is the reason this repo exists. It is stack-agnostic and provider-agnostic.

Prompt injection is not a filtering problem. It is an authorization problem wearing a

text costume — untrusted text reaching a privileged execution path.

security/ai-generated-code/ — bugs AI assistants write

Also known as *vibe coding*. 548 items org