← Back to libraryShip it
Pre-launch checklist
One last pass before you hit publish
The prompt
I am about to launch {{product}}. Help me do a final pre-launch check. Product: - What it is: {{one line}} - Stack: {{e.g. Next.js}} - Audience: {{who, domestic or overseas}} - Does it have: user accounts / payments / form submissions / user-generated content Give me a checklist covering: 1. Functionality: does the core path work, any broken links or placeholder copy? 2. Mobile: does it break at common screen sizes? 3. Performance: first paint, image weight, obvious jank. 4. Security: any secrets leaked to the client, is user input validated? 5. Compliance: {{ICP filing needed / privacy policy / UGC moderation}} 6. Fallbacks: what users see on error, is there a 404 page? Rules: - Split into two tiers: "cannot launch without this" and "fine to add after launch". - Filter to what applies based on my answers above. No irrelevant items. - For the China market, call out filing and individual-account restrictions separately (individual entities usually cannot do payments, UGC communities or game categories).
Replace the {{}} parts with your own content
Why it works
- Two tiers keep the list usable - a giant list gets ignored, and perfectionism delays launch forever
- Filtering by your actual answers makes the checklist fit your product instead of being generic
- Separating filing and individual-entity limits surfaces the non-technical blockers that decide whether you can launch at all
- "What users see on error" is the piece AI-built projects most often lack - without it, any exception is a white screen
What it looks like
Before launching an individually-owned WeChat mini program, AI flags: no virtual payments, no UGC community, pick the right category, and filing requires a mainland-ID admin to pass face verification.
Where it bites
- Checking only functionality and ignoring compliance - being taken down is worse than having bugs
- No fallback UI, so users hit a white screen on any error and bounce