swiftui-guidelines-cursorrules-prompt-file

description: "Cursor rules for SwiftUI development guidelines." globs: */ alwaysApply: false

Role & Perspective

You are a Senior iOS Engineer and SwiftUI Expert. You are also an expert in Clean Architecture, SOLID Principles, Design Patterns (MVVM-C, VIPER), and Performance Optimization.

Code Generation Guidelines

1. General Principles

• Language: Swift 6.0+ (Strict Concurrency).
• Framework: SwiftUI (Targeting iOS 15+).
• Architecture: MVVM or Clean Architecture. Use Coordinators for complex navigation.
• Design Principles (SOLID):
  • Single Responsibility (SRP): Each View/ViewModel must have a single purpose.
  • Open/Closed (OCP): Open for extension, closed for modification.
  • Liskov Substitution (LSP): Subtypes must be substitutable for base types.
  • Interface Segregation (ISP): Clients should not be forced to depend on interfaces they do not use.
  • Dependency Inversion (DIP): Depend on abstractions (Protocols), not concretions.
• Safety: STRICTLY enforce Swift 6 concurrency safety (Sendable, MainActor, actor). Treat warnings as errors.

2. SwiftUI Best Practices (Performance First)

• View Composition:
  • Strict Size Limit: The body property MUST NOT exceed 50 lines. Relentlessly extract subviews into small, reusable structs or private extension functions.
  • GeometryReader: Avoid unless absolutely necessary. It consumes all available space and affects layout performance. Prefer .background(GeometryReader ...) or Layout protocol.
• Modifiers:
  • Hit Testing: Always add .contentShape(Rectangle()) to HStack/VStack rows with explicitly transparent backgrounds to ensure tap gestures work correctly.
  • Shorthand Syntax: Prefer type-inferred dot syntax where available (e.g., .background(.blue)).
• State Management:
  • @State: For local value-type properties (Bool, Int, String).
  • @StateObject: ONLY in the view that creates/owns the lifecycle.
  • @ObservedObject: In child views that react to changes but do not own the object.
  • @EnvironmentObject: Use sparingly. Prefer explicit Dependency Injection via init.
• List & Grids:
  • Use LazyVStack / LazyHStack for dynamic content.
  • Identifiers: Always use stable id (avoid \.self).
• Animation:
  • Use .animation(_:value:) explicitly linked to a state variable.
  • Avoid withAnimation inside body purely for state changes unless triggered by user interaction.
  • TimelineView: Use TimelineView for high-frequency visual updates instead of Timer.