dpearson2699/swift-ios-skills

swift-architecture

Selects, reviews, and migrates Apple-platform app architectures across MV with Observation, MVVM, MVI, TCA, Clean Architecture, Coordinator, and legacy VIPER.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/dpearson2699/swift-ios-skills --skill swift-architecture

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

Swift Architecture

Choose the smallest architecture that makes state ownership, dependencies, side effects, and tests explicit. Default new SwiftUI features to MV; escalate only for observed complexity.

Contents

Scope Boundary

This skill owns pattern selection, module boundaries, dependency direction, migration strategy, and architecture-level test seams. Route SwiftUI property-wrapper wiring and view composition to swiftui-patterns, navigation APIs and route models to swiftui-navigation, isolation diagnostics to swift-concurrency, and test syntax/fixtures to swift-testing.

Decision Workflow

  1. Record the feature's state owner, inputs, outputs, dependencies, side effects, navigation handoffs, and current tests.
  2. Identify the concrete pressure: complex state machine, shared derived state, dependency control, feature composition, team ownership, or UIKit navigation.
  3. Select the smallest pattern that addresses that pressure; write down what it adds and what remains unchanged.
  4. Implement one vertical slice with injected dependencies and observable state transitions.
  5. Run existing behavior tests plus state-transition and dependency-failure tests. If behavior changes, restore the fixture, fix the smallest boundary, and rerun before migrating another slice.

Pattern Selection

PatternChoose whenMain cost
MVSwiftUI feature has straightforward state and orchestrationLogic can drift into large views without decomposition
MVVMPresentation logic needs an independently testable adapterExtra layer can become a forwarding shell
MVIA feature is best modeled as explicit state + intents + reducer/effectsBoilerplate and centralized transition design
TCAMany composable features need deterministic effects, dependencies, and testingFramework learning and architectural commitment
Clean ArchitectureLarge product needs strict dependency direction across domain/data/UIProtocol and mapping overhead
CoordinatorUIKit or hybrid navigation needs a separate flow ownerAnother lifecycle and routing owner
VIPERMaintaining an existing UIKit module with established VIPER boundariesVery high ceremony; poor default for new SwiftUI work

Use Coordinator alongside another state pattern when navigation complexity is the pressure; it is not a replacement for domain/state architecture.

MV Default

Keep views as state expressions and put business operations in observable models and injected services:

swift
@MainActor
@Observable
final class TripStore {
    private let client: TripClient
    var trips: [Trip] = []
    var error: Error?

    init(client: TripClient) { self.client = client }

    func load() async {
        do { trips = try await client.fetchTrips() }
        catch { self.error = error }
    }
}

struct TripList: View {
    @State private var store: TripStore

    init(client: TripClient) {
        _store = State(initialValue: TripStore(client: client))
    }

    var body: some View {
        List(store.trips) { Text($0.name) }
            .task { await store.load() }
    }
}

Load Architecture Pattern Recipes for MVVM, MVI, TCA, Clean Architecture, Coordinator, and VIPER structure.

Escalation Signals

  • Choose MVVM when substantial presentation transformation must be tested without rendering and the adapter has real behavior.
  • Choose MVI when transitions, invalid states, and effects need one auditable reducer-like path.
  • Choose TCA when feature composition, dependency overrides, cancellation, and deterministic effect tests recur across modules.
  • Choose Clean Architecture when independent domain rules and dependency direction matter across multiple delivery/data layers.
  • Add Coordinator for UIKit/hybrid route ownership, deep flow composition, or conditional navigation outside view controllers.
  • Keep VIPER for compatible legacy modules or deliberate migrations; do not start a new SwiftUI feature with it by habit.

Do not escalate merely because a view is long. First extract subviews, services, and focused observable models.

Migration

