What should I check before I launch my project?
Use the launch checklist from Check it before you launch. Give it to Claude with the files or preview it may inspect. It reviews security, privacy, legal exposure and the public site, then gives you a short next list.
Read the lesson and get the files first
Run a launch review of my project using the launch-checklist.txt I supplied. If you can't read it, ask me for it before starting. Ask which local files and preview or public addresses are in scope. Review only; don't change files, publish, spend money, send messages or test other people's systems. Use fake data and ask before tests that change data or could disrupt a service. Report every ID: A1-A20, B1-B20, C1-C10 and D1-D18. For each, give OK, GAP, Not applicable or Not checked, with evidence or a reason. Separate what you saw from what you inferred. Don't print secrets. Check current official sources for legal claims and ask where the business and its users are. Finish with the three things to address first and what remains untested. Don't call the project secure or legally compliant.
What to expect
All 68 IDs, each with OK, GAP, Not applicable or Not checked. Missing access stays Not checked. Read the evidence; the report is not a security or legal certificate.