← ClaudeAtlas

website-launch-checklistlisted

Comprehensive pre-launch checklist for shipping a website to production. TRIGGER when the user says 'launch checklist', 'pre-launch', 'ready to publish', 'מוכן להשקה', or asks to prepare a website for production/public launch. Covers infrastructure, auth/security, SEO, analytics, performance, accessibility, legal, content/UX, and a final pre-publish sweep, organized in execution order.
hiyabh/claude-skills · ★ 0 · Web & Frontend · score 72
Install: claude install-skill hiyabh/claude-skills
# Website Launch Checklist ## Trigger When the user says "launch checklist", "pre-launch", "ready to publish", "מוכן להשקה", or asks to prepare a website for production/public launch. ## Overview Comprehensive checklist distilled from real-world experience launching a production Next.js site (a multi-hundred-page directory site). Covers everything from infrastructure to SEO to legal compliance. Organized in execution order — each phase must be verified before moving to the next. --- ## Phase 1: Infrastructure & Deployment ### Hosting & Domain - [ ] Domain purchased and DNS configured (A record + CNAME for www) - [ ] SSL/HTTPS working (check padlock icon) - [ ] www → non-www redirect (or vice versa) — pick one canonical URL - [ ] Environment variables set in hosting platform (Vercel/Railway/etc.) - [ ] Production database accessible from hosting (check connection string, SSL) - [ ] `.env.example` exists with all required var names (no values) ### Database - [ ] Production database provisioned (not dev/local) - [ ] Migrations applied to production - [ ] Indexes on all filtered/sorted columns - [ ] Connection pooling configured (PgBouncer for Supabase) - [ ] Direct URL configured for migrations (separate from pooled URL) ### Build & Deploy - [ ] `npm run build` passes with zero errors - [ ] `npm run lint` passes - [ ] No TypeScript errors - [ ] Auto-deploy on push to main branch working - [ ] Environment variables include all secrets (DB, auth, API keys, etc.) #### Lesso