--- name: workflow-launch-ready description: > Launch-preparation sweep for a new app or major release. Use when "prepare for launch", "launch week", "everything before going live", "is the app launch-ready?", or "pre-launch sweep". Working tree to a PR → workflow-release-prep. license: MIT metadata: chain: "enhance-web-seo enhance-pwa audit-bundle-size audit-i18n workflow-quality-gate deploy-verify iterate-post-launch" --- # workflow-launch-ready — Full Launch Preparation **Degree of freedom: MIXED.** Skip/condition judgment `[HIGH freedom]`; sweep order and quality-gate NO-GO block `[LOW freedom — run exactly]`. The pre-launch sequence. Run once, get the complete picture across SEO, PWA, performance, quality, and post-launch monitoring. Local dirty-tree → merge-ready PR is **`workflow-release-prep`**, not this. Copy this checklist and tick items as you go: ``` - [ ] Step 1: SEO: title, description, OG, canonical, JSON-LD, sitemap - [ ] Step 2: PWA: manifest, service worker, offline; or note the skip - [ ] Step 3: Bundle size: first-load JS 200 KB gzip or less - [ ] Step 4: i18n: no hardcoded strings; skip if single locale, noted - [ ] Step 5: Quality gate: a NO-GO verdict blocks launch - [ ] Step 6: Deploy and smoke right after the production deploy - [ ] Step 7: Day-1 iteration loop scheduled; launch checklist with verdict ``` ## This skill vs neighbors | Skill | Owns | |---|---| | **workflow-launch-ready** (this) | Pre-launch sweep: SEO, PWA, bundle, i18n, gate, deploy, day-1 loop | | `workflow-quality-gate` | Pre-release gate across red-team, security, bundle, performance, unit tests | | `workflow-release-prep` | Local working tree to a merge-ready PR against main; never merge | | `deploy-verify` | Post-deploy smoke test across browser, Sentry, Supabase, Langfuse, public web | | `iterate-post-launch` | Live app feedback loop: read signals, rank issues, fix, verify, repeat | | `enhance-web-seo` | Audit and fix SEO: meta tags, structured data, sitemap, canonicals | | `enhance-pwa` | Add or upgrade PWA features: manifest, service worker, offline, install prompt | ## How to reason 1. **Scope** — new app / major release, not a dirty-tree PR 2. **Sweep** — which steps apply; which are honest skips 3. **Verdict** — LAUNCH-READY / WITH CONDITIONS / NOT READY 4. **Handoff** — day-1 loop scheduled; blockers named ## Worked example > **Scope:** first public launch of a Next.js + Supabase app; single locale; PWA wanted. > **Sweep:** SEO + PWA + bundle + quality-gate; skip i18n with a note. > **Verdict:** NOT READY — quality-gate NO-GO on missing RLS on `profiles`. > **Handoff:** fix RLS, re-run Gate 2, then `deploy-verify`; do not treat this as `workflow-release-prep`. ## Self-critique before reporting - **Not a PR-prep** — local dirty tree was not routed here - **Skips named** — PWA/i18n skipped only when inapplicable, in the table - **NO-GO blocks launch** — quality-gate NO-GO is NOT READY, not "with conditions" - **Right owner** — merge-ready PR → `workflow-release-prep`; npm package → `deploy-npm` --- ## Sweep sequence [LOW freedom — run exactly] ``` 1. SEO → enhance-web-seo (meta, OG, JSON-LD, sitemap, canonicals) 2. PWA → enhance-pwa (manifest, service worker, offline, install) 3. BUNDLE → audit-bundle-size (first-load JS ≤ 200 KB goal) 4. i18n → audit-i18n (if multi-locale: natural copy, no hardcoded strings) 5. QUALITY GATE → workflow-quality-gate (red-team + security + perf + unit tests) 6. DEPLOY → deploy-verify (post-deploy smoke after the release) 7. ITERATE → iterate-post-launch (close loop on day-1 production signals) ``` Skip steps 2 (PWA) and 4 (i18n) if not applicable — note the skip in the checklist. --- ## Step 1: SEO (read enhance-web-seo) [HIGH freedom] > Read the `enhance-web-seo` skill and follow it. Every public page needs: `