Slash Command

/navigation

Enforces SwiftUI navigation best practices: prefers NavigationStack/SplitView over deprecated NavigationView, navigationDestination; optimizes alerts, sheets, and confirmation dialogs.

Swift

iOS

mobile

code-quality

npx claudepluginhub fradser/dotclaude --plugin swiftui

Details

Namespaceswiftui-review/references/

Prompt Preview

# Navigation and presentation

- Use `NavigationStack` or `NavigationSplitView` as appropriate; flag all use of the deprecated `NavigationView`.
- Strongly prefer to use `navigationDestination(for:)` to specify destinations; flag all use of the old `NavigationLink(destination:)` pattern where it should be replaced.
- Never mix `navigationDestination(for:)` and `NavigationLink(destination:)` in the same navigation hierarchy; it causes significant problems.
- `navigationDestination(for:)` must be registered once per data type; flag duplicates.


## Alerts, confirmation dialogs, and sheets

- ...

Command Content

Other plugins with /navigation

/create-view

1.0k

Generates a SwiftUI view file with MVVM architecture, property wrappers, layouts, navigation elements, states, accessibility, dark mode support, previews, and documentation.

ios-developer

/audit

717

Analyzes iOS/Swift projects to suggest relevant audits or runs specified ones (e.g., memory, concurrency, accessibility, SwiftUI performance, security).

axiom

/convert

Convert Claude-generated HTML design from URL or tarball path into SwiftUI View file in active Xcode workspace, with build, error fix, and preview diff.

8 tools

claudedesign-to-swiftui

Stats

Parent Repo Stars545

Parent Repo Forks44

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Navigation and presentation - Use `NavigationStack` or `NavigationSplitView` as appropriate; flag all use of the deprecated `NavigationView`. - Strongly prefer to use `navigationDestination(for:)` to specify destinations; flag all use of the old `NavigationLink(destination:)` pattern where it should be replaced. - Never mix `navigationDestination(for:)` and `NavigationLink(destination:)` in the same navigation hierarchy; it causes significant problems. - `navigationDestination(for:)` must be registered once per data type; flag duplicates. ## Alerts, confirmation dialogs, and sheets - ...

Navigation and presentation

Use NavigationStack or NavigationSplitView as appropriate; flag all use of the deprecated NavigationView.

Strongly prefer to use navigationDestination(for:) to specify destinations; flag all use of the old NavigationLink(destination:) pattern where it should be replaced.

Never mix navigationDestination(for:) and NavigationLink(destination:) in the same navigation hierarchy; it causes significant problems.

navigationDestination(for:) must be registered once per data type; flag duplicates.

Alerts, confirmation dialogs, and sheets

Always attach confirmationDialog() to the user interface that triggers the dialog. This allows Liquid Glass animations to move from the correct source.

If an alert has only a single “OK” button that does nothing but dismiss the alert, it can be omitted entirely: .alert("Dismiss Me", isPresented: $isShowingAlert) { }.

If a sheet is designed to present an optional piece of data, prefer sheet(item:) over sheet(isPresented:) so the optional is safely unwrapped.

When using sheet(item:) with a view that accepts the item as its only initializer parameter, prefer sheet(item: $someItem, content: SomeView.init) over sheet(item: $someItem) { someItem in SomeView(item: someItem) }.

Navigation and presentation

Use NavigationStack or NavigationSplitView as appropriate; flag all use of the deprecated NavigationView.
Strongly prefer to use navigationDestination(for:) to specify destinations; flag all use of the old NavigationLink(destination:) pattern where it should be replaced.
Never mix navigationDestination(for:) and NavigationLink(destination:) in the same navigation hierarchy; it causes significant problems.
navigationDestination(for:) must be registered once per data type; flag duplicates.

Alerts, confirmation dialogs, and sheets

Always attach confirmationDialog() to the user interface that triggers the dialog. This allows Liquid Glass animations to move from the correct source.
If an alert has only a single “OK” button that does nothing but dismiss the alert, it can be omitted entirely: .alert("Dismiss Me", isPresented: $isShowingAlert) { }.
If a sheet is designed to present an optional piece of data, prefer sheet(item:) over sheet(isPresented:) so the optional is safely unwrapped.
When using sheet(item:) with a view that accepts the item as its only initializer parameter, prefer sheet(item: $someItem, content: SomeView.init) over sheet(item: $someItem) { someItem in SomeView(item: someItem) }.