Swift Expert

作者 jeffallan1be15d8064f8MIT11K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库5天前更新

Builds iOS/macOS/watchOS/tvOS applications, implements SwiftUI views and state management, designs protocol-oriented architectures, handles async/await concurrency, implements actors for thread safety, and debugs Swift-specific issues. Use when building iOS/macOS applications with Swift 5.9+, SwiftUI, or async/await concurrency. Invoke for protocol-oriented programming, SwiftUI state management, actors, server-side Swift, UIKit integration, Combine, or Vapor.

仅含说明Software Development

AI 生成的概览

指导 Swift 5.9+ 的 Apple 平台开发，涵盖 SwiftUI、async/await、actor、协议与测试。

功能: 为在 iOS、macOS、watchOS 和 tvOS 上构建 Swift 应用提供结构化工作流程与参考资料。内容涵盖 SwiftUI 视图与状态管理、面向协议的架构、async/await 并发、actor 隔离、内存与性能，以及基于 XCTest 的测试。产出包括代码模式、协议与模型定义、视图实现、测试以及架构说明。
适用场景: 适用于实现或调试 Swift 5.9+ 代码时，尤其是 SwiftUI 界面、async/await 或 actor 并发、面向协议的设计、UIKit 或 Combine 集成，以及使用 Vapor 的服务端 Swift。
运行要求: 需要 Swift 5.9+ 工具链以及 swift build、swift test 等构建工具。仅附带参考文档，不包含脚本。

Swift Expert

Core Workflow

Architecture Analysis - Identify platform targets, dependencies, design patterns
Design Protocols - Create protocol-first APIs with associated types
Implement - Write type-safe code with async/await and value semantics
Optimize - Profile with Instruments, ensure thread safety
Test - Write comprehensive tests with XCTest and async patterns

Validation checkpoints: After step 3, run swift build to verify compilation. After step 4, run swift build -warnings-as-errors to surface actor isolation and Sendable warnings. After step 5, run swift test and confirm all async tests pass.

Reference Guide

Load detailed guidance based on context:

Topic	Reference	Load When
SwiftUI	`references/swiftui-patterns.md`	Building views, state management, modifiers
Concurrency	`references/async-concurrency.md`	async/await, actors, structured concurrency
Protocols	`references/protocol-oriented.md`	Protocol design, generics, type erasure
Memory	`references/memory-performance.md`	ARC, weak/unowned, performance optimization
Testing	`references/testing-patterns.md`	XCTest, async tests, mocking strategies

Code Patterns

async/await — Correct vs. Incorrect

swift

// ✅ DO: async/await with structured error handlingfunc fetchUser(id: String) async throws -> User {    let url = URL(string: "https://api.example.com/users/\(id)")!    let (data, _) = try await URLSession.shared.data(from: url)    return try JSONDecoder().decode(User.self, from: data)}
// ❌ DON'T: mixing completion handlers with async contextfunc fetchUser(id: String) async throws -> User {    return try await withCheckedThrowingContinuation { continuation in        // Avoid wrapping existing async APIs this way when a native async version exists        legacyFetch(id: id) { result in            continuation.resume(with: result)        }    }}

// ✅ DO: async/await with structured error handlingfunc fetchUser(id: String) async throws -> User {    let url = URL(string: "https://api.example.com/users/\(id)")!    let (data, _) = try await URLSession.shared.data(from: url)    return try JSONDecoder().decode(User.self, from: data)}
// ❌ DON'T: mixing completion handlers with async contextfunc fetchUser(id: String) async throws -> User {    return try await withCheckedThrowingContinuation { continuation in        // Avoid wrapping existing async APIs this way when a native async version exists        legacyFetch(id: id) { result in            continuation.resume(with: result)        }    }}

SwiftUI State Management

swift

// ✅ DO: use @Observable (Swift 5.9+) for view models@Observablefinal class CounterViewModel {    var count = 0    func increment() { count += 1 }}
struct CounterView: View {    @State private var vm = CounterViewModel()
    var body: some View {        VStack {            Text("\(vm.count)")            Button("Increment", action: vm.increment)        }    }}
// ❌ DON'T: reach for ObservableObject/Published when @Observable sufficesclass LegacyViewModel: ObservableObject {    @Published var count = 0  // Unnecessary boilerplate in Swift 5.9+}

