📋 The "Are You Actually Done?" Pre-Ship Checklist

Your flagship free resource. Post it, pin it, Feature it. This is what people will screenshot and share — and it's the most concrete expression of Build It Right, Or Don't Build It At All.

---

🏛️ ARE YOU ACTUALLY DONE? — The TOVCDI Pre-Ship Checklist

Your AI said it's finished. Here's how a developer checks. Run every box before you call it shipped. Organized by the B.U.I.L.D. Method.

✅ B — Build (does it actually work?)

• It works on a fresh load, not just after the steps you happen to remember
• It works on someone else's device/browser, not just yours
• Every button, link, and form does what it claims
• Edge cases: empty inputs, huge inputs, weird characters, double-clicks — handled, not crashed

✅ U — Understand (can you explain it?)

• You can explain, out loud, what each major file/function does
• There's no code you're afraid to touch because you don't know what it does
• You removed dead code, debug logs, and commented-out experiments

✅ I — Interface & Experience (is it actually usable?)

• It doesn't look like a default AI template — you made at least one deliberate design choice (color, type, spacing, layout)
• Responsive: it works on a phone screen, not just your wide monitor
• Loading & empty states exist (not a blank flash or frozen screen)
• Errors are human: users see a helpful message, not a raw stack trace
• ♿ Accessibility: real <button>/<a> tags (not clickable divs), images have alt text, it's usable with keyboard only, and text has enough contrast

✅ L — Lock It Down (is it safe?)

• No secrets in the code — API keys/passwords live in environment variables, not committed to the repo
• All user input is validated on the server, not just the browser
• Auth checks happen on the backend — you can't reach protected data by guessing a URL
• Your database isn't wide open (check your rules/permissions — the #1 vibe-coder leak)
• You ran a dependency audit (e.g. npm audit) and addressed the criticals
• Nothing sensitive is logged or exposed in error messages

✅ D — Document, Test & Deploy (will it survive reality?)

• A README exists: what it is, how to run it, what it needs
• It's in version control (Git) with real commit messages
• At least the critical path is tested (manually with a written list, or automated)
• You ran a Lighthouse / performance check and it's not painfully slow
• Environment variables are set in production (not hardcoded localhost values)
• You know how you'd roll back if the deploy breaks

---

🟢 Scoring

• All boxes checked? Ship it with pride. You built it right.
• A few unchecked? That's your to-do list — not a failure. Post the ones you're stuck on in the group; that's literally what we're here for.
• Most unchecked? Perfect. You just found out what to learn next. Welcome to developing.

You don't have to be done to be proud. But know the difference between "it runs" and "it's Right."

Build It Right, Or Don't Build It At All. 🏛️