agentleFS
gygantskiyMatilyockgygantskiyMatilyock/ios-developer-agents/.claude/skills/ios-app-store-validator/SKILL.md

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

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
  1. Distinctive:

    Use this skill when preparing an iOS app for App Store submission.

    line 3
  2. Distinctive:

    Before submitting to App Store Connect

    line 7
  3. Distinctive:

    When preparing for TestFlight external testing

    line 8
  4. Distinctive:

    After significant app updates

    line 9
  5. Distinctive:

    When adding new permissions or entitlements

    line 10
  6. Distinctive:

    When concerned about potential rejection

    line 11
  7. Very specific:

    Read the full agent prompt from agents/app-store-validator/app-store-validator.md in the ios-developer-agents repository.

    line 15
  8. Distinctive:

    Follow the validation process:

    line 17
  9. Distinctive:

    In-App Purchase Validation: - If applicable

    line 27

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Fetch Current Guidelines - Get latest from developer.apple.com
  2. Technical Configuration Scan
    • Info.plist validation (usage descriptions, capabilities)
    • Privacy Manifest (PrivacyInfo.xcprivacy)
    • Entitlements check
    • Code-level issues (private APIs, deprecated frameworks)
  3. Metadata Validation - App name, description, screenshots, age rating
  4. Privacy & Legal Compliance - Privacy policy, terms, GDPR/CCPA
  5. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.