swiftui-patterns
affaan-m/everything-claude-code
Modern SwiftUI patterns: @Observable state, type-safe navigation, view composition, and performance optimization.
What is swiftui-patterns?
Covers contemporary SwiftUI architecture using the Observation framework, NavigationStack for routing, view composition strategies, and rendering performance best practices. Use this when building declarative UIs on iOS/macOS with proper state management and efficient layouts.
- Manage state with @Observable, @State, @Binding, and @Environment for fine-grained reactivity
- Design type-safe navigation flows using NavigationStack and Destination enums
- Compose views into small, focused structs to limit re-renders and improve maintainability
- Optimize rendering performance with LazyVStack, stable identifiers, and Equatable conformance
- Inject dependencies via environment values and avoid legacy ObservableObject patterns
- Use .task{} for async work that cancels automatically on view disappearance
How to install swiftui-patterns
npx skills add https://github.com/affaan-m/everything-claude-code --skill swiftui-patternsHow to use swiftui-patterns
- 1.Choose the appropriate property wrapper (@State, @Observable, @Binding, @Environment) based on your data ownership and sharing needs
- 2.Structure view models as @Observable classes and own them with @State in the consuming view
- 3.Break views into small, focused subviews to ensure only changed properties trigger re-renders
- 4.Use NavigationStack with a Router @Observable class and Destination enum for programmatic navigation
- 5.Apply LazyVStack/LazyHStack for large collections and always use stable, unique identifiers in ForEach
- 6.Avoid expensive work in body; use .task{} for async operations and ViewModifier for reusable styling
Use cases
- Building a list-based app with search and filtering using @Observable view models
- Implementing multi-screen navigation with programmatic routing via NavigationStack
- Structuring a complex form with multiple sections and conditional state updates
- Optimizing a scrollable collection of hundreds of items with lazy rendering
- Sharing authentication state across the app via @Environment injection
- iOS/macOS app developers adopting modern SwiftUI (iOS 17+)
- Engineers migrating from ObservableObject to @Observable
- Teams building performant list-heavy or data-driven UIs
- Developers implementing type-safe navigation architectures
swiftui-patterns FAQ
Use @State for simple value types (toggles, strings, numbers). Use @Observable for classes with multiple properties that you own; wrap the instance in @State. Use @Observable without a wrapper when reading a reference passed from a parent.
Extract subviews so only the view reading a changed property re-renders. Use Equatable conformance on expensive views. Use LazyVStack for large lists. Avoid putting computed properties or expensive logic in body.
@Environment with the Observation framework. Inject with .environment(object) and consume with @Environment(Type.self).
Create a Router @Observable class with a NavigationPath property, use NavigationStack(path:) bound to it, and define a Destination enum with all possible routes. Call router.navigate(to:) to push or router.popToRoot() to reset.
.task{} is preferred—it automatically cancels when the view disappears, preventing memory leaks and stale requests. Use .onAppear{} only for non-async side effects.
Full instructions (SKILL.md)
Source of truth, from affaan-m/everything-claude-code.
name: swiftui-patterns description: SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.
SwiftUI Patterns
Modern SwiftUI patterns for building declarative, performant user interfaces on Apple platforms. Covers the Observation framework, view composition, type-safe navigation, and performance optimization.
When to Activate
- Building SwiftUI views and managing state (
@State,@Observable,@Binding) - Designing navigation flows with
NavigationStack - Structuring view models and data flow
- Optimizing rendering performance for lists and complex layouts
- Working with environment values and dependency injection in SwiftUI
State Management
Property Wrapper Selection
Choose the simplest wrapper that fits:
| Wrapper | Use Case |
|---|---|
@State | View-local value types (toggles, form fields, sheet presentation) |
@Binding | Two-way reference to parent's @State |
@Observable class + @State | Owned model with multiple properties |
@Observable class (no wrapper) | Read-only reference passed from parent |
@Bindable | Two-way binding to an @Observable property |
@Environment | Shared dependencies injected via .environment() |
@Observable ViewModel
Use @Observable (not ObservableObject) — it tracks property-level changes so SwiftUI only re-renders views that read the changed property:
@Observable
final class ItemListViewModel {
private(set) var items: [Item] = []
private(set) var isLoading = false
var searchText = ""
private let repository: any ItemRepository
init(repository: any ItemRepository = DefaultItemRepository()) {
self.repository = repository
}
func load() async {
isLoading = true
defer { isLoading = false }
items = (try? await repository.fetchAll()) ?? []
}
}
View Consuming the ViewModel
struct ItemListView: View {
@State private var viewModel: ItemListViewModel
init(viewModel: ItemListViewModel = ItemListViewModel()) {
_viewModel = State(initialValue: viewModel)
}
var body: some View {
List(viewModel.items) { item in
ItemRow(item: item)
}
.searchable(text: $viewModel.searchText)
.overlay { if viewModel.isLoading { ProgressView() } }
.task { await viewModel.load() }
}
}
Environment Injection
Replace @EnvironmentObject with @Environment:
// Inject
ContentView()
.environment(authManager)
// Consume
struct ProfileView: View {
@Environment(AuthManager.self) private var auth
var body: some View {
Text(auth.currentUser?.name ?? "Guest")
}
}
View Composition
Extract Subviews to Limit Invalidation
Break views into small, focused structs. When state changes, only the subview reading that state re-renders:
struct OrderView: View {
@State private var viewModel = OrderViewModel()
var body: some View {
VStack {
OrderHeader(title: viewModel.title)
OrderItemList(items: viewModel.items)
OrderTotal(total: viewModel.total)
}
}
}
ViewModifier for Reusable Styling
struct CardModifier: ViewModifier {
func body(content: Content) -> some View {
content
.padding()
.background(.regularMaterial)
.clipShape(RoundedRectangle(cornerRadius: 12))
}
}
extension View {
func cardStyle() -> some View {
modifier(CardModifier())
}
}
Navigation
Type-Safe NavigationStack
Use NavigationStack with NavigationPath for programmatic, type-safe routing:
@Observable
final class Router {
var path = NavigationPath()
func navigate(to destination: Destination) {
path.append(destination)
}
func popToRoot() {
path = NavigationPath()
}
}
enum Destination: Hashable {
case detail(Item.ID)
case settings
case profile(User.ID)
}
struct RootView: View {
@State private var router = Router()
var body: some View {
NavigationStack(path: $router.path) {
HomeView()
.navigationDestination(for: Destination.self) { dest in
switch dest {
case .detail(let id): ItemDetailView(itemID: id)
case .settings: SettingsView()
case .profile(let id): ProfileView(userID: id)
}
}
}
.environment(router)
}
}
Performance
Use Lazy Containers for Large Collections
LazyVStack and LazyHStack create views only when visible:
ScrollView {
LazyVStack(spacing: 8) {
ForEach(items) { item in
ItemRow(item: item)
}
}
}
Stable Identifiers
Always use stable, unique IDs in ForEach — avoid using array indices:
// Use Identifiable conformance or explicit id
ForEach(items, id: \.stableID) { item in
ItemRow(item: item)
}
Avoid Expensive Work in body
- Never perform I/O, network calls, or heavy computation inside
body - Use
.task {}for async work — it cancels automatically when the view disappears - Use
.sensoryFeedback()and.geometryGroup()sparingly in scroll views - Minimize
.shadow(),.blur(), and.mask()in lists — they trigger offscreen rendering
Equatable Conformance
For views with expensive bodies, conform to Equatable to skip unnecessary re-renders:
struct ExpensiveChartView: View, Equatable {
let dataPoints: [DataPoint] // DataPoint must conform to Equatable
static func == (lhs: Self, rhs: Self) -> Bool {
lhs.dataPoints == rhs.dataPoints
}
var body: some View {
// Complex chart rendering
}
}
Previews
Use #Preview macro with inline mock data for fast iteration:
#Preview("Empty state") {
ItemListView(viewModel: ItemListViewModel(repository: EmptyMockRepository()))
}
#Preview("Loaded") {
ItemListView(viewModel: ItemListViewModel(repository: PopulatedMockRepository()))
}
Anti-Patterns to Avoid
- Using
ObservableObject/@Published/@StateObject/@EnvironmentObjectin new code — migrate to@Observable - Putting async work directly in
bodyorinit— use.task {}or explicit load methods - Creating view models as
@Stateinside child views that don't own the data — pass from parent instead - Using
AnyViewtype erasure — prefer@ViewBuilderorGroupfor conditional views - Ignoring
Sendablerequirements when passing data to/from actors
References
See skill: swift-actor-persistence for actor-based persistence patterns.
See skill: swift-protocol-di-testing for protocol-based DI and testing with Swift Testing.
Related skills
More from affaan-m/everything-claude-code and the wider catalog.
security-review
Security checklist and patterns for authentication, input validation, secrets, and sensitive features.
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable applications.
coding-standards
Baseline coding conventions for naming, readability, immutability, and quality across projects.
frontend-patterns
React and Next.js patterns for components, state management, performance, and modern frontend practices.
backend-patterns
REST/GraphQL API design, database optimization, and server-side patterns for Node.js, Express, and Next.js.
golang-testing
Go testing patterns: table-driven tests, subtests, benchmarks, fuzzing, and TDD methodology.