swiftui-feature-implementation

To implement standard SwiftUI pages with @Observable and @Bindable, provide a clearly defined page structure, routing, and state ownership. The Skill then converts these definitions into stable SwiftUI code that adheres to modern iOS 17+ architecture conventions.

The best way to build SwiftUI forms and lists within an existing state-management setup is to apply established architecture patterns. This approach enforces clean separation of UI and logic while integrating with the existing router for predictable navigation and data flow.

Yes, you can use this to generate new Swift files with proper Created by metadata for iOS 17+. It requires new Swift files with proper metadata and enforces modern APIs like @Observable and @Bindable for clean state management.

Yes, the SwiftUI implementation routes project changes to the verify-ios-build workflow. This ensures that generated views, components, and interactions are verified for stability within the established routing and state-management architecture.

Separate UI and logic when implementing SwiftUI detail views and interactions by using iOS 17+ patterns like @Observable, @State, and @Bindable. These patterns maintain clean separation while supporting common view structures within established architecture.