site-launch-checklist

Featured

Pre-launch checklist for shipping a new website. Orchestrates analytics setup (GA4, PostHog, Google Search Console, Ahrefs), legal compliance, security headers and audit, SEO and GEO with keyword research validated against Google Trends (robots.txt, sitemaps, llms.txt, AI policy, schema markup, hreflang), copywriting consistency via a TONE.md and a humanizer pass in the matching language, OpenGraph and social previews, full favicon set with manifest, quality gates (Lighthouse, Core Web Vitals, WCAG accessibility, mobile testing), and setup of a weekly SEO agent. Use this skill whenever the user mentions launching a site/app, deploying a domain to production, pre-launch audit, shipping a marketing/docs/SaaS site or lead magnet, or says "checklist for the site", "ready to ship", "before I go live", "audit before launch", "ready for prod", or asks for a site review.

AI & Automation 188 stars 14 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Site Launch Checklist Pre-launch audit and setup workflow for shipping a new website. Opinionated for Cloudflare DNS + Vercel hosting + PostHog + Legal context. ## Interaction style (READ FIRST) This skill is intentionally interactive. **Use `ask_user_input_v0` aggressively** instead of assuming. Ask one question at a time with 2-4 tappable options. The user will tap, not type. **Always ask these questions at the start of a run** (one at a time, in this order): 1. Site type: `doc-site` | `marketing/lead-gen` | `SaaS-app` | `training/paid-course` | `personal-portfolio` 2. Migration: `greenfield-new-domain` | `migration-need-301-redirects` | `replacing-existing-on-same-domain` 3. Multilingual: `single-locale` | `en` | `fr+en` | `other-multi` 4. PostHog setup: `hogpost.samber.dev` | `set-up-new-proxy` | `skip-PostHog` 5. AI scraper policy: `use-default-for-site-type` | `customize-per-bot` | `block-all` 6. Browser tool available: `claude-chrome-extension` | `playwright` | `neither-skip-browser-checks` **Ask again at every decision point throughout the phases**, including: - Whether to install Sentry / BetterStack / Crisp (depends on site type, ask explicitly) - www vs apex canonical preference (most sites: apex; ask anyway) - Which AI bots to allow if user chose `customize-per-bot` - CSP tightness level: `strict-default-src-none` | `balanced-allow-self` | `permissive-for-marketing` - Whether to skip a phase entirely (e.g., skip Phase 3 if non-FR site) Never proceed past...

Details

Author
samber
Repository
samber/cc-skills
Created
5 months ago
Last Updated
yesterday
Language
CSS
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

product-launch-checklist

Runs a one-time go/no-go readiness check before a product or campaign launch, covering stock, page, tracking, lifecycle flows, support, and margin as a checklist the launch owner signs off against. Use when a launch, restock, or spend increase is about to go live and the cost of finding a gap after the fact is high. Boundary: `marketing-automation` designs ongoing marketing and sales automation that runs indefinitely; this skill is a single pre-launch checklist for one specific launch date, not an automation build.

0 Updated today
sidchaudhary
Code & Development Listed

full-stack-audit

Comprehensive website and web app audit covering security, UX, performance, accessibility, SEO, compliance, and revenue protection. Use this skill whenever the user asks to audit, review, check, or score a website or web application. Also use when the user says 'full-stack audit', 'UX audit', 'security audit', 'launch checklist', 'is my site ready to launch', 'check my site', 'review my code for issues', 'what did I miss', or any variation of wanting a comprehensive quality review before or after launch. This skill catches the issues that AI-built and vibe-coded sites consistently get wrong: client-side paywalls, exposed database tables, missing security headers, broken mobile layouts, and trust gaps that kill conversion. Triggers even if the user only asks about one area (e.g., 'check my security') because problems compound across categories.

0 Updated yesterday
osbertunawakened431
Web & Frontend Listed

web-qa

Runs a professional, meticulous end-to-end QA pass on a website before it ships, and re-verifies it after it goes live. Covers functionality, links, forms, responsive/cross-browser, accessibility (WCAG 2.2 AA), performance/Core Web Vitals, content and copy proofing, SEO and social metadata, analytics, security/privacy, deploy/DNS, and post-launch monitoring. Includes an automated scanner and a severity-graded punch list. Use when someone says "QA this site," "final check before launch," "pre-launch checklist," "is this ready to ship," "review my site before I deploy," "punch list," "why does this look broken," or after a deploy to confirm nothing regressed.

0 Updated today
brittanyslay