Free starter
One check instruction
Use the builder below to create a useful prompt for the project you have open now.
- Plain-English setup
- Copy or download the prompt
- A good way to try the method
01 Production safety for vibe coders
Built for vibe coders who can make an app but are not sure it is safe to launch. Ship Doctor gives your coding assistant a thorough safety-check instruction, then it examines the real project and tells you what could break, leak data or cost you money.
Choose your level
Free starter
Use the builder below to create a useful prompt for the project you have open now.
KHDS Ship Doctor Toolkit
A reusable Codex skill that performs the full evidence-led workflow—not just a single prompt.
Secure Stripe checkout. Instant ZIP download after payment. Your Codex usage is separate.
See the evidence first
We ran the method against Ship Doctor’s own payment and delivery path. See the score, verified evidence, limitations and exact launch conditions—without buying anything.
Read the sample report →Exactly what downloads
SKILL.mdThe reusable Codex examinerdiagnostics.md14-area inspection playbookkhds-business-checks.mdMoney, data and operational risksreporting.mdEvidence, scoring and report templatesopenai.yamlCodex skill configurationREADME.mdPlain-English installation guideFree versus paid
Start here
What you need
Your project open in Codex or a link to its code.A live website link helps too, but is not essential.What you get
A verdict, score and plain-English fix list.The detailed evidence is saved in your project.What you pay here
£0 for this starter prompt.The reusable full toolkit is £49. Your own Codex plan may use credits.Your instructions are ready
Your free prompt is ready
Install it once, run all four modes, and use the full diagnostic playbook on this project and future projects.
The examination
Ship Doctor follows behaviour through the real system, then reconciles claims against what is reachable, enforced, tested and observable.
Establish the canonical source, runtime, providers and production dependencies.
Map the user and business paths whose failure would matter most.
Test whether capabilities are real, wired, enforced and visible when they fail.
Turn concrete evidence into a scored release verdict and ordered treatment plan.
Plain-English answers
A production-readiness toolkit that tells your coding assistant how to inspect your real project, find launch risks and give you a clear ship or do-not-ship verdict.
Vibe coders, non-technical founders, solo builders, freelancers and AI-assisted developers who can make an app but are not sure whether it is safe to launch.
Authentication, secrets, data, payments, AI usage and costs, automations, integrations, deployment, testing and monitoring—the areas most likely to hurt users or your business.
The free builder creates one starter check prompt. The £49 toolkit is the complete reusable Codex skill, with four modes, a 14-area playbook, evidence templates, scoring and fix workflows. It is one payment, not a subscription.
No. This page does not upload your code. The prompt or toolkit runs inside the coding workspace where your project is already open.
Verdict language
An unresolved critical risk or unsafe core path exists.
Risk is bounded, but named conditions must be met.
Critical paths are meaningfully verified with no blockers.