ワンクリックでManusで任意のスキルを実行

workflow-launch-ready

Full launch preparation sweep for a new app or major release. One entry point that sequences enhance-web-seo, enhance-pwa, audit-bundle-size, audit-i18n, workflow-quality-gate, deploy-verify, and iterate-post-launch. Produces a launch checklist with all open items and a launch-readiness verdict. Use when "prepare for launch", "launch week", "everything before going live", "is the app launch-ready?", "pre-launch sweep", or "ship it to the world".

Manusで実行

スター4

フォーク0

更新日2026年6月12日 00:41

ソース

kensaurus

kensaurus/cursor-kenji

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

SKILL.md

readonly

name	workflow-launch-ready
description	Full launch preparation sweep for a new app or major release. One entry point that sequences enhance-web-seo, enhance-pwa, audit-bundle-size, audit-i18n, workflow-quality-gate, deploy-verify, and iterate-post-launch. Produces a launch checklist with all open items and a launch-readiness verdict. Use when "prepare for launch", "launch week", "everything before going live", "is the app launch-ready?", "pre-launch sweep", or "ship it to the world".
license	MIT

workflow-launch-ready — Full Launch Preparation

The pre-launch sequence. Run once, get the complete picture across SEO, PWA, performance, quality, and post-launch monitoring.

Sweep sequence

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)

Read ~/.cursor/skills/enhance-web-seo/SKILL.md and follow it.

Every public page needs: <title>, meta description, OG tags, canonical URL, structured data (JSON-LD), and a sitemap entry.

Step 2: PWA (read enhance-pwa)

Read ~/.cursor/skills/enhance-pwa/SKILL.md and follow it.

Required: Web App Manifest + service worker with offline fallback. Lighthouse PWA score ≥ 90 before launch.

Step 3: Bundle size (read audit-bundle-size)

Read ~/.cursor/skills/audit-bundle-size/SKILL.md and follow it.

Target: first-load JS ≤ 200 KB gzip. All routes lazy-loaded.

Step 4: i18n (read audit-i18n — skip if single locale)

Read ~/.cursor/skills/audit-i18n/SKILL.md and follow it.

Priority: no hardcoded user-facing strings, natural copy in all supported locales, correct date/number/currency formatting.

Step 5: Quality gate (read workflow-quality-gate)

Read ~/.cursor/skills/workflow-quality-gate/SKILL.md and follow it.

This step runs test-red-team, audit-security, audit-performance, and test-unit internally. A NO-GO verdict from this step blocks launch.

Step 6: Deploy & smoke (read deploy-verify)

Read ~/.cursor/skills/deploy-verify/SKILL.md and follow it.

Run immediately after the production deploy. Confirm no new Sentry errors, schema is healthy, and critical flows work.

Step 7: Day-1 iteration loop (read iterate-post-launch)

Read ~/.cursor/skills/iterate-post-launch/SKILL.md and follow it.

Schedule this 24–48 hours after launch. Pull first real-user signals and prioritize the first fix pass.

Launch checklist output

## Launch Readiness — [App] — [Date]

### Verdict: LAUNCH-READY / LAUNCH WITH CONDITIONS / NOT READY

| Step | Status | Open items |
|------|--------|------------|
| SEO | ✅ / ⚠️ / ❌ | [list] |
| PWA | ✅ / ⚠️ / ❌ / skipped | [list] |
| Bundle size | ✅ / ⚠️ / ❌ | [X KB] |
| i18n | ✅ / ⚠️ / skipped | [list] |
| Quality gate | GO / NO-GO / CONDITIONAL | [see gate report] |
| Deploy smoke | ✅ / ❌ | [notes] |
| Day-1 plan | scheduled / not yet | [date] |

### Blockers (must fix before launch)
[list]

### Post-launch backlog (fix within 48 h)
[list]

このリポジトリの他の Skills

同じリポジトリ

test-red-team

kensaurus/cursor-kenji

Adversarial red-team of a running web, React Native, or Capacitor hybrid app. Drives Playwright browser MCP (web/PWA), Playwright Android WebView attach (Capacitor), or adb tap-walk (native chrome) against a feature-first coverage matrix: each feature decomposed to surfaces, sub-pages, components, and states, attacked across 4 dimensions — UI/UX, data pipeline, security (OWASP-mapped), and performance. Cross-references Sentry for production telemetry, Supabase for DB-layer mutation truth and RLS verification, and Firecrawl for current OWASP/MASVS guidance. Produces a severity-ranked defect list with repro steps and evidence. Generic across any repo and stack. Use when asked to "red team this app", "attack my app", "break it", "find all the defects", "adversarial test", "pre-launch hardening", "pentest the app", or "full app QA". Distinct from test-playwright (session PDCA), test-qa (happy-path crawl), and audit-security (static code review).

2026-06-124

workflow-build-feature

kensaurus/cursor-kenji

End-to-end feature build workflow: spec → TDD → implement → smoke test → PR. Sequences workflow-spec-tdd, test-unit, test-playwright, and workflow-pr into a single tracked loop. The single entry point for "build a feature", "implement this", "add X", "ship a new capability", or any non-trivial feature request. Asks for scope clarification before starting if the request is ambiguous. Generic across web, mobile, and full-stack repos.

2026-06-124

workflow-fix-and-ship

kensaurus/cursor-kenji

Complete bug-fix lifecycle in one sweep: triage production signals (Sentry / logs) → reproduce → fix (debug-error) → verify full-stack (test-playwright) → PR (workflow-pr) → post-deploy smoke (deploy-verify). Use when "fix this bug and close the ticket", "patch this and ship", "fix this Sentry issue", "bug report from user", or when a production error needs to go from alert to resolved in a single session.

2026-06-124

workflow-onboard

kensaurus/cursor-kenji

First-contact orientation for an unfamiliar codebase. Reads package manifests, entry points, routing, data layer, auth, environment variables, and recent git history. Produces a concise briefing: what the app does, how it's structured, how to run it locally, and the top areas to understand first. Generic across web, mobile, and full-stack repos. Use when "I'm new to this repo", "orient me", "explain this codebase", "what does this do?", "onboard me", "first day on this project", or "catch me up on the codebase".

2026-06-124

workflow-quality-gate

kensaurus/cursor-kenji

Pre-release quality gate that sequences test-red-team, audit-security, audit-bundle-size, audit-performance, and test-unit into a single sweep. Produces a go/no-go verdict with a ranked defect list. Use when "is this ready to ship?", "quality gate", "pre-release checklist", "what do I need to fix before launch?", "ship-readiness check", or before any production release.

2026-06-124

audit-bundle-size

kensaurus/cursor-kenji

Analyse and shrink JavaScript bundle size for any web app. Auto-detects bundler (Vite, Webpack, Rollup, esbuild, Next.js, Turbopack). Runs a production build with bundle analysis, identifies the largest chunks, duplicate dependencies, non-tree-shakeable imports, and missing code-splitting or lazy-load boundaries. Researches current best practices via Firecrawl and Context7. Maps every finding to a specific file and import with before/after size estimates. Generic across any framework. Use when asked to "reduce bundle size", "analyse bundle", "tree shaking", "lazy loading", "code splitting", "slow initial load", "large JS", "chunk size", "build performance", "LCP caused by JS", "why is the bundle so big", or "first load JS too large".

2026-06-124

name	workflow-launch-ready
description	Full launch preparation sweep for a new app or major release. One entry point that sequences enhance-web-seo, enhance-pwa, audit-bundle-size, audit-i18n, workflow-quality-gate, deploy-verify, and iterate-post-launch. Produces a launch checklist with all open items and a launch-readiness verdict. Use when "prepare for launch", "launch week", "everything before going live", "is the app launch-ready?", "pre-launch sweep", or "ship it to the world".
license	MIT

workflow-launch-ready — Full Launch Preparation

The pre-launch sequence. Run once, get the complete picture across SEO, PWA, performance, quality, and post-launch monitoring.

Sweep sequence

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)

Read ~/.cursor/skills/enhance-web-seo/SKILL.md and follow it.

Every public page needs: <title>, meta description, OG tags, canonical URL, structured data (JSON-LD), and a sitemap entry.

Step 2: PWA (read enhance-pwa)

Read ~/.cursor/skills/enhance-pwa/SKILL.md and follow it.

Required: Web App Manifest + service worker with offline fallback. Lighthouse PWA score ≥ 90 before launch.

Step 3: Bundle size (read audit-bundle-size)

Read ~/.cursor/skills/audit-bundle-size/SKILL.md and follow it.

Target: first-load JS ≤ 200 KB gzip. All routes lazy-loaded.

Step 4: i18n (read audit-i18n — skip if single locale)

Read ~/.cursor/skills/audit-i18n/SKILL.md and follow it.

Priority: no hardcoded user-facing strings, natural copy in all supported locales, correct date/number/currency formatting.

Step 5: Quality gate (read workflow-quality-gate)

Read ~/.cursor/skills/workflow-quality-gate/SKILL.md and follow it.

This step runs test-red-team, audit-security, audit-performance, and test-unit internally. A NO-GO verdict from this step blocks launch.

Step 6: Deploy & smoke (read deploy-verify)

Read ~/.cursor/skills/deploy-verify/SKILL.md and follow it.

Run immediately after the production deploy. Confirm no new Sentry errors, schema is healthy, and critical flows work.

Step 7: Day-1 iteration loop (read iterate-post-launch)

Read ~/.cursor/skills/iterate-post-launch/SKILL.md and follow it.

Schedule this 24–48 hours after launch. Pull first real-user signals and prioritize the first fix pass.

Launch checklist output

## Launch Readiness — [App] — [Date]

### Verdict: LAUNCH-READY / LAUNCH WITH CONDITIONS / NOT READY

| Step | Status | Open items |
|------|--------|------------|
| SEO | ✅ / ⚠️ / ❌ | [list] |
| PWA | ✅ / ⚠️ / ❌ / skipped | [list] |
| Bundle size | ✅ / ⚠️ / ❌ | [X KB] |
| i18n | ✅ / ⚠️ / skipped | [list] |
| Quality gate | GO / NO-GO / CONDITIONAL | [see gate report] |
| Deploy smoke | ✅ / ❌ | [notes] |
| Day-1 plan | scheduled / not yet | [date] |

### Blockers (must fix before launch)
[list]

### Post-launch backlog (fix within 48 h)
[list]