app-store-listing
Skill1 starsChanged 36 days agoMITView on GitHub
Write and audit an App Store product page and pre-check App Review risks — app name, subtitle, keywords, description, promotional text, screenshots and previews, privacy nutrition labels, age rating, and a guideline pre-flight. Use for "write my App Store listing", "ASO", "keywords", "screenshots", "will this pass review", or before a first submission.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Innei/SKILLtheir own version, first seen Apr 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Innei/SKILL★ 92same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- ios-app-intentsSkill
- ios-crash-monitoring-sentrySkill
- ios-debugger-agentSkill
- ios-ettrace-performanceSkill
- ios-lifecycleSkill
- ios-memgraph-leaksSkill
- ios-monetizationSkill
- ios-post-launchSkill
- ios-project-setupSkill
- ios-releaseSkill
- ios-testingSkill
- swiftui-liquid-glassSkill
- swiftui-performance-auditSkill
- swiftui-ui-patternsSkill
- swiftui-view-refactorSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the app (features, onboarding, paywall), any existing listing (fastlane/metadata/ if deliver is used), and ask for: the target …
- Distinctive: line 35
If the app tracks across apps or websites, it needs App Tracking Transparency before tracking.
- Distinctive: line 40
Check the app against the guidelines that most often cause rejections, and report each one as pass / risk / fail, with the evidence:
- Very specific: line 54
When adding locales, translate keywords per locale (don't copy them), and localize the screenshot text.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
App Store Listing & Review Pre-flight
1. Gather inputs
Read the app (features, onboarding, paywall), any existing listing (fastlane/metadata/ if deliver is used), and ask for: the target audience, the top 3 competitors, primary markets/locales, and whether the app is free, paid, or freemium.
2. Metadata (respect the hard limits)
| Field | Limit | Guidance |
| App name | 30 chars | Brand + the strongest keyword if it fits naturally |
| Subtitle | 30 chars | The core benefit; don't repeat words from the name |
| Keywords | 100 bytes, comma-separated, no spaces | Singular forms, no words already in name/subtitle, no competitor trademarks |
| Promotional text | 170 chars | Changeable without a review; use it for the current offer or news |
| Description | 4,000 chars | First 3 lines carry the weight; benefits → features → social proof → subscription terms |
| What's New | 4,000 chars | See ios-release |
Count characters with code, not by eye. Output a ready-to-paste block for each field, and (if fastlane deliver is used) write the files under fastlane/metadata/<locale>/.
3. Screenshots and previews
- Plan up to 10 screenshots per device class. The first 3 matter most: each one is a single headline benefit plus the screen that proves it.
- Required sizes change. Check App Store Connect's current screenshot specifications (the largest iPhone size, plus iPad if the app runs on iPad) before rendering.
- Capture clean states in the Simulator with demo data: status bar overridden via
xcrun simctl status_bar <udid> override --time 9:41 --batteryState charged --batteryLevel 100, thenxcrun simctl io <udid> screenshot. - For automation, fastlane
snapshot+frameit, or design the frames in Figma with the Figma connector.
4. Privacy and ratings
- Build the privacy nutrition label from the code: list every SDK and what it collects, linked to identity or not, used for tracking or not. Flag any mismatch with
PrivacyInfo.xcprivacy. - If the app tracks across apps or websites, it needs App Tracking Transparency before tracking.
- Answer the age-rating questionnaire based on actual content, including user-generated content and web views.
5. Review pre-flight
Check the app against the guidelines that most often cause rejections, and report each one as pass / risk / fail, with the evidence:
- 2.1 App completeness — no crashes, placeholder text, broken links or empty states; a demo account if login is required
- 2.3 Accurate metadata — screenshots show the real app; no prices or "#1" claims in the name
- 3.1.1 / 3.1.2 In-app purchase and subscriptions — digital goods use IAP; the paywall shows price, period, what's included, and links to Terms and Privacy; Restore Purchases exists
- 4.2 Minimum functionality — more than a wrapped website
- 4.8 Login services — if third-party social login is offered, an equivalent privacy-focused option (e.g. Sign in with Apple) is offered too
- 5.1.1 Data collection — purpose strings for every permission; account deletion in-app if accounts exist; no forced sign-up for features that don't need it
- 5.1.2 Data use and sharing — tracking only with ATT consent
Guidelines get revised. When something is borderline, check the current App Review Guidelines on developer.apple.com instead of relying on memory.
6. Localization
When adding locales, translate keywords per locale (don't copy them), and localize the screenshot text. Offer to set up fastlane/metadata for each locale.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.