axiom-swiftui-nav-ref

Reference SwiftUI navigation APIs for NavigationStack, NavigationSplitView, and NavigationPath.

Updated Dec 23, 2025

Search Tags:#navigation #swiftui #coordinator #navigationstack #navigationsplitview #state-restoration #deeplinking

Ready to run

npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-swiftui-nav-ref-pradeepmouli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: axiom-swiftui-nav-ref
Source: https://github.com/pradeepmouli/swift-template/tree/main/.agents/skills/axiom-swiftui-nav-ref
Command: npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-swiftui-nav-ref-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SwiftUI navigation can be complex across NavigationStack, NavigationSplitView, and multi-column layouts. This reference consolidates APIs, patterns, and guidance to help developers design robust, data-driven navigation flows across iOS variants and feature sets.

Core Features & Use Cases

Comprehensive API reference for NavigationStack, NavigationSplitView, NavigationPath, and deep linking
Practical patterns for per-tab navigation state, coordinators, and state restoration
Use cases spanning iOS 16–26, including multi-column layouts, deep links, and migration notes

Quick Start

Start with a basic NavigationStack and progressively add destinations, deep links, and a split-view detail column as your app grows.

Frequently Asked Questions about axiom-swiftui-nav-ref

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage state restoration with NavigationStack in SwiftUI?▼

SwiftUI state restoration in NavigationStack requires data-driven NavigationPath management to serialize and restore navigation history. This reference provides practical patterns for persisting navigation state across iOS 16–26 app lifecycle transitions.

What is the best way to implement deep linking with NavigationSplitView?▼

Deep linking with NavigationSplitView involves binding URL inputs to your NavigationPath to programmatically drive column selections and detail destinations. This reference explains how to synchronize multi-column layouts with incoming deep link requests.

Can I maintain separate navigation state for each tab in SwiftUI?▼

Yes, you can maintain per-tab navigation state by isolating NavigationStack instances within each tab view. This reference details coordinator patterns to keep tab-specific NavigationPath data independent across your app.

How do I migrate from NavigationView to NavigationStack and NavigationSplitView?▼

Migrating from NavigationView to NavigationStack and NavigationSplitView requires replacing deprecated APIs with data-driven path bindings. This reference includes migration notes covering structural changes needed for iOS 16 and later.

Why does my SwiftUI NavigationPath drop destinations when deep linking programmatically?▼

NavigationPath drops destinations when the data type bindings do not match your declared navigation destinations. This reference outlines how to correctly structure data-driven navigation flows to avoid state loss during programmatic pushes.

Does this SwiftUI navigation reference cover multi-column layouts on iPadOS?▼

Yes, this reference covers NavigationSplitView multi-column layouts and per-tab navigation patterns across iOS 16–26. It provides structured API explanations for building robust data-driven navigation flows on iPadOS.