Skip to main content
skill CX Codex

app-store-submission-stinger — Claude Code skill for App Store and Google Play submission

app-store-submission-stinger guides an app through App Store and Google Play submission: ASO, privacy forms, rejection fixes. Use it before the first release or after a rejected build.

AGPL-3.0-or-later ★ 96 updated 2026-10-18

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install backend-and-desktop-tools@wasp-nest
Open on GitHub

What app-store-submission-stinger does

The skill maps the submission path into five stages. ASO covers 30-character titles, the 100-character iOS keyword field with no spaces after commas, and screenshots sized to current App Store Connect rules. Separate guides handle compliance, the submission itself, rejection analysis, and purchase setup.

Inside there are guides, a worksheet for evidence, and synthetic readiness cases. The activation checklist asks five questions: platform, stage, monetization model, special categories, and whether a rejection is in hand. If the app targets children, the skill switches to strict COPPA/GDPR-K handling and flags it in every report.

For iOS, the critical pieces are PrivacyInfo.xcprivacy for SDKs using required-reason APIs, the privacy nutrition label, and an honest age rating. Android needs the Data Safety form plus the April 2026 policy shifts: Contact Picker, Location Button, no geofencing in foreground services. The deadline for those is October 28, 2026.

On rejection, the skill's first move is not a resubmit. It classifies the note as policy, metadata, binary, or legal. Terse Apple wording gets two interpretations and two fix paths. Purchases go through StoreKit 2, with the transaction listener started at app entry and every transaction finished after granting access.

What it helps with

  • fit metadata into App Store and Google Play limits
  • fill PrivacyInfo.xcprivacy and the Data Safety form
  • classify a rejection and pick a remediation path
  • avoid common StoreKit 2 transaction mistakes
  • check Google Play 2026 policy compliance

Example prompts for the agent

  • Prepare my app for first submission to both stores, subscription monetization
  • Analyze this App Store rejection and give me two fix plans
  • Build a compliance checklist for an Android app using precise location

How to install app-store-submission-stinger

1Plugin marketplace

/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install backend-and-desktop-tools@wasp-nest

This installs the whole backend-and-desktop-tools plugin with all its skills

2Skills CLI (Vercel)

npx skills add legioncodeinc/vibe-coding-tools --skill app-store-submission-stinger -a claude-code

3Manually: put the files in place

~/.claude/skills/app-store-submission-stinger/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/app-store-submission-stinger/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about app-store-submission-stinger

How do I install app-store-submission-stinger in Claude Code?

Add the marketplace first: /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the package: /plugin install backend-and-desktop-tools@wasp-nest. You can also run npx skills add legioncodeinc/vibe-coding-tools --skill app-store-submission-stinger -a claude-code, which places the skill at ~/.claude/skills/app-store-submission-stinger/SKILL.md.

What does app-store-submission-stinger do?

It walks through five submission stages: ASO, compliance, the actual submit, rejection remediation, and IAP setup. Each stage has a dedicated guide with checklists.

What Android policy changes does the skill account for?

The April 2026 Google Play policy updates with a deadline of October 28, 2026: Android Contact Picker replaces Contacts permissions, Android Location Button for precise location, and geofencing is no longer approved for foreground services.

Similar skills

All skills for Mobile →

From the same set172

The whole set →
auth-wasp-drone auth-wasp-drone — an authentication implementation subagent for provider choice, OAuth wiring, MFA, RBAC, session handling, and B2B SSO. CX Codex ★ 96repo stars status-page-wasp-drone status-page-wasp-drone is a Claude Code subagent for choosing a status platform, designing components, writing incident messages, and configuring subscriber notifications. CX Codex ★ 96repo stars natural-photography-stinger natural-photography-stinger is a Claude Code skill that generates and retouches realistic photos with consented models and strict EXIF rules. CX Codex +1 ★ 96repo stars discovery-research-stinger discovery-research-stinger is a Claude Code skill that shapes discovery before development by examining assumptions and defining a first version. CX Codex +1 ★ 96repo stars agile-scrum-wasp-drone agile-scrum-wasp-drone — a subagent for auditing team workflows against the 2020 Scrum Guide, diagnosing process anti-patterns, and writing Definition of Done templates. CX Codex ★ 96repo stars remove-unused-dependencies remove-unused-dependencies audits selected dependencies inside an approved package and lockfile scope, then checks imports, tests, builds, and packaging before removal. CX Codex +1 ★ 96repo stars harness-integration-stinger harness-integration-stinger — a skill for Claude Code and Codex that explains how to wire a single capability—skill, agent, hook, or MCP server—across four platforms: Claude Code, Cursor, Codex, and Cowork. CX Codex +1 ★ 96repo stars font-loading-wasp-drone font-loading-wasp-drone audits font loading pipelines, eliminates CLS shifts from font swaps, and configures Next.js font delivery. CX Codex ★ 96repo stars

Project sponsors

Companies that keep this analytics open