Configure Xcode Projects for Optimal Development

This skill covers Xcode project setup and configuration for iOS/macOS development - project organization, build settings, dependency management, and automated configuration. Core structural principles: organize code into logical groups mirroring the filesystem, separate business logic/UI/networking/data into distinct folders, use consistent naming, follow reverse-DNS bundle identifiers, and set deployment targets by feature requirement.

It gives concrete build-setting values for Debug (DEBUG_INFORMATION_FORMAT = dwarf-with-dsym, ENABLE_TESTABILITY = YES, SWIFT_OPTIMIZATION_LEVEL = -Onone) versus Release (SWIFT_OPTIMIZATION_LEVEL = -O, SWIFT_COMPILATION_MODE = wholemodule, VALIDATE_PRODUCT = YES), plus security settings (ENABLE_HARDENED_RUNTIME = YES, CODE_SIGN_INJECT_BASE_ENTITLEMENTS = YES). Dependency management is covered for both Swift Package Manager (a full Package.swift example targeting iOS 15/macOS 12 with Alamofire and RealmSwift) and CocoaPods as an alternative (a Podfile with a test target using Quick/Nimble, plus a post_install hook to force a consistent IPHONEOS_DEPLOYMENT_TARGET across all pod targets).

Use it when setting up or hardening an Xcode project's configuration: essential Info.plist keys (CFBundleDisplayName, CFBundleIdentifier, CFBundleVersion, LSRequiresIPhoneOS, ITSAppUsesNonExemptEncryption, and others), separate schemes for Debug/Staging/Production with environment-specific API endpoints and feature flags via preprocessor conditions (#if DEBUG / #elseif STAGING), code signing (automatic for development, manual for distribution, with team IDs and provisioning profiles configured rather than hand-edited entitlements), and a build-phase script example that auto-increments CFBundleVersion on Release builds via PlistBuddy.

Don't hardcode sensitive information into the project or commit it to version control - the skill specifically recommends .xcconfig files for environment-specific settings, proper App Transport Security configuration, and keychain sharing groups instead.

Testing guidance covers setting up both unit and UI test targets, configuring test plans for different scenarios, enabling code coverage collection, proper test-host configuration, and simulator destinations for automated testing. Performance guidance covers whole-module optimization for release builds, dead-code stripping, asset catalogs for efficient resource management, bitcode when required by the distribution method, and correct library/framework search paths.

Covers Swift Package Manager and CocoaPods as dependency managers, with Alamofire, RealmSwift, Quick, and Nimble as example packages. Security guidance closes the loop on all of the above: never commit sensitive information to version control, keep environment-specific settings in .xcconfig files rather than hardcoded build settings, and enable hardened runtime specifically for macOS applications.

iOS/macOS developers setting up or standardizing a new Xcode project's build configuration, dependency management, scheme structure, and code-signing setup, rather than relying on Xcode's raw defaults.