菜单
Use for App Store Connect work - creating the app record, filling metadata, creating subscription products, or checking review status (Stages 2, 3, and 6 of SUBMISSION.md)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating a new .NET CLI/console project from the agent-harness template ("new cli tool", "new console app", "new dotnet project"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new .NET ETL/API service from the agent-harness template ("new api", "new etl service", "new backend service"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new Expo/React Native app from the agent-harness template ("new expo app", "new mobile app", "scaffold an app with payments"). Scaffolds, stamps provenance, and verifies guardrails.
Use at session start when config-doctor reports the project is not build/deploy-ready, or when the user asks to set up the project - interviews the user, gets EAS logged in / project linked / iOS credentials provisioned and a real bundle id, offers optional payments/auth/API config, and records decisions so the session-start nudge goes quiet
Use when asked to report harness feedback, promote captured guardrail failures into issues, or check "anything worth turning into a rule?". Clusters unreported feedback events and raises digest issues on the agent-harness repo.
Use after a PR merges, or on request, to capture human review comments from a PR into the harness feedback store ("capture the review comments", "harvest PR feedback"). Routed from the merge step.
| name | asc-setup |
| description | Use for App Store Connect work - creating the app record, filling metadata, creating subscription products, or checking review status (Stages 2, 3, and 6 of SUBMISSION.md) |
Drives https://appstoreconnect.apple.com via Playwright MCP browser tools.
Before creating ANYTHING: snapshot the current page and check whether the object already exists (app record in the Apps list, subscription group on the Subscriptions page, product in the group). If it exists, verify its fields match SUBMISSION.md, record its IDs, check the box, and move on. Re-running any stage must always be safe.
On ANY unexpected page state (selector missing, unfamiliar layout, error banner): stop, snapshot, report what you saw. Never guess-click.
ios.bundleIdentifier in app.config.js — cross-check), SKU
(use the bundle id), full access.monthly_premium — must match what RevenueCat will import in Stage 4),
duration, price. Localization: display name + description. Review
screenshot (1242x2208 or device-equivalent) — ask the user to provide one
or generate from the running app.Navigate to the app's Distribution page and report the current version status (Waiting for Review / In Review / Rejected / Ready for Sale). If rejected, open Resolution Center, extract the rejection reasons verbatim, and report them.