Ios Navigation

This enforces a strict modular MVVM-C navigation pattern for SwiftUI apps on iOS 26 and Swift 6.2. It's built around coordinators owning NavigationPath, route shells handling destination mapping, and keeping feature modules isolated from each other through Domain protocol boundaries. You'll want this if you're building clinic-style modular apps where navigation logic lives in the app target, not scattered across feature modules. The big opinion here is coordinator-owned modal state and mandatory @Equatable on every navigation view with zero AnyView escapes. It also bakes in assumptions about stale-while-revalidate data flows and optimistic writes, so it's pretty specific to that architecture style. Good for teams that want navigation guardrails and don't mind the constraints.

skills.sh installs: 267
GitHub stars: 222
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pproenca/dot-skills --skill ios-navigation --agent claude-code

Installs into .claude/skills of the current project.

Files

iOS Navigation (Modular MVVM-C)

Opinionated navigation enforcement for SwiftUI apps using the clinic modular architecture. Focus on coordinator + route shell wiring, feature isolation, and resilient push/sheet/deep-link flows.

Non-Negotiable Constraints (iOS 26 / Swift 6.2)

@Equatable macro on every navigation view, AnyView never
@Observable everywhere, ObservableObject / @Published never
App-target coordinators own NavigationPath; route shells own .navigationDestination mappings
Coordinator-owned modal state, inline @State booleans for sheets never
Domain layer defines coordinator protocols; concrete coordinators stay out of feature modules