swiftui-app-architecture-workflow

What problem does it solve?

Provide a docs-first workflow to decide where responsibilities belong in a SwiftUI app and which data-flow mechanisms to use so app structure remains maintainable and platform-correct. It helps teams and maintainers correct wrapper-heavy designs, eliminate state scattering, and avoid environment- or preference-key abuse that obscures ownership.

Core Features & Use Cases

• Ownership Boundary Selection: Recommend whether a responsibility belongs at the App, Scene, focused-scene, view-tree, or local-view boundary.
• Transport Recommendation: Choose between explicit initializer injection, Binding, environment values, FocusState, focused values/objects, focused scene values/objects, preference keys, or local state.
• Anti-Pattern Detection and Corrections: Detect environment dumping grounds, giant root views, wrapper-heavy layers, hidden modifier control flow, and preference-keys-as-state-bus; propose corrective refactors.
• Commands, Focus, and Scene Coordination: Advise on command ownership, focused-context publication, and native scene actions for settings and windows.
• Use Case: Refactor a single giant App root view into scene-local state, move inspector state into a UtilityWindow, or choose focused-scene publication for command-sensitive editor context.

Quick Start

Help me decide app versus scene ownership and the appropriate data-flow transport for a SwiftUI app with multiple windows, commands, and focused editors.