Migrate one feature boundary at a time:

  1. Freeze behavior with tests and a dependency/state inventory.
  2. Introduce the target boundary around existing operations.
  3. Move one state transition or dependency at a time without rewriting UI and persistence simultaneously.
  4. Compare behavior, navigation, cancellation, error, and persistence results after each slice.
  5. Remove the old path only after no callers or tests depend on it.

For ObservableObject to Observation, preserve the same owner and mutation isolation before replacing wrappers. For MVVM to MV, delete forwarding view-model members only after views bind to the same model/service behavior. For TCA adoption, wrap one feature's state/actions/effects and migrate dependencies incrementally.

Common Mistakes

MistakeFix
Pattern chosen by popularityTie it to an observed feature pressure.
View model only forwards propertiesRemove it and use MV.
One object owns navigation, networking, formatting, persistence, and UI stateSplit by responsibility and dependency direction.
TCA or Clean Architecture applied to trivial screensStart with MV and preserve an escalation seam.
Coordinator used as a state architectureKeep it focused on route/lifecycle ownership.
Multiple patterns mixed inside one featureDefine one local state/effect model and migrate at feature boundaries.
Big-bang migrationMove one tested vertical slice and rerun the same proof matrix.

Review Checklist

  • [ ] Choice is justified by concrete feature/team pressures
  • [ ] State owner, mutation path, dependencies, effects, and navigation owner are explicit
  • [ ] Dependencies are injected and replaceable in tests
  • [ ] Pattern cost is proportional to feature complexity
  • [ ] UI mechanics, navigation APIs, isolation, and test syntax route to sibling skills
  • [ ] Migration preserves behavior one vertical slice at a time
  • [ ] Failure, cancellation, navigation, and persistence behavior are verified after each slice
  • [ ] No forwarding-only layers or god objects remain

References

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
dpearson2699
Społeczność

app-intents

Implement App Intents for Siri, Shortcuts, Spotlight, widgets, Control Center, and Apple Intelligence on iOS. Covers AppIntent actions, AppEntity and EntityQuery models, AppShortcutsProvider phrases, IndexedEntity Spotlight indexing, WidgetConfigurationIntent, SnippetIntent, and assistant schemas. Use when exposing app actions or entities to system surfaces.

Instalacje / 1h
2
GitHub Stars
1,3 tys.
Aktualizacja
31 lip
dpearson2699
Społeczność

carplay

Build CarPlay-enabled apps using the CarPlay framework. Use when creating navigation, audio, communication, EV charging, parking, or food ordering apps for the car display, working with CPTemplateApplicationScene, CPInterfaceController template hierarchies, CPListTemplate, CPMapTemplate, CPNowPlayingTemplate, configuring CarPlay entitlements, or integrating with CarPlay Simulator for testing.

Instalacje / 1h
2
GitHub Stars
1,3 tys.
Aktualizacja
31 lip
dpearson2699
Społeczność

ios-accessibility

Build and audit SwiftUI, UIKit, and AppKit accessibility for VoiceOver, Voice Control, Switch Control, Full Keyboard Access, Dynamic Type, focus restoration, labels/traits/actions, traversal, custom rotors, NSAccessibility, XCTest checks, adaptive system preferences, and App Store accessibility declarations. Use when implementing accessible UI, fixing an accessibility audit, testing assistive-technology behavior, or substantiating App Store Accessibility Nutrition Labels.

Instalacje / 1h
1
GitHub Stars
1,3 tys.
Aktualizacja
31 lip
dpearson2699
Społeczność

speech-recognition

Transcribe speech to text using Apple's Speech framework. Use when implementing live microphone transcription with AVAudioEngine, recognizing recorded audio files, handling speech and microphone authorization, choosing on-device vs server-backed SFSpeechRecognizer behavior, or adopting SpeechAnalyzer, SpeechTranscriber, DictationTranscriber, AssetInventory, and async result streams on iOS 26+.

Instalacje / 1h
1
GitHub Stars
1,3 tys.
Aktualizacja
31 lip