Axiom Swiftui Nav Diag

What it does

This skill helps diagnose issues with SwiftUI navigation by identifying problems related to path state management, view identity, or placement errors—common causes of unexpected navigation behavior. It provides a systematic approach to pinpointing root causes in minutes rather than hours and discourages wrapping SwiftUI's NavigationStack in a UINavigationController, which can introduce more complexity. The skill guides users through specific checks and logging techniques to isolate the source of navigation problems within their code.

When to use it

• When navigation taps do nothing (links are present but don’t push).
• When the back button pops to the wrong screen or root.
• When deep links open the app but display an incorrect screen.
• When navigation state is lost when switching tabs or the app backgrounds.
• When a NavigationLink pushes twice unexpectedly.

Key capabilities

• Provides diagnostics for SwiftUI navigation issues.
• Identifies problems related to path state management, view identity, and placement errors.
• Offers specific checks using logging techniques (e.g., NavigationPath logging).
• Guides users through a structured troubleshooting process.
• Discourages wrapping NavigationStack in UINavigationController.

Example prompts

• "I'm having trouble with my SwiftUI navigation; can you help me diagnose the issue?"
• "My back button is taking me to the wrong screen. What should I check first?"
• "How do I debug a SwiftUI navigation problem related to path state management?"

Tips & gotchas

• Always start with the mandatory first steps: Implement NavigationPath logging, verify navigationDestination visibility, and confirm that NavigationLink is within a NavigationStack.
• State Location Matters: Ensure @State variables are located in stable views (not recreated on every render). They must be declared as @State, @StateObject, or @Observable.
• Isolate the Problem: Create a minimal, reproducible example to test basic navigation functionality.