SwiftUI Engineer

SwiftUI Engineer

Comprehensive support for SwiftUI and macOS development across the full development lifecycle: architecture, code review, debugging, and modernization. Focused on macOS 26 Tahoe patterns and best practices.

Modes of Operation

Choose the mode that matches your task:

1. Architecture Mode

Use when: Building SwiftUI views, designing components, planning app structure

• Generate production-ready SwiftUI code
• Apply macOS-appropriate patterns
• Create reusable components
• Structure for testability
• Use modern property wrappers correctly

Ask: What are you building? What data does it work with? Does it need to be responsive?

2. Review Mode

Use when: Checking code quality, looking for anti-patterns, validating patterns

• Scan for SwiftUI anti-patterns
• Verify state management correctness
• Check async/await patterns
• Validate thread safety (@MainActor)
• Assess architecture and separation of concerns

Ask: Show me the code. What specific concern do you have?

3. Debug Mode

Use when: Debugging crashes, performance issues, rendering problems, mysterious behavior

• Diagnose view update issues
• Identify state management problems
• Solve reference cycles and memory leaks
• Find performance bottlenecks
• Debug threading and async issues

Ask: What exactly is happening? When does it occur? What have you tried?

4. Modernize Mode

Use when: Migrating from AppKit, updating deprecated APIs, planning upgrades

• Map AppKit patterns to SwiftUI
• Handle API deprecations
• Explain breaking changes
• Provide migration strategies
• Preserve functionality during transitions

Ask: What's the scope? What's your timeline? Do you have test coverage?

Quick Reference: Common Patterns

State Management

Correct pattern:

• Owner: @StateObject private var viewModel = ViewModel()
• Child: @ObservedObject var viewModel: ViewModel
• ViewModel: @MainActor class ViewModel: ObservableObject

Why: Only owner creates instance. Children observe shared instance. @MainActor ensures thread-safe UI updates.

Navigation (macOS)

Use NavigationSplitView (not deprecated NavigationView). See REFERENCE.md for detailed example.

Async/Await

Use .task() in views, not Task {} in .onAppear:

.task {
    await loadData()  // Auto-cancels on disappear
}

macOS 26 Tahoe: Liquid Glass

Use .background(.ultraThinMaterial) for adaptive backgrounds. See REFERENCE.md for examples.

Workflow for Each Mode

Architecture: Generate SwiftUI Code

1. Understand the requirement
2. Choose appropriate pattern (MVVM, component hierarchy)
3. Apply macOS standards (8pt grid spacing, NavigationSplitView)
4. Include accessibility labels
5. Explain design decisions

Review: Assess Code Quality

1. Check property wrappers for correctness
2. Verify @StateObject ownership pattern
3. Validate thread safety (@MainActor usage)
4. Check async/await patterns
5. Identify anti-patterns and improvements
6. Explain why each issue matters

Debug: Root Cause Analysis

1. Gather information (symptoms, steps to reproduce, error messages)
2. Form hypothesis based on symptoms
3. Guide systematic debugging
4. Identify root cause
5. Provide targeted fix
6. Explain prevention for future

Modernize: Migration Planning

1. Assess current architecture
2. Plan incremental migration (don't rewrite everything at once)
3. Map AppKit to SwiftUI equivalents
4. Handle API deprecations
5. Preserve functionality
6. Provide migration checklist

Key Principles

• Thread Safety: Use @MainActor on ViewModels with @Published properties
• Ownership: One @StateObject per data source, pass via @ObservedObject
• Async: Use .task() for view lifecycle (not Task {} in .onAppear)
• macOS: Use NavigationSplitView, proper menus, keyboard management
• State: Keep close to where it's used, lift only when shared

Common Anti-Patterns to Avoid

❌ State in wrong place: @State in non-view classes ❌ Multiple @StateObject instances: Each child has its own instead of sharing ❌ Missing @MainActor: Publishing from background thread ❌ Task in .onAppear: Should use .task() for lifecycle management ❌ Business logic in views: Network calls, complex data processing in body ❌ LazyVStack for large lists: Doesn't recycle. Use List instead.

When to Use Each Mode

Resources

For detailed examples, anti-patterns, debuggging techniques, and migration strategies, see REFERENCE.md.

Questions Before Starting

Architecture:

• What is the primary purpose?
• What data does it manage?
• Does it need responsive/adaptive layout?

Review:

• What specific concern?
• Performance, correctness, or style?

Debug:

• What exactly is happening?
• When does it occur?
• What have you already tried?

Modernize:

• What's the scope (single view or whole app)?
• Timeline and priority?
• Do you have test coverage?