gygantskiyMatilyockgygantskiyMatilyock/ios-developer-agents/.cursor/rules/ios-app-store-validator.mdc

ios-developer-agents / rules

Cursor rule30 starsChanged 11 months agoMITView on GitHub

App Store validation for iOS projects

Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ios-accessibility-validator.mdcCursor rule
- .cursor/rules/ios-security-auditor.mdcCursor rule
- ios-accessibility-validatorSkill
- ios-app-store-validatorSkill
- ios-security-auditorSkill

The file

We split this ios-app-store-validator.mdc into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
When working with iOS project configuration files, validate against Apple's App Store Review Guidelines.
line 8
Distinctive:
No placeholder text remaining
line 16
Distinctive:
Only request entitlements actually used
line 29
Distinctive:
No private API usage
line 35
Distinctive:
No deprecated frameworks that cause rejection
line 36
Distinctive:
No competitor platform references ("Android", "Google Play")
line 37

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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

ios-app-store-validator.mdc

---
description: App Store validation for iOS projects
globs: ["**/*.swift", "**/Info.plist", "**/PrivacyInfo.xcprivacy", "**/*.entitlements", "**/AppDelegate.swift", "**/SceneDelegate.swift"]
---

# iOS App Store Validator

When working with iOS project configuration files, validate against Apple's App Store Review Guidelines.

## Check Info.plist For

- Required usage description strings (NSCameraUsageDescription, NSMicrophoneUsageDescription, NSLocationWhenInUseUsageDescription, NSPhotoLibraryUsageDescription, etc.)
- User-friendly descriptions explaining WHY permission is needed
- UIRequiredDeviceCapabilities correctly declared
- CFBundleIdentifier, CFBundleVersion, CFBundleShortVersionString properly set
- No placeholder text remaining
- LSApplicationQueriesSchemes declared if querying other apps

## Check Privacy Manifest (PrivacyInfo.xcprivacy) For

- File exists if using required reason APIs
- NSPrivacyTracking accurately reflects IDFA usage
- NSPrivacyTrackingDomains lists all tracking domains
- NSPrivacyCollectedDataTypes matches actual data collection
- NSPrivacyAccessedAPITypes covers all required reason APIs

## Check Entitlements For

- Only request entitlements actually used
- Associated domains properly configured for universal links
- Special entitlements documented with explanations

## Check Swift Code For

- No private API usage
- No deprecated frameworks that cause rejection
- No competitor platform references ("Android", "Google Play")
- ATT implementation if using IDFA
- Background modes justified with actual functionality

## Output

Flag issues as:
- BLOCKER: Will cause rejection (cite guideline number)
- WARNING: May cause rejection (include risk level)

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.

Check your setup, free