ios-project-setup
Skill1 starsChanged 36 days agoMITView on GitHub
Set up or clean up an iOS project foundation — new Xcode project or XcodeGen/Tuist spec, targets and schemes, build configurations and xcconfigs, Swift Package dependencies, bundle IDs and capabilities, signing, a repo CLAUDE.md, and CI. Use when starting a new iOS app, adding a target (widget, extension, watch), or when "the project setup is a mess".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jx1100370217/my-openclaw-skillstheir own version, first seen Feb 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jx1100370217/my-openclaw-skills★ 4same 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.
- app-store-listingSkill
- ios-app-intentsSkill
- ios-crash-monitoring-sentrySkill
- ios-debugger-agentSkill
- ios-ettrace-performanceSkill
- ios-lifecycleSkill
- ios-memgraph-leaksSkill
- ios-monetizationSkill
- ios-post-launchSkill
- 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
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 13
Don't convert project styles unless the user asks.
- Very specific: line 22
Use .xcconfig files for Debug, Release and (optionally) Staging.
- Very specific: line 23
No secrets in the repo. Use a git-ignored Secrets.xcconfig with a committed Secrets.example.xcconfig.
- Very specific: line 24
Keep PrivacyInfo.xcprivacy from day one.
- Very specific: line 36
Prefer automatic signing for development.
- Distinctive: line 37
Never create, export or move certificates or private keys yourself.
- Distinctive: line 41
Create or update CLAUDE.md at the repo root with:
- Very specific: line 56
Use a simulator name that actually exists on this Mac (xcrun simctl list devices available).
- Distinctive: line 64
Do a clean build and test run for every scheme you touched.
≈ “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 Project Setup
1. Inspect before changing
- Detect the project style: plain
.xcodeproj, XcodeGen (project.yml), Tuist (Project.swift), or SPM-only (Package.swift). - List the schemes and targets:
xcodebuild -list -json(or the XcodeBuildMCP discovery tools). - Note the deployment target, Swift version, strict-concurrency setting, bundle IDs, team ID, and entitlements files.
- Don't convert project styles unless the user asks.
2. New project defaults
Unless the user says otherwise:
- Structure:
App/(entry point, app wiring),Features/<Feature>/(views, models, view models),Core/(networking, persistence, utilities),Resources/,Tests/,UITests/. - For larger apps, put features in local Swift packages (
Packages/). This speeds up builds and previews. - Swift 6 language mode with complete concurrency checking.
@MainActoron UI types. - Use
.xcconfigfiles for Debug, Release and (optionally) Staging. Keep the bundle ID suffix, API base URL and feature flags in the xcconfig, not in code. - No secrets in the repo. Use a git-ignored
Secrets.xcconfigwith a committedSecrets.example.xcconfig. - Keep
PrivacyInfo.xcprivacyfrom day one. Declare required-reason APIs as you adopt them.
3. Extensions and extra targets
For widgets, Live Activities, App Intents extensions, share extensions, or watchOS:
- Share code through a framework or local package, not by adding files to several targets.
- Set up an App Group when the app and extension share data, and keep the identifier in one constant.
- Match the deployment targets and versions to the main app (
MARKETING_VERSION,CURRENT_PROJECT_VERSION).
4. Signing
- Prefer automatic signing for development. For release, use fastlane match or Xcode Cloud managed signing. See
ios-release. - Never create, export or move certificates or private keys yourself. Explain what's needed and let the user do it.
5. Repo CLAUDE.md
Create or update CLAUDE.md at the repo root with:
# <App name>
- What: one line on what the app does
- Open: <App>.xcodeproj | <App>.xcworkspace
- Schemes: <App> (Debug/Release), <App>Tests
- Build: xcodebuild -scheme <App> -destination 'platform=iOS Simulator,name=iPhone 17' build
- Test: xcodebuild -scheme <App> -destination 'platform=iOS Simulator,name=iPhone 17' test
- Release: bundle exec fastlane beta | release
- Min iOS: <x> Swift: 6 Concurrency: complete
- Conventions: <state management, folder layout, naming>
- Gotchas: <anything that bit us>Use a simulator name that actually exists on this Mac (xcrun simctl list devices available).
6. CI (optional)
Offer a GitHub Actions workflow on a macos-latest runner (or Xcode Cloud) that builds and tests on every PR. Select the Xcode version explicitly. Cache SPM in ~/Library/Developer/Xcode/DerivedData/**/SourcePackages.
7. Verify
Do a clean build and test run for every scheme you touched. Report what was changed and the commands to reproduce.
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.