app-store-submission-wasp-drone — Claude Code subagent
The app-store-submission-wasp-drone subagent prepares iOS and Android apps for store release. Use it for ASO, privacy checks, rejection analysis, TestFlight, and IAP setup.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install backend-and-desktop-tools@wasp-nestWhat app-store-submission-wasp-drone does
The subagent covers the release workflow for iOS through App Store Connect and TestFlight, plus Android through Google Play Console. It reviews store metadata, screenshots, preview assets, privacy declarations, age-rating forms, and the evidence needed for a submission-readiness report.
When a review rejection is unclear, it separates possible readings of the message and drafts a remediation path for each one. It also handles StoreKit 2 and Google Play IAP setup at the publication level, including product, base-plan, and offer configuration. It does not write client-side StoreKit or Play Billing code, so that work still needs a qualified native owner.
The workflow includes TestFlight checks, expedited-review assessment, platform-specific timeline ranges, and Android policy changes dated April 2026. The subagent runs with Claude Code or Codex; its Claude Code installation uses backend-and-desktop-tools@wasp-nest.
What it helps with
- prepare an app for App Store Connect submission
- audit Apple and Google privacy declarations
- draft store metadata and screenshot requirements
- diagnose an App Store or Google Play rejection
- review IAP setup before a store release
Example prompts for the agent
- Prepare my iOS app for App Store Connect and produce a submission-readiness report.
- Analyze this Google Play rejection, give two possible readings, and draft a fix plan for each.
- Review the Android privacy forms, ASO metadata, and IAP setup before release.
How to install app-store-submission-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install backend-and-desktop-tools@wasp-nest2Manually: put the files in place
.claude/agents/app-store-submission-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/app-store-submission-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/app-store-submission-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about app-store-submission-wasp-drone
How do I install app-store-submission-wasp-drone in Claude Code?
Run these steps in order: /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install backend-and-desktop-tools@wasp-nest, then add .claude/agents/app-store-submission-wasp-drone.md.
What does app-store-submission-wasp-drone do?
It guides mobile app release work for App Store Connect, TestFlight, and Google Play Console. Its scope includes ASO, privacy declarations, age ratings, IAP setup, rejection analysis, and release readiness.
Does the subagent implement StoreKit or Play Billing?
No. It reviews IAP and store configuration, while client-side StoreKit and Play Billing implementation remains outside its scope.