shipping-skills / rules
Cursor rule1 starsChanged 10 days agoMITView on GitHub
Take a SwiftUI iOS app from source to TestFlight and the App Store — XcodeGen project.yml setup, bundling resources, build and marketing version numbers, archiving, the privacy manifest, App Privacy answers, screenshots and creative assets at Apple's exact pixel sizes, and the pre-submission checklist. Use this whenever you are configuring an Xcode project, preparing a build for upload, answering anything in App Store Connect, generating store screenshots, setting up internal or external TestFlight testers, or diagnosing a rejection. Reach for it before the first submission rather than after — most rejections here are metadata, and most of them are predictable.
We split this ios-app-store-release.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 6
Read skills/ios-app-store-release/SKILL.md in this repository and follow it.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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.
Files
--- description: Take a SwiftUI iOS app from source to TestFlight and the App Store — XcodeGen project.yml setup, bundling resources, build and marketing version numbers, archiving, the privacy manifest, App Privacy answers, screenshots and creative assets at Apple's exact pixel sizes, and the pre-submission checklist. Use this whenever you are configuring an Xcode project, preparing a build for upload, answering anything in App Store Connect, generating store screenshots, setting up internal or external TestFlight testers, or diagnosing a rejection. Reach for it before the first submission rather than after — most rejections here are metadata, and most of them are predictable. alwaysApply: false --- Read `skills/ios-app-store-release/SKILL.md` in this repository and follow it. It is the single source of truth for this topic — this rule only points at it, so that the guidance cannot drift between the formats different tools expect.
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 3,978 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/app-flow-design.mdcCursor rule
- .cursor/rules/supabase-auth-swift.mdcCursor rule
- .cursor/rules/supabase-edge-functions.mdcCursor rule
- .cursor/rules/supabase-rls-data-model.mdcCursor rule
- app-flow-designSkill
- ios-app-store-releaseSkill
- supabase-auth-swiftSkill
- supabase-edge-functionsSkill
- supabase-rls-data-modelSkill
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.