tddworks/ios-app-scaffold
skills/ios-app-scaffold/SKILL.md
Scaffold iOS apps with Tuist and layered architecture (Domain, Infrastructure, App). Use when: (1) Creating a new iOS app project, (2) Setting up Tuist project structure, (3) User asks to "create an iOS app", "scaffold an app", or "set up a new Swift project", (4) User wants layered/clean architecture for iOS, (5) User mentions Tuist setup.
$ install --global
skillsauthnpx skillsauth add tddworks/claude-skills ios-app-scaffoldInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 4:35 AM64.1s3 files scanned
SKILL.md
- name:
- ios-app-scaffold
- description:
- |
- Use when:
- (1) Creating a new iOS app project, (2) Setting up Tuist project structure,
iOS App Scaffold
Scaffold iOS apps with Tuist, Swift 6, and layered architecture.
Quick Start
Run the scaffold script:
python3 scripts/scaffold.py <AppName> <output-directory> [--bundle-id <id>] [--team-id <id>]
Example:
python3 scripts/scaffold.py MyApp /Users/me/projects --bundle-id com.mycompany.myapp --team-id ABC123
Then generate and open:
cd /Users/me/projects/MyApp
tuist generate
open MyApp.xcworkspace
Generated Structure
AppName/
├── Sources/
│ ├── App/ # SwiftUI views, app entry
│ │ ├── Views/
│ │ ├── Resources/
│ │ │ ├── Assets.xcassets
│ │ │ ├── XCConfig/ # Build configuration
│ │ │ │ ├── shared.xcconfig
│ │ │ │ ├── debug.xcconfig
│ │ │ │ └── release.xcconfig
│ │ │ └── en.lproj/
│ │ ├── Application/
│ │ ├── Info.plist
│ │ └── AppNameApp.swift
│ ├── Domain/ # Business logic (no dependencies)
│ │ ├── Models/
│ │ ├── Protocols/ # @Mockable repository interfaces
│ │ └── Utils/
│ └── Infrastructure/ # Persistence implementations
│ └── Local/ # SwiftData repositories
├── Tests/
│ ├── DomainTests/
│ └── InfrastructureTests/
├── Project.swift # Tuist configuration
├── Tuist.swift
├── .gitignore
└── README.md
Architecture
| Layer | Purpose | Dependencies | |-------|---------|--------------| | Domain | Models, protocols, business logic | None | | Infrastructure | SwiftData persistence | Domain | | App | SwiftUI views, app entry | Domain, Infrastructure |
For detailed patterns, see references/architecture.md.
After Scaffolding
- Replace example files: Edit
Example.swift,ExampleRepository.swift,LocalExampleRepository.swift - Add domain models: Create models in
Sources/Domain/Models/ - Define protocols: Add repository protocols in
Sources/Domain/Protocols/ - Implement persistence: Add SwiftData entities in
Sources/Infrastructure/Local/ - Build UI: Create views in
Sources/App/Views/
Adding Dependencies
Edit Project.swift packages array:
packages: [
.remote(url: "https://github.com/Kolos65/Mockable.git", requirement: .upToNextMajor(from: "0.5.0")),
// Add more packages here
],
Then add to target dependencies:
dependencies: [
.package(product: "PackageName"),
]
Key Patterns
Domain models are rich - Include computed properties and business logic:
public struct Order: Identifiable, Codable, Sendable {
public var items: [Item]
public var total: Decimal { items.reduce(0) { $0 + $1.price } }
}
Protocols use @Mockable - Enables testing without real persistence:
@Mockable
public protocol OrderRepository: Sendable {
func fetchAll() async throws -> [Order]
}
Views consume Domain directly - No ViewModel layer needed:
struct OrdersView: View {
let orders: [Order] // Domain model directly
}
Version Management
Version numbers are managed in Project.swift build settings:
settings: .settings(
base: [
"MARKETING_VERSION": "1.0.0", // App Store version
"CURRENT_PROJECT_VERSION": "1", // Build number
],
...
)
The Info.plist references these via build setting variables:
CFBundleShortVersionString→$(MARKETING_VERSION)CFBundleVersion→$(CURRENT_PROJECT_VERSION)
To bump version, edit Project.swift:
"MARKETING_VERSION": "1.1.0",
"CURRENT_PROJECT_VERSION": "2",
XCConfig
Build settings are managed via xcconfig files in Sources/App/Resources/XCConfig/:
| File | Purpose |
|------|---------|
| shared.xcconfig | Common settings (bundle ID, team ID, deployment target) |
| debug.xcconfig | Debug configuration (Apple Development signing) |
| release.xcconfig | Release configuration (Apple Development signing) |
Edit shared.xcconfig to customize:
PRODUCT_BUNDLE_IDENTIFIER = com.yourcompany.app
DEVELOPMENT_TEAM = YOUR_TEAM_ID
IPHONEOS_DEPLOYMENT_TARGET = 18.0
Related Skills
tddworks/template-skill
tools
VerifiedTrustedCommunity
Replace with description of the skill and when Claude should use it.
27SKILL.mdUpdated Apr 20, 2026
tddworks/app-localization
development
VerifiedTrustedCommunity
iOS/macOS app localization management for Tuist-based projects with .strings files. Use when: (1) Adding new translation keys to modules, (2) Validating .strings files for missing/duplicate keys, (3) Syncing translations across languages, (4) AI-powered translation from English to other locales, (5) Checking placeholder consistency (%@, %d), (6) Generating localization reports, (7) Updating Swift code to use localized strings instead of hardcoded text.
27SKILL.mdUpdated Apr 20, 2026
tddworks/swiftui-atomic-design
development
VerifiedTrustedCommunity
Guide for building SwiftUI components using Brad Frost's Atomic Design methodology — organizing views into Atoms, Molecules, Organisms, Templates, and Pages with Design Tokens for theming. Use this skill whenever building new SwiftUI UI components, refactoring existing views into reusable pieces, creating a design system, or organizing a component library. Also trigger when the user mentions "atomic design", "design system", "component hierarchy", "reusable components", "atoms and molecules", "design tokens", or wants to decompose a complex SwiftUI view into smaller, composable parts, or needs to implement theming/customization across a SwiftUI app.
27SKILL.mdUpdated Apr 20, 2026
tddworks/ios-ux-prototype
development
VerifiedTrustedCommunity
Create interactive iOS/mobile app UX flow prototypes as HTML documents with realistic phone mockups. Use when: (1) Visualizing user journeys and navigation flows, (2) Creating mobile app wireframes, (3) Documenting screen-to-screen navigation patterns, (4) Presenting iOS UI designs with annotations, (5) Prototyping app architecture before implementation. Generates self-contained HTML files with iOS-native styling, phone frames, flow arrows, and callout annotations.
27SKILL.mdUpdated Apr 20, 2026