swift-patterns
Original:🇺🇸 English
Translated
Review, refactor, or build SwiftUI features with correct state management, modern API usage, optimal view composition, navigation patterns, performance optimization, and testing best practices.
17installs
Added on
NPX Install
npx skill4agent add efremidze/swift-patterns-skill swift-patternsTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →swift-patterns
Review, refactor, or build SwiftUI features with correct state management, modern API usage, optimal view composition, and performance-conscious patterns. Prioritize native APIs, Apple design guidance, and testable code structure. This skill focuses on facts and best practices without enforcing specific architectural patterns.
Workflow Decision Tree
1) Review existing SwiftUI code
→ Read for review methodology
references/workflows-review.md- Check state management against property wrapper selection (see )
references/state.md - Verify view composition and extraction patterns (see )
references/view-composition.md - Audit list performance and identity stability (see )
references/lists-collections.md - Validate modern API usage (see )
references/modern-swiftui-apis.md - Check async work patterns with .task (see )
references/concurrency.md - Verify navigation implementation (see )
references/navigation.md - Use Review Response Template (below)
2) Refactor existing SwiftUI code
→ Read for refactor methodology
references/workflows-refactor.md- Extract complex views using playbooks (see )
references/refactor-playbooks.md - Migrate deprecated APIs to modern equivalents (see )
references/modern-swiftui-apis.md - Optimize performance hot paths (see )
references/performance.md - Restructure state ownership (see )
references/state.md - Apply common patterns (see )
references/patterns.md - Use Refactor Response Template (below)
3) Implement new SwiftUI features
- Design data flow first: identify owned vs injected state (see )
references/state.md - Structure views for optimal composition (see )
references/view-composition.md - Use modern APIs only (see )
references/modern-swiftui-apis.md - Handle async work with .task modifier (see )
references/concurrency.md - Apply performance patterns early (see )
references/performance.md - Implement navigation flows (see )
references/navigation.md
4) Answer best practice questions
- Load relevant reference file(s) based on topic (see Reference Files below)
- Provide direct guidance with examples
If intent unclear, ask: "Do you want findings only (review), or should I change the code (refactor)?"
Response Templates
Review Response:
- Scope - What was reviewed
- Findings - Grouped by severity with actionable statements
- Evidence - File paths or code locations
- Risks and tradeoffs - What could break or needs attention
- Next steps - What to fix first or verify
Refactor Response:
- Intent + scope - What is being changed and why
- Changes - Bulleted list with file paths
- Behavior preservation - What should remain unchanged
- Next steps - Tests or verification needed
Quick Reference: Property Wrapper Selection
| Wrapper | Use When | Ownership |
|---|---|---|
| Internal view state (value type or | View owns |
| Child needs to modify parent's state | Parent owns |
| Injected | Injected |
| Read-only value from parent | Injected |
| Read-only value needing reactive updates | Injected |
Key rules:
- Always mark as
@State(makes ownership explicit)private - Never use for passed values (accepts initial value only)
@State - Use with
@Stateclasses (not@Observable)@StateObject
See for detailed guidance and tradeoffs.
references/state.mdQuick Reference: Modern API Replacements
| Deprecated | Modern Alternative | Notes |
|---|---|---|
| | Supports dynamic type |
| | More flexible |
| | Type-safe navigation |
| | iOS 18+ |
| | Unless need location/count |
| | Two or zero parameters |
| | Avoid hard-coded sizes |
See for complete migration guide.
references/modern-swiftui-apis.mdReview Checklist
Use this when reviewing SwiftUI code:
State Management
- properties marked
@Stateprivate - Passed values NOT declared as or
@State@StateObject - only where child modifies parent state
@Binding - Property wrapper selection follows ownership rules
- State ownership clear and intentional
Modern APIs
- No deprecated modifiers (foregroundColor, cornerRadius, etc.)
- Using instead of
NavigationStackNavigationView - Using instead of
Buttonwhen appropriateonTapGesture - Using two-parameter or no-parameter
onChange()
View Composition
- Using modifiers over conditionals for state changes (maintains identity)
- Complex views extracted to separate subviews
- Views kept small and focused
- View simple and pure (no side effects)
body
Navigation & Sheets
- Using for type-safe navigation
navigationDestination(for:) - Using for model-based sheets
.sheet(item:) - Sheets own their dismiss actions
Lists & Collections
- uses stable identity (never
ForEachfor dynamic data).indices - Constant number of views per element
ForEach - No inline filtering in (prefilter and cache)
ForEach - No in list rows
AnyView
Performance
- Passing only needed values to views (not large config objects)
- Eliminating unnecessary dependencies
- Checking value changes before state assignment in hot paths
- Using /
LazyVStackfor large listsLazyHStack - No object creation in view
body
Async Work
- Using for automatic cancellation
.task - Using for value-dependent tasks
.task(id:) - Not mixing with async work
.onAppear
See reference files for detailed explanations of each item.
Constraints
- Swift/SwiftUI focus only - Exclude server-side Swift and UIKit unless bridging required
- No Swift concurrency patterns - Use for SwiftUI async work
.task - No architecture mandates - Don't require MVVM/MVC/VIPER or specific structures
- No formatting/linting rules - Focus on correctness and patterns
- No tool-specific guidance - No Xcode, Instruments, or IDE instructions
- Citations allowed: ,
developer.apple.com/documentation/swiftui/developer.apple.com/documentation/swift/
All workflows must follow these constraints.
Philosophy
This skill focuses on facts and best practices from Apple's documentation:
- Modern APIs over deprecated ones
- Clear state ownership patterns
- Performance-conscious view composition
- Testable code structure
- No architectural mandates (MVVM/VIPER not required)
- Apple Human Interface Guidelines adherence
Reference Files
All references in :
references/- - Review methodology and findings taxonomy
workflows-review.md - - Refactor methodology and invariants
workflows-refactor.md - - Step-by-step refactor guides
refactor-playbooks.md - - Property wrappers and ownership patterns
state.md - - Navigation implementation patterns
navigation.md - - View structure and extraction
view-composition.md - - Identity and ForEach patterns
lists-collections.md - - Scroll handling and pagination
scrolling.md - - Async work with .task
concurrency.md - - Optimization strategies
performance.md - - Testing and dependency injection
testing-di.md - - Common SwiftUI patterns
patterns.md - - Legacy API migration
modern-swiftui-apis.md - - Code quality checks
code-review-refactoring.md