SwiftUI Empty App Init

**Quick judgment:** This skill is well-focused and suitable for iOS developers who want a clean, XcodeGen-driven SwiftUI starter app with no extra scaffolding. Its scope is intentionally narrow but appears coherent and useful. **Strengths:** - Produces a minimal, single-target SwiftUI iOS app with modern @main lifecycle and a basic ContentView. - Uses XcodeGen for project generation, which is a strong choice for maintainability and reproducibility. - Enforces a simple structure (single .xcodeproj, no workspace, no packages, no tests by default) that is ideal for greenfield work. - Sensible defaults (e.g., `com.example.<ProjectName>` bundle ID) and minimal Info.plist keep the result clean and unopinionated. - Explicit prerequisite checks and lightweight post-generation verification improve robustness. **Key risks / limitations:** - Requires XcodeGen to be preinstalled and on PATH; users unfamiliar with it may face setup friction. - Behavior in non-empty directories or name collisions is not specified, so there is some uncertainty about overwriting or error handling in edge cases. - Lack of built-in options for tests, packages, or additional targets may be limiting for teams that want a richer template out of the box. **Best-fit scenarios:** - iOS/macOS developers who already use or are comfortable adopting XcodeGen and want a reproducible, minimal SwiftUI starter. - Teams standardizing on a very barebones template that they will extend with their own scripts, tests, or package setup. - Quick prototypes, tutorials, or experiments where extra scaffolding (workspaces, SPM, architectures) would be a distraction rather than a benefit.