launch-checklist
Launch Checklist
Everything that needs to be true before real people see this.
How to use
/launch-checklistRun a pre-launch audit against these constraints.
Checklist
Copy
- All placeholder/lorem ipsum text has been replaced
- Headlines communicate value, not just describe features
- CTA button text is specific and action-oriented
- Error messages are human-readable with recovery steps
- Empty states have helpful copy and clear next actions
- Legal pages exist: Terms, Privacy Policy, at minimum
Technical
- Page loads in under 3 seconds on mobile 4G
- No console errors in production build
- Forms validate inline and preserve data on error
- All links work (no 404s, no placeholder hrefs)
- Favicon and app icons are set
- SSL certificate is active and valid
SEO and Social
- Page titles are unique and descriptive (50-60 chars)
- Meta descriptions exist for all public pages (150-160 chars)
- Open Graph tags are set (title, description, image)
- Twitter Card tags are set
- Canonical URLs are configured
- Sitemap exists and is submitted
Mobile
- All pages tested on actual mobile devices (not just responsive preview)
- Touch targets are at least 44x44px
- Forms are usable with mobile keyboards (correct input types)
- No horizontal scrolling on any viewport
- Text is readable without zooming
Analytics
- Analytics tracking is installed and firing
- Key conversion events are tracked (signup, purchase, activation)
- Error events are logged
- UTM parameters are preserved through signup flow
Post-Launch
- Monitoring/uptime alerts are configured
- Error reporting is active (Sentry or equivalent)
- Support channel exists and is reachable
- Backup and recovery process is documented and tested
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1