smithery/johnrogers

swiftui-patterns

>- Use when implementing iOS 17+ SwiftUI patterns: @Observable/@Bindable, MVVM architecture, NavigationStack, lazy loading, UIKit interop, accessibility (VoiceOver/Dynamic Type), async operations (.task/.refreshable), or migrating from ObservableObject/@StateObject.

Installation

$ npx skills add smithery/johnrogers --skill swiftui-patterns

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/johnrogers · top by installs.

npx skills add smithery/johnrogers

Browse all from smithery/johnrogers

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,273 B
  • docs SUMMARY.md 287 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

SwiftUI Patterns (iOS 17+)

SwiftUI 17+ removes ObservableObject boilerplate with @Observable, simplifies environment injection with @Environment, and introduces task-based async patterns. The core principle: use Apple's modern APIs instead of reactive libraries.

Overview

Quick Reference

Need Use (iOS 17+) NOT
Observable model @Observable ObservableObject
Published property Regular property @Published
Own state @State @StateObject
Passed model (binding) @Bindable @ObservedObject
Environment injection environment(_:) environmentObject(_:)
Environment access @Environment(Type.self) @EnvironmentObject
Async on appear .task { } .onAppear { Task {} }
Value change onChange(of:initial:_:) onChange(of:perform:)

Core Workflow

  1. Use @Observable for model classes (no @Published needed)
  2. Use @State for view-owned models, @Bindable for passed models
  3. Use .task { } for async work (auto-cancels on disappear)
  4. Use NavigationStack with NavigationPath for programmatic navigation
  5. Apply .accessibilityLabel() and .accessibilityHint() to interactive elements

Reference Loading Guide

ALWAYS load reference files if there is even a small chance the content may be required. It's better to have the context than to miss a pattern or make a mistake.

Reference Load When
[Observable](references/observable.md) Creating new @Observable model classes
[State Management](references/state-management.md) Deciding between @State, @Bindable, @Environment
[Environment](references/environment.md) Injecting dependencies into view hierarchy
[View Modifiers](references/view-modifiers.md) Using onChange, task, or iOS 17+ modifiers
[Migration Guide](references/migration-guide.md) Updating iOS 16 code to iOS 17+
[MVVM Observable](references/mvvm-observable.md) Setting up view model architecture
[Navigation](references/navigation.md) Programmatic or deep-link navigation
[Performance](references/performance.md) Lists with 100+ items or excessive re-renders
[UIKit Interop](references/uikit-interop.md) Wrapping UIKit components (WKWebView, PHPicker)
[Accessibility](references/accessibility.md) VoiceOver, Dynamic Type, accessibility actions
[Async Patterns](references/async-patterns.md) Loading states, refresh, background tasks
[Composition](references/composition.md) Reusable view modifiers or complex conditional UI

Common Mistakes

  1. Over-using @Bindable for passed models — Creating @Bindable for every property causes unnecessary view reloads. Use @Bindable only for mutable model properties that need two-way binding. Read-only computed properties should use regular properties.
  1. State placement errors — Putting model state in the view instead of a dedicated @Observable model causes view logic to become tangled. Always separate model and view concerns.
  1. NavigationPath state corruption — Mutating NavigationPath incorrectly can leave it in inconsistent state. Use navigationDestination(for:destination:) with proper state management to avoid path corruption.
  1. Missing .task cancellation — .task handles cancellation on disappear automatically, but nested Tasks don't. Complex async flows need explicit cancellation tracking to avoid zombie tasks.
  1. Ignoring environment invalidation — Changing environment values at parent doesn't invalidate child views automatically. Use @Environment consistently and understand when re-renders happen based on observation.
  1. UIKit interop memory leaks — UIViewRepresentable and UIViewControllerRepresentable can leak if delegate cycles aren't broken. Weak references and explicit cleanup are required.