macos-development-workflow

Structure macOS SwiftUI apps using NavigationSplitView for multi-pane desktop UIs and SwiftData with @Observable for state management. This enforces native window management, toolbars, and menu commands while prohibiting legacy patterns like AppKit and Core Data.

Enforce SwiftUI quality gates through phase-based management with a five-agent team pattern. Apply precommit checks and phase gates to ensure reliable delivery, architectural consistency, and performance baselines across async/await concurrency patterns.

No, a modern macOS SwiftUI workflow prohibits AppKit, Core Data, and Combine. It strictly requires SwiftUI, SwiftData, @Observable, and async/await to prevent architectural drift and standardize desktop development.

Phase management governs macOS SwiftData development through a five-agent team pattern with quality gates. Start at Phase 0, execute precommit checks before every commit, and pass architectural decision records before advancing phases.

Yes, async/await and @Observable are required for macOS desktop app development within this workflow. They replace legacy concurrency and state management patterns, ensuring SwiftData integration aligns with modern SwiftUI conventions.

Avoid Combine and Core Data to prevent architectural drift and reduce onboarding time. SwiftData and @Observable provide modern, integrated state management directly compatible with SwiftUI, eliminating redundant reactive frameworks.