ios-navigation

Enforce SwiftUI navigation patterns for iOS 26 modular MVVM-C apps.

193|17|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/pproenca/dot-skills --skill ios-navigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-navigation
Source: https://github.com/pproenca/dot-skills/tree/main/skills/.experimental/ios-navigation
Command: npx skills add https://github.com/pproenca/dot-skills --skill ios-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive set of rules and best practices for implementing navigation in SwiftUI applications, specifically targeting iOS 26 and Swift 6.2, with a focus on the clinic modular MVVM-C architecture. It aims to enforce consistency, prevent common anti-patterns, and ensure a high-quality, maintainable, and accessible navigation experience.

Core Features & Use Cases

  • Architecture Enforcement: Guides the implementation of navigation using NavigationStack, NavigationSplitView, and coordinator patterns.
  • Best Practices: Details rules for animations, modal presentations, flow orchestration, accessibility, and state restoration.
  • Modular Design: Aligns with the clinic modular MVVM-C architecture, emphasizing feature isolation and clear separation of concerns.
  • Use Case: When designing or refactoring the navigation flows for a new feature in a SwiftUI application built with the clinic modular MVVM-C architecture, use this Skill to ensure all navigation elements adhere to the defined constraints and best practices.

Quick Start

Use the ios-navigation skill to review the current navigation implementation for adherence to modular MVVM-C principles.

Frequently Asked Questions about ios-navigation

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

FAQPage Schema
What is the best way to implement SwiftUI navigation in a modular MVVM-C architecture?

SwiftUI navigation in a modular MVVM-C architecture is implemented using NavigationStack and NavigationSplitView alongside coordinator protocols to enforce feature isolation, flow orchestration, and separation of concerns.

How do I manage state restoration and flow orchestration in SwiftUI?

State restoration and flow orchestration in SwiftUI are managed by applying opinionated architectural constraints and utilizing @Observable state management within coordinator patterns to maintain consistent navigation paths.

Does this navigation approach support iOS 26 and Swift 6.2?

Yes, this navigation approach explicitly targets iOS 26 and Swift 6.2, enforcing architectural constraints and best practices specifically designed for the latest SwiftUI frameworks and modular MVVM-C applications.

What anti-patterns should I avoid when building SwiftUI navigation flows?

When building SwiftUI navigation flows, you should avoid anti-patterns that violate modular MVVM-C constraints, such as breaking feature isolation, mismanaging @Observable state, or bypassing coordinator protocols for transitions and modal presentations.

How do I handle modal presentations and transitions in a SwiftUI MVVM-C app?

Modal presentations and transitions in a SwiftUI MVVM-C app are handled through defined flow orchestration rules and coordinator protocols, ensuring animations and presentations adhere to strict architectural constraints.