// ✅ DO: use @Observable (Swift 5.9+) for view models@Observablefinal class CounterViewModel {    var count = 0    func increment() { count += 1 }}
struct CounterView: View {    @State private var vm = CounterViewModel()
    var body: some View {        VStack {            Text("\(vm.count)")            Button("Increment", action: vm.increment)        }    }}
// ❌ DON'T: reach for ObservableObject/Published when @Observable sufficesclass LegacyViewModel: ObservableObject {    @Published var count = 0  // Unnecessary boilerplate in Swift 5.9+}

Protocol-Oriented Architecture

swift

// ✅ DO: define capability protocols with associated typesprotocol Repository<Entity> {    associatedtype Entity: Identifiable    func fetch(id: Entity.ID) async throws -> Entity    func save(_ entity: Entity) async throws}
struct UserRepository: Repository {    typealias Entity = User    func fetch(id: UUID) async throws -> User { /* … */ }    func save(_ user: User) async throws { /* … */ }}
// ❌ DON'T: use classes as base types when a protocol fitsclass BaseRepository {  // Avoid class inheritance for shared behavior    func fetch(id: UUID) async throws -> Any { fatalError("Override required") }}

// ✅ DO: define capability protocols with associated typesprotocol Repository<Entity> {    associatedtype Entity: Identifiable    func fetch(id: Entity.ID) async throws -> Entity    func save(_ entity: Entity) async throws}
struct UserRepository: Repository {    typealias Entity = User    func fetch(id: UUID) async throws -> User { /* … */ }    func save(_ user: User) async throws { /* … */ }}
// ❌ DON'T: use classes as base types when a protocol fitsclass BaseRepository {  // Avoid class inheritance for shared behavior    func fetch(id: UUID) async throws -> Any { fatalError("Override required") }}

Actor for Thread Safety

swift

// ✅ DO: isolate mutable shared state in an actoractor ImageCache {    private var cache: [URL: UIImage] = [:]
    func image(for url: URL) -> UIImage? { cache[url] }    func store(_ image: UIImage, for url: URL) { cache[url] = image }}
// ❌ DON'T: use a class with manual lockingclass UnsafeImageCache {    private var cache: [URL: UIImage] = [:]    private let lock = NSLock()  // Error-prone; prefer actor isolation    func image(for url: URL) -> UIImage? {        lock.lock(); defer { lock.unlock() }        return cache[url]    }}

// ✅ DO: isolate mutable shared state in an actoractor ImageCache {    private var cache: [URL: UIImage] = [:]
    func image(for url: URL) -> UIImage? { cache[url] }    func store(_ image: UIImage, for url: URL) { cache[url] = image }}
// ❌ DON'T: use a class with manual lockingclass UnsafeImageCache {    private var cache: [URL: UIImage] = [:]    private let lock = NSLock()  // Error-prone; prefer actor isolation    func image(for url: URL) -> UIImage? {        lock.lock(); defer { lock.unlock() }        return cache[url]    }}

Constraints

MUST DO

Use type hints and inference appropriately
Follow Swift API Design Guidelines
Use async/await for asynchronous operations (see pattern above)
Ensure Sendable compliance for concurrency
Use value types (struct/enum) by default
Document APIs with markup comments (/// …)
Use property wrappers for cross-cutting concerns
Profile with Instruments before optimizing

MUST NOT DO

Use force unwrapping (!) without justification
Create retain cycles in closures
Mix synchronous and asynchronous code improperly
Ignore actor isolation warnings
Use implicitly unwrapped optionals unnecessarily
Skip error handling
Use Objective-C patterns when Swift alternatives exist
Hardcode platform-specific values

Output Templates

When implementing Swift features, provide:

Protocol definitions and type aliases
Model types (structs/classes with value semantics)
View implementations (SwiftUI) or view controllers
Tests demonstrating usage
Brief explanation of architectural decisions

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

来源与署名

来源：jeffallan/claude-skills位于skills/swift-expert提交1be15d8

许可证： MIT

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

Swift Expert

Swift Expert

Core Workflow

Reference Guide

Code Patterns

async/await — Correct vs. Incorrect

SwiftUI State Management

Protocol-Oriented Architecture

Actor for Thread Safety

Constraints

MUST DO

MUST NOT DO

Output Templates

来源与署名

更多来自 jeffallan/claude-skills 的技能

Wordpress Pro

Vue Expert Js

The Fool

Sql Pro

Spring Boot Engineer

Spark Engineer

更多Software Development技能

Playground

M5 Onboard

Cardputer Buddy

Dpop Adoption

Gemini Live Api

Gemini Api