ios-app-store-validator
Skill30 starsChanged 11 months agoMITView on GitHub
Use this skill when preparing an iOS app for App Store submission. This validates against Apple's App Store Review Guidelines to catch rejection-worthy issues early. Read the full agent prompt from agents/app-store-validator/app-store-validator.md in the ios-developer-agents repository. Follow the validation process: Provide structured findings with: - Submission Readiness status (READY / BLOCKED / NEEDS REVIEW) - Blockers (will cause rejection) - Warnings (may cause rejection) - Metadata review table - Technical configuration table - Pre-submission checklist
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ios-accessibility-validator.mdcCursor rule
- .cursor/rules/ios-app-store-validator.mdcCursor rule
- .cursor/rules/ios-security-auditor.mdcCursor rule
- ios-accessibility-validatorSkill
- ios-security-auditorSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Use this skill when preparing an iOS app for App Store submission.
- Distinctive: line 7
Before submitting to App Store Connect
- Distinctive: line 8
When preparing for TestFlight external testing
- Distinctive: line 9
After significant app updates
- Distinctive: line 10
When adding new permissions or entitlements
- Distinctive: line 11
When concerned about potential rejection
- Very specific: line 15
Read the full agent prompt from agents/app-store-validator/app-store-validator.md in the ios-developer-agents repository.
- Distinctive: line 17
Follow the validation process:
- Distinctive: line 27
In-App Purchase Validation: - If applicable
≈ “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
iOS App Store Validator
Use this skill when preparing an iOS app for App Store submission. This validates against Apple's App Store Review Guidelines to catch rejection-worthy issues early.
When to Use
- Before submitting to App Store Connect
- When preparing for TestFlight external testing
- After significant app updates
- When adding new permissions or entitlements
- When concerned about potential rejection
How to Apply
Read the full agent prompt from agents/app-store-validator/app-store-validator.md in the ios-developer-agents repository.
Follow the validation process:
- Fetch Current Guidelines - Get latest from developer.apple.com
- Technical Configuration Scan
- Info.plist validation (usage descriptions, capabilities)
- Privacy Manifest (PrivacyInfo.xcprivacy)
- Entitlements check
- Code-level issues (private APIs, deprecated frameworks)
- Metadata Validation - App name, description, screenshots, age rating
- Privacy & Legal Compliance - Privacy policy, terms, GDPR/CCPA
- In-App Purchase Validation - If applicable
Output Format
Provide structured findings with:
- Submission Readiness status (READY / BLOCKED / NEEDS REVIEW)
- Blockers (will cause rejection)
- Warnings (may cause rejection)
- Metadata review table
- Technical configuration table
- Pre-submission checklist
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.

