site-launch-checklist
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, W
Security Assessment
Detected risks:
About site-launch-checklist
Site-launch-checklist is an interactive pre-launch audit and setup workflow for shipping a new website, opinionated toward a Cloudflare DNS, Vercel hosting, and PostHog stack. It orchestrates a broad range of launch concerns including analytics setup (GA4, PostHog, Google Search Console, Ahrefs), legal compliance, security headers and audits, SEO and GEO work such as robots.txt, sitemaps, llms.txt, an AI policy, schema markup and hreflang, copywriting consistency, OpenGraph and social previews, a full favicon set with manifest, and quality gates like Lighthouse, Core Web Vitals, WCAG accessibility and mobile testing, plus setting up a recurring weekly SEO agent.
The skill is deliberately conversational: it uses tappable questions aggressively rather than assuming, asking one question at a time with two to four options. A fixed set of start-of-session questions establishes the site type (doc-site, marketing/lead-gen, SaaS-app, training/paid-course, or personal-portfolio), migration situation, multilingual needs, PostHog setup, AI scraper policy, and which browser tool is available. It continues asking at every decision point, covering choices such as whether to install Sentry, BetterStack or Crisp, www versus apex canonical, which AI bots to allow, and CSP tightness. It never installs an MCP server or skill without explicit confirmation.
Work proceeds through ten ordered phases; for each phase it lists items, asks what to skip, runs verification commands, and reports pass or fail before ending with a status report that separates blockers, recommended fixes, and optional improvements. It curates a subset of six companion skill packs (for SEO/GEO, web quality, security, marketing, and developer marketing) mapped to the confirmed site type, always querying each pack's --list for current sub-skill names and installing only an agreed subset rather than whole packs. Copywriting gets two mandatory polish layers: defining a TONE.md once per site and running a humanizer pass in the site's primary language to strip AI-sounding patterns.
FAQ
What hosting and analytics stack is it opinionated for?
It is opinionated for Cloudflare DNS plus Vercel hosting plus PostHog, with a legal-compliance context. Other tools like Sentry, BetterStack, or Crisp are offered but only installed after you confirm.
What does it ask at the start of a session?
It asks six questions one at a time: site type, migration situation, multilingual needs, PostHog setup, AI scraper policy, and which browser tool is available. These answers drive later decisions and which skill packs are considered.
Will it install companion skill packs automatically?
No. It never installs any MCP server or skill without explicit confirmation, and it never installs full multi-skill packs. It queries each pack's --list, proposes a curated subset for your site type, and installs only the agreed sub-skills.
How is the launch work organized?
As ten ordered phases. For each phase it lists items, asks whether to skip any, runs a verification command, and reports pass or fail, ending with a status report grouped by phase that separates blockers, fixes, and optional improvements.
How does it handle copywriting quality?
Two mandatory layers before launch: define a TONE.md once per site (voice, forbidden patterns, reading level, good and bad examples) and run a humanizer pass in the site's primary language after every drafting step to strip AI-sounding patterns.
Install site-launch-checklist
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
samber/cc-skills