add-new-screen

To add a new SwiftUI screen with proper navigation, scaffold a view under your project's Views directory, integrate Environment(AppState) for state management, and use NavigationStack to wire the screen into the main navigation flow.

Implementing navigation for different SwiftUI screen types requires a multi-path flow strategy. You can route users through Settings sub-screens, push detail screens from a list, or present modal sheets using NavigationStack and project-specific router conventions.

Environment(AppState) provides shared state access when creating a new SwiftUI screen. Injecting AppState into your view environment ensures the new screen observes and reacts to global state changes following the project's MVVM architecture.

Yes, you can use NavigationStack to wire both modal and detail screens in SwiftUI. NavigationStack manages hierarchical navigation for detail screens, while modal flows can be presented independently within the same architectural pattern.

You need to create a separate view file under the Views directory in a SwiftUI app whenever adding a distinct screen like a Settings sub-screen or a detail view. This maintains project organization and adheres to MVVM file structure conventions.

A new SwiftUI screen might not follow file organization if it is placed outside the designated Views directory. Adhering to project conventions by placing files under VivaDicta/Views ensures proper navigation integration and architectural consistency.