Claude Code 提示词：让 Opus 5.5 审查应用收款前 23

Claude Code tip: before your vibe-coded app takes its first payment, have Opus 5.5 check 𝘁𝗵𝗲𝘀𝗲 𝟮𝟯 𝘁𝗵𝗶𝗻𝗴𝘀:

> One design doc that every color, font size and spacing follows > A real screen for every state: loading, empty, error > Private keys only on the server, with your frontend files and git history searched, and anything that ever leaked replaced > Every endpoint checks login and permissions on the server, and RLS is on in the database > Spending caps or alerts on anything billed per use: AI, SMS, email > Payment webhooks verify their signature, and the same payment sent twice only counts once > Refunds, cancellations and failed charges each run once in test mode, ending in the right status > Access revoked on time when a trial or subscription ends > When payments switch from test to live, the live keys and webhook signing secret are set up again > Money stored as integers in the smallest currency unit, like Stripe does. No floats: in JS, 0.1 + 0.2 isn't 0.3 > A user double-clicking submit creates only one order > Sales tax or VAT set up for the countries you sell to > Your terms and privacy policy match what the code actually does > Daily automatic backups (Supabase's free plan has none, so upgrade to Pro or schedule your own dump), plus one test restore into a new database > Every schema migration has its reverse SQL written and has been run both ways on a copy of production data > Lists over 1,000 rows aren't silently cut off. Supabase's API returns at most 1,000 rows by default > Times stored as timestamptz, with each user's timezone in its own column, so reminders go out in their local time > Soft delete first, with RLS hiding deleted rows too. When a user deletes their account, wipe it for real > Users can export their own data > Names with apostrophes, emoji or right-to-left text don't break any input > Images in WebP or AVIF, with anything below the fold loading as you scroll > Indexes on the fields you filter by most. With a few dozen test rows everything is fast; real data is where it slows down > Error monitoring hooked up, so you're the first to know when something breaks

Send this whole list to Claude Code and add this line at the end. It checks every item and gives you a table 👇 "Split it across 5 subagents: design and speed, security, payments, data, and after launch. Check without editing anything, and for each item note pass or fail and which file the problem is in. For anything only visible in a dashboard, mark it 'needs my confirmation' and give me the steps to look. Only test backups and restores on a test database, only test payments in test mode, and don't touch production data. Show me the table first, and don't fix anything until I confirm."