easyAppStore

What does easyAppStore do?

Take an iOS project from local development to the App Store. The Agent automatically determines the build command based on the project's actual configuration, and operates on an already logged-in App Store Connect via Easy WebBridge. This Skill follows the Agent Skills standard and can be used by Claude Code, Codex, OpenCode, WorkBuddy, and other compatible agents.

Prerequisites: Confirm it works

In the root directory of this Skill, run:

node scripts/easy-webbridge-client.mjs preflight

The self-check will confirm Node.js, Easy WebBridge, access token, and online browser, and return the available browser name and browserId. If not yet installed, follow the self-check results to complete installation of Easy WebBridge once; all subsequent Easy WebBridge business Skills share this runtime.

What it can do

• Identify Xcode, Flutter, React Native, Unity, Fastlane, and other projects, finding the correct app, Bundle ID, version number, and build number.
• Check signing and release configuration, build using the project's existing tools or find an uploadable IPA.
• Upload build packages, app icons, screenshots of all sizes, preview videos, and review attachments.
• Fill in app name, subtitle, description, keywords, category, support URL, privacy policy, and version release notes.
• Fill in age ratings, privacy information, export compliance, content rights, and review contact information.
• Fill in review account credentials, demo steps, QR codes, or test attachments as needed.
• Select the correct build version, submit to App Review, and continue checking the real review status.
• Read review feedback, determine whether to modify code, screenshots, store copy, or review materials, then complete fixes and resubmit.

Getting Started

1. Read the app project and existing release configuration, using the project's current build system.
2. Confirm the target app, version, store territory, release scope, and user's expected endpoint.
3. Based on preflight results, select the browser that is already logged into App Store Connect.
4. Create a tab group named easy-app-store-<run-id> for this submission; subsequent operations reuse the current page within the group.
5. Gather the text, images, videos, accounts, and review attachments needed for this submission; read content directly from the project when reliably available.

Execution

1. Use the project's existing Xcode, build scripts, or Fastlane to complete a Release build and upload.
2. In App Store Connect, select the correct app and version, and link the just-uploaded build.
3. Fill in the version page, store listing, privacy and compliance pages, and review information.
4. Upload required screenshots and attachments, and wait for the page to indicate processing is complete.
5. If the user asks to "submit" or "submit for review," proceed with the submission; if the user only wants to prepare or check, stop at the corresponding result page.
6. After submission, re-read the page and record the actual displayed version, build number, and status.
7. If rejected, read the full review feedback, identify the issue, modify the corresponding content, and restart the process.

How to use Easy WebBridge

• Easy WebBridge address is fixed at 127.0.0.1:17777.
• A single task controls one browserId.
• Sequential steps reuse the same tab; only add a new tab within the same task group when comparison is truly needed.
• Use this Skill's scripts/easy-webbridge-client.mjs to call list, navigate, snapshot, click, fill, upload, and command; it connects directly to the running Easy WebBridge, independent of another Skill's local path.
• Use upload to upload absolute file paths; re-read the page after any change before continuing.
• At task end, only close the tab group created by this Skill; preserve the user's original pages.

Completion Criteria

Clearly provide the user with:

• App name, Bundle ID, version number, and build number.
• IPA generation or upload result.
• Completion status of store listing, screenshots, privacy compliance, and review materials.
• Current actual status in App Store Connect, such as "Prepare for Submission," "Waiting for Review," "In Review," "Rejected," or "Ready for Sale."
• If there are review issues, provide specific reasons, what was modified, and next steps.

Record "Upload Successful," "Submission Successful," "Review Approved," and "Visible on Store" separately, based on the final App Store Connect page.