heymegabyte/agent-skills / 08-deploy-and-runtime-verification
deploy-and-runtime-verification
UnverifiedMANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.6 KB |
| backup-and-disaster-recovery.md | markdown | 2.7 KB |
| changelog-and-releases.md | markdown | 5.3 KB |
| ci-cd-pipeline.md | markdown | 7.1 KB |
| critical-css.md | markdown | 4.7 KB |
| font-subsetting.md | markdown | 4.5 KB |
| gh-fix-ci.md | markdown | 3.5 KB |
| launch-day-sequence.md | markdown | 5.2 KB |
| pipeline-health-check.md | markdown | 4.5 KB |
| r2-lifecycle.md | markdown | 5.6 KB |
| service-worker.md | markdown | 9.7 KB |
| uptime-and-health.md | markdown | 6.5 KB |
launch-day-sequence.md
View on GitHub---
name: "Launch Day Sequence"
version: "1.1.0"
updated: "2026-04-23"
description: "Go-live checklist: sitemap → GSC, robots.txt unblock, Postiz social, Resend launch email, full quality gate, uptime monitoring setup. Nothing forgotten."
---
# Launch Day Sequence
## Pre-Launch Verification
- [ ] All pages return 200
- [ ] All forms submit correctly (8-point test matrix — 06/contact-forms-and-endpoints)
- [ ] All images load (no broken images)
- [ ] No placeholder content (Lorem, TODO, coming soon)
- [ ] Mobile responsive at 375px
- [ ] Desktop looks good at 1280px
- [ ] Accessibility — axe-core 0 violations (07/accessibility-gate)
- [ ] SEO — Yoast checklist passes on all pages (09/seo-and-keywords)
- [ ] Performance — Lighthouse report generated
- [ ] Security — CSP headers, Turnstile on forms
- [ ] Legal — privacy policy + terms present
- [ ] Easter egg — at least one hidden delight (06/easter-eggs)
- [ ] Error pages — branded 404 + 500 (06/custom-error-pages)
- [ ] Contact form — working and tested (06/contact-forms-and-endpoints)
- [ ] Web property completeness (06/web-manifest-system):
- `site.webmanifest` validates in Chrome DevTools (0 warnings)
- PWA screenshots taken with Playwright (wide + narrow `form_factor`)
- 4+ JSON-LD blocks per page (Organization, WebSite + SearchAction, WebPage, domain-specific)
- OG images at 1200×630, visually verified on Twitter Card Validator + Facebook Debugger
- Infrastructure files — `humans.txt`, `security.txt`, `browserconfig.xml`, `opensearch.xml`
- Cross-site alternate links present
- Sitemap submitted to Google Search Console
## Launch Sequence (Automated)
### Step 1: Final Deploy + Purge
```bash
npx wrangler deploy
curl -s -X POST "https://api.cloudflare.com/client/v4/zones/$CF_ZONE_ID/purge_cache" \
-H "Authorization: Bearer $CF_API_TOKEN" --data '{"purge_everything":true}'
sleep 5
```
### Step 2: Ensure Search Engines Can Crawl
```bash
# Verify robots.txt allows crawling
curl -s "https://domain.com/robots.txt" | grep "Allow: /"
# Verify sitemap exists and is valid XML
curl -s "https://domain.com/sitemap.xml" | head -5
```
### Step 3: Submit Sitemap to Google Search Console
```bash
# Via GSC API (GCP service account required)
curl -X PUT "https://www.googleapis.com/webmasters/v3/sites/https%3A%2F%2Fdomain.com/sitemaps/https%3A%2F%2Fdomain.com%2Fsitemap.xml" \
-H "Authorization: Bearer $GSC_TOKEN"
# Or via ping (no auth needed)
curl "https://www.google.com/ping?sitemap=https://domain.com/sitemap.xml"
```
### Step 4: GitHub Auto-Config
```bash
gh repo edit --description "$(curl -s https://domain.com | grep -oP '(?<=<meta name="description" content=")[^"]*')"
gh repo edit --homepage "https://domain.com"
gh repo edit --add-topic "cloudflare,hono,emdash,typescript"
```
### Step 5: Generate README (09/documentation-and-codebase-hygiene)
Auto-generate branded README with install.doctor template, aqua dividers, badges.
### Step 6: Social Announcement (09/social-automation)
```bash
# Auto-post via Postiz
curl -X POST "https://postiz.megabyte.space/api/posts" \
-H "Authorization: Bearer $POSTIZ_API_KEY" \
-d '{
"content": "Just shipped: domain.com — [product description]",
"platforms": ["twitter", "linkedin"],
"media": ["https://domain.com/og/homepage.png"],
"schedule": "now"
}'
```
### Step 7: Launch Email (09/email-templates)
Send branded launch announcement via Resend to newsletter subscribers (if Listmonk is set up).
### Step 8: Production E2E Suite
```bash
PROD_URL=https://domain.com npx playwright test
```
### Step 9: Cross-Browser Smoke (first deploy only)
```bash
npx playwright test --project=chromium --project=firefox --project=webkit
```
### Step 10: Final Report
```markdown
## Launch Report — domain.com
### Status: ✅ LIVE
- URL: https://domain.com
- Deploy: [timestamp]
- Lighthouse: [score]
- E2E: [pass/fail]
- Sitemap: submitted to GSC
- Social: posted to [platforms]
- README: generated
### What Was Built
- [feature list]
### Next Steps
- [improvements from idea engine — 14-independent-idea-engine]
```
### Step 11: Notify Connected Services
```typescript
// Slack deploy notification
await notifySlack(env, `🚀 *${domain}* is LIVE\n<https://${domain}|Visit site>\nBuilt with projectsites.dev`);
// Discord community notification (if applicable)
await notifyDiscord(env, `${domain} launched!`, `Check it out: https://${domain}`);
// Zapier webhook (triggers any connected automations)
await triggerZapier(env, 'site_launched', { domain, url: `https://${domain}` });
```
### Step 12: Psychology-Optimized Launch (04/wisdom-and-human-psychology)
- **Peak-End Rule** — the launch announcement IS the peak moment. Make it count.
- **Social Proof** — include user count or testimonial in the social post
- **Reciprocity** — share something valuable in the announcement (tip, insight, free tool)
- **Unity** — frame as "we built this" not "I built this" — shared identity with community
### Brand Amplification
Every launch amplifies the projectsites.dev brand:
- Social posts mention "Built with projectsites.dev" when appropriate
- README includes projectsites.dev badge
- Footer includes projectsites.dev attribution
- The quality of the launch IS the marketing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |