swift

What problem does it solve?

This skill codifies Swift architectural rules and best practices to help teams build maintainable, concurrency-safe modules in Swift 6.

Core Features & Use Cases

• UseCases (Interactors) must expose a single public function: func execute() async -> Result<T, Error>, with dependencies injected rather than accessing repositories directly.
• Repositories and DataSources must adhere to strict dependency rules: DataSources depend on external APIs, Repositories depend on DataSources, and Repositories expose raw data types via async throws while UseCases map errors to Result.
• Dependency Graph must be UI/ViewModel -> UseCase -> Repository -> DataSource, enabling clear boundaries and testability.
• Language & concurrency patterns emphasize Swift Concurrency (async/await), Actors for shared state, Codable models, and explicit error handling boundaries to avoid leaking internal errors to the UI.
• Use Swift 6 Strict Concurrency checks and @Sendable closures to ensure thread safety and testability.

Quick Start

Create a minimal Swift module that demonstrates a UseCase -> Repository -> DataSource pipeline following the rules described above.