菜单
Orchestrate the full App Store launch pipeline — ASO listing, onboarding flow, screenshots, and App Store Connect submission — in order, with resumable progress. Use when the user says "ship my app", "launch pipeline", or invokes /shipkit with no sub-command.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate high-converting App Store listing metadata (name, subtitle, keywords, and description) using proven ASO principles and keyword optimization.
Design and build a high-converting questionnaire-style onboarding flow for your app, modelled on proven conversion patterns from top subscription apps.
Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.
Automate App Store Connect submission with the asc CLI — install/auth, metadata and screenshot upload, preflight validation, release staging, review submission, and status monitoring. Use when the user asks to submit, ship, release, or publish an app to the App Store.
| name | shipkit-pipeline |
| description | Orchestrate the full App Store launch pipeline — ASO listing, onboarding flow, screenshots, and App Store Connect submission — in order, with resumable progress. Use when the user says "ship my app", "launch pipeline", or invokes /shipkit with no sub-command. |
| user-invocable | true |
You are the ShipKit launch conductor. Run the four stages in order, or the subset the user picks. Each stage is its own skill; your job is sequencing, shared state, and progress tracking.
| # | Stage | Skill | Output consumed by later stages |
|---|---|---|---|
| 1 | ASO listing | shipkit-aso (or aso-appstore-listing-skill) | metadata/<locale>/*.txt |
| 2 | Onboarding | shipkit-onboarding (or app-onboarding-questionnaire) | onboarding code in the app |
| 3 | Screenshots | shipkit-screenshots (or aso-appstore-screenshots) | screenshots/final/*.png |
| 4 | Submit | shipkit-submit (+ asc-* skills if installed) | live review submission |
Status check. Look for existing outputs (metadata/, screenshots/final/, onboarding code, .shipkit/progress.md) and any saved memory. Present a checklist of what's done and what's pending:
ShipKit pipeline status:
✅ 1. ASO listing — metadata/en-US complete
◻️ 2. Onboarding — not started
⏳ 3. Screenshots — 2 of 4 in final/
◻️ 4. Submission — blocked on screenshots
Confirm scope. Ask which stages to run (default: all pending, in order). Stage 2 (onboarding) is optional for already-shipped apps — offer to skip it.
Run each stage by invoking its skill (prefer the richer installed original if present, else the shipkit-* fallback). Complete each stage's confirmation loop with the user before advancing.
Export stage outputs. The ASO skill saves the approved listing to memory only — after stage 1, also write it to metadata/<locale>/ as name.txt, subtitle.txt, keywords.txt, promotional_text.txt, description.txt (default locale en-US) so stage 4 can upload it with asc.
Hand off context between stages — don't re-ask what a previous stage established. App context, audience, tone, benefits, and brand colour flow forward: ASO benefits inform screenshot headlines; the transformation story from onboarding informs the description; metadata + finals feed submission.
Track progress in .shipkit/progress.md after each stage (stage, status, key outputs, decisions like brand colour and confirmed benefits) so the pipeline is resumable in a fresh session even without a memory system.
Finish with a launch summary: what was produced, where it lives, submission status, and remaining manual steps (e.g. App Privacy publish, first-time IAP selection in App Store Connect).
--confirm always requires the user's explicit go-ahead in that moment.