Ios Expert
swiftui general rules
When reviewing or writing code, apply these guidelines:
- You are an expert in coding with Swift and SwiftUI.
- Always write maintainable and clean code.
- Focus on the latest August, September 2024 version of the documentation and features.
- Descriptions should be short and concise.
- Don't remove any comments.
swiftui project structure rules
When reviewing or writing code, apply these guidelines:
- Enforce the following SwiftUI project structure:
- The main folder contains a "Sources" folder with:
- "App" for main files
- "Views" divided into "Home" and "Profile" sections with their ViewModels
- "Shared" for reusable components and modifiers
- "Models" for data models
- "ViewModels" for view-specific logic
- "Services" with:
- "Network" for networking
- "Persistence" for data storage
- "Utilities" for extensions, constants, and helpers
- The "Resources" folder holds:
- "Assets" for images and colors
- "Localization" for localized strings
- "Fonts" for custom fonts
- The "Tests" folder includes:
- "UnitTests" for unit testing
- "UITests" for UI testing
swiftui ui design rules
When reviewing or writing code, apply these guidelines:
- Use Built-in Components: Utilize SwiftUI's native UI elements like List, NavigationView, TabView, and SF Symbols for a polished, iOS-consistent look.
- Master Layout Tools: Employ VStack, HStack, ZStack, Spacer, and Padding for responsive designs; use LazyVGrid and LazyHGrid for grids; GeometryReader for dynamic layouts.
- Add Visual Flair: Enhance UIs with shadows, gradients, blurs, custom shapes, and animations using the .animation() modifier for smooth transitions.
- Design for Interaction: Incorporate gestures (swipes, long presses), haptic feedback, clear navigation, and responsive elements to improve user engagement and satisfaction.
Iron Laws
- ALWAYS use
@MainActor for UI updates — SwiftUI and UIKit views must be modified on the main thread; background thread UI updates cause runtime crashes or silent visual corruption.
- NEVER use
@State for data that is shared between views — @State is local to the view and does not propagate changes to siblings or parents; use @ObservedObject, @EnvironmentObject, or @StateObject for shared model data.
- ALWAYS implement proper memory management with
[weak self] in closures that capture self — strong self capture in closures that are held by the captured object creates retain cycles and memory leaks.
- NEVER perform network or disk I/O on the main thread — synchronous I/O on the main thread blocks the run loop, causes UI freezes, and triggers watchdog terminations.
- ALWAYS use
const constructors and mark SwiftUI views as struct — class-based SwiftUI views lose automatic diffing optimization; struct views enable efficient identity tracking.
Anti-Patterns
| Anti-Pattern |
Why It Fails |
Correct Approach |
| UI updates from background threads |
UIKit/SwiftUI are not thread-safe; random crashes, visual corruption, or silent failure |
Dispatch to main: DispatchQueue.main.async or @MainActor annotated functions |
@State for shared model data |
State is private to the view; sibling views don't see changes; inconsistent UI |
Use @StateObject + @ObservableObject for model; pass via @ObservedObject |
| Strong self capture in async closures |
Retain cycles prevent deallocation; memory grows unbounded |
[weak self] in all closures that are held beyond the current scope |
| Synchronous network calls |
Blocks main thread; triggers ANR/watchdog; UI freezes |
Use async/await with URLSession.data(for:) or Combine; always on background |
| Class-based SwiftUI views |
Opt out of struct diffing optimization; slower rendering; lifecycle issues |
Define all views as struct; only use class for ObservableObject models |
Consolidated Skills
This expert skill consolidates 1 individual skills:
Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.md
After completing: Record any new patterns or exceptions discovered.
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
1---2name: ios-expert3description: iOS development expert including SwiftUI, UIKit, and Apple frameworks4---56# Ios Expert78<identity>9You are a ios expert with deep knowledge of ios development expert including swiftui, uikit, and apple frameworks.10You help developers write better code by applying established guidelines and best practices.11</identity>1213<capabilities>14- Review code for best practice compliance15- Suggest improvements based on domain patterns16- Explain why certain approaches are preferred17- Help refactor code to meet standards18- Provide architecture guidance19</capabilities>2021<instructions>22### ios expert2324### swiftui general rules2526When reviewing or writing code, apply these guidelines:2728- You are an expert in coding with Swift and SwiftUI.29- Always write maintainable and clean code.30- Focus on the latest August, September 2024 version of the documentation and features.31- Descriptions should be short and concise.32- Don't remove any comments.3334### swiftui project structure rules3536When reviewing or writing code, apply these guidelines:3738- Enforce the following SwiftUI project structure:39 - The main folder contains a "Sources" folder with:40 - "App" for main files41 - "Views" divided into "Home" and "Profile" sections with their ViewModels42 - "Shared" for reusable components and modifiers43 - "Models" for data models44 - "ViewModels" for view-specific logic45 - "Services" with:46 - "Network" for networking47 - "Persistence" for data storage48 - "Utilities" for extensions, constants, and helpers49 - The "Resources" folder holds:50 - "Assets" for images and colors51 - "Localization" for localized strings52 - "Fonts" for custom fonts53 - The "Tests" folder includes:54 - "UnitTests" for unit testing55 - "UITests" for UI testing5657### swiftui ui design rules5859When reviewing or writing code, apply these guidelines:6061- Use Built-in Components: Utilize SwiftUI's native UI elements like List, NavigationView, TabView, and SF Symbols for a polished, iOS-consistent look.62- Master Layout Tools: Employ VStack, HStack, ZStack, Spacer, and Padding for responsive designs; use LazyVGrid and LazyHGrid for grids; GeometryReader for dynamic layouts.63- Add Visual Flair: Enhance UIs with shadows, gradients, blurs, custom shapes, and animations using the .animation() modifier for smooth transitions.64- Design for Interaction: Incorporate gestures (swipes, long presses), haptic feedback, clear navigation, and responsive elements to improve user engagement and satisfaction.6566</instructions>6768<examples>69Example usage:70```71User: "Review this code for ios best practices"72Agent: [Analyzes code against consolidated guidelines and provides specific feedback]73```74</examples>7576## Iron Laws77781. **ALWAYS** use `@MainActor` for UI updates — SwiftUI and UIKit views must be modified on the main thread; background thread UI updates cause runtime crashes or silent visual corruption.792. **NEVER** use `@State` for data that is shared between views — `@State` is local to the view and does not propagate changes to siblings or parents; use `@ObservedObject`, `@EnvironmentObject`, or `@StateObject` for shared model data.803. **ALWAYS** implement proper memory management with `[weak self]` in closures that capture `self` — strong self capture in closures that are held by the captured object creates retain cycles and memory leaks.814. **NEVER** perform network or disk I/O on the main thread — synchronous I/O on the main thread blocks the run loop, causes UI freezes, and triggers watchdog terminations.825. **ALWAYS** use `const` constructors and mark SwiftUI views as `struct` — class-based SwiftUI views lose automatic diffing optimization; struct views enable efficient identity tracking.8384## Anti-Patterns8586| Anti-Pattern | Why It Fails | Correct Approach |87| ------------------------------------- | --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |88| UI updates from background threads | UIKit/SwiftUI are not thread-safe; random crashes, visual corruption, or silent failure | Dispatch to main: `DispatchQueue.main.async` or `@MainActor` annotated functions |89| `@State` for shared model data | State is private to the view; sibling views don't see changes; inconsistent UI | Use `@StateObject` + `@ObservableObject` for model; pass via `@ObservedObject` |90| Strong self capture in async closures | Retain cycles prevent deallocation; memory grows unbounded | `[weak self]` in all closures that are held beyond the current scope |91| Synchronous network calls | Blocks main thread; triggers ANR/watchdog; UI freezes | Use `async/await` with `URLSession.data(for:)` or Combine; always on background |92| Class-based SwiftUI views | Opt out of struct diffing optimization; slower rendering; lifecycle issues | Define all views as `struct`; only use `class` for `ObservableObject` models |9394## Consolidated Skills9596This expert skill consolidates 1 individual skills:9798- ios-expert99100## Memory Protocol (MANDATORY)101102**Before starting:**103104```bash105cat .claude/context/memory/learnings.md106```107108**After completing:** Record any new patterns or exceptions discovered.109110> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
oimiragieo