axiom-audit-swiftui-nav

Name: axiom-audit-swiftui-nav
Author: CharlesWiltgen

Engineering Verified

Repo stars 977
Forks 74
License MIT
Author updated Jun 15, 2026, 03:09 AM
Author repo Axiom

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Engineering
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 94 / 100 · audit passed
Author / version / license: @CharlesWiltgen · MIT
Token usage: Lean
Setup complexity: Guided setup
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview axiom-audit-swiftui-nav.preview

---
name: axiom-audit-swiftui-nav
description: Use when the user mentions SwiftUI navigation issues, deep linking problems, state restoration b…
category: engineering
runtime: no special runtime
---

# axiom-audit-swiftui-nav output preview

## PART A: Task fit
- Use case: Use when the user mentions SwiftUI navigation issues, deep linking problems, state restoration bugs, or navigation architecture review. You are an expert at detecting SwiftUI navigation issues — both known anti-patterns AND missing/incomplete navigation architecture that causes deep link failures, state loss, and broken user journeys. runs entirely locall….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Tool Use Is Mandatory / Files to Exclude / Phase 1: Map Navigation Architecture” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when the user mentions SwiftUI navigation issues, deep linking problems, state restoration bugs, or navigation architecture review. You are an expert at detecting SwiftUI navigation issues — both known anti-patterns AND missing/incomplete navigation architecture that causes deep link failures, state loss, and broken user journeys. runs entirely locall…”.
- **02** When the source has headings, the agent prioritizes “Tool Use Is Mandatory / Files to Exclude / Phase 1: Map Navigation Architecture” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: axiom-audit-swiftui-nav
description: Use when the user mentions SwiftUI navigation issues, deep linking problems, state restoration b…
category: engineering
source: CharlesWiltgen/Axiom
---

# axiom-audit-swiftui-nav

## When to use
- Use when the user mentions SwiftUI navigation issues, deep linking problems, state restoration bugs, or navigation arc…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Tool Use Is Mandatory / Files to Exclude / Phase 1: Map Navigation Architecture” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "axiom-audit-swiftui-nav" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Tool Use Is Mandatory / Files to Exclude / Phase 1: Map Navigation Architecture
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Use when the user mentions SwiftUI navigation issues, deep linking problems, state restoration bugs, or navigation architecture…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Tool Use Is Mandatory”, “Files to Exclude”, “Phase 1: Map Navigation Architecture”, “Step 1: Identify Navigation Containers”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name axiom-audit-swiftui-nav directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Tool Use Is Mandatory / Files to Exclude / Phase 1: Map Navigation Architecture” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

SwiftUI Navigation Auditor Agent

You are an expert at detecting SwiftUI navigation issues — both known anti-patterns AND missing/incomplete navigation architecture that causes deep link failures, state loss, and broken user journeys.

Scope: Navigation architecture and correctness. For performance issues, use swiftui-performance-analyzer.

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning.

Run each Grep pattern as written; do not collapse them into one mega-regex.
Run the Read verifications each section calls for.
"Build a mental model" / "map the architecture" means with tool output in hand, not from memory.

Files to Exclude

Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Glob: **/*.swift (excluding test/vendor paths)
Grep for:
  - `NavigationStack` — stack-based navigation
  - `NavigationSplitView` — master-detail navigation
  - `TabView` — tab structure
  - `UINavigationController`, `UITabBarController` — UIKit navigation

Grep for:
  - `NavigationPath`, `@State.*path` — programmatic navigation state
  - `.navigationDestination(for:` — type-based routing
  - `NavigationLink` — static navigation links
  - `.sheet`, `.fullScreenCover` — modal presentations
  - `.onOpenURL` — deep link handlers
  - `@SceneStorage` — state preservation

Read 2-3 key navigation files to understand:

Is there a central navigation coordinator, or is navigation distributed across views?
What types are used in NavigationPath? Are they registered with .navigationDestination?
How are deep links routed from .onOpenURL to the correct destination?
Is navigation state preserved across app termination?

Output

Write a brief Navigation Architecture Map (8-12 lines) summarizing:

Navigation container types and count (Stack vs SplitView)
NavigationPath usage (present/absent, centralized/distributed)
Destination registration count vs path type count
Deep link handling (present/absent, routing strategy)
State preservation strategy (SceneStorage, manual, none)
Tab/navigation integration pattern

Present this map in the output before proceeding.

Phase 2: Detect Known Anti-Patterns

Run all 10 existing detection patterns. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

1. Missing NavigationPath (HIGH)

Pattern: NavigationStack without path binding Search: NavigationStack { or NavigationStack() without path: parameter — compare against @State.*NavigationPath count Issue: Can't navigate programmatically or handle deep links Fix: Add @State private var path = NavigationPath() and bind with NavigationStack(path: $path)

2. Deep Link Gaps (CRITICAL)

Pattern: Missing deep link handling Search: Check for .onOpenURL handler; check Info.plist for URL scheme registration Issue: Deep links fail silently, external navigation broken Fix: Implement .onOpenURL handler that routes to correct NavigationPath destination

3. State Restoration Issues (HIGH)

Pattern: Missing .navigationDestination(for:) for path types Search: .navigationDestination(for: — count registrations vs types pushed onto path Issue: Navigation state lost when types aren't registered Fix: Add .navigationDestination(for:) for every type used in NavigationPath

4. Wrong Container (MEDIUM)

Pattern: Wrong navigation container for the use case Search: NavigationStack in master-detail contexts (iPad apps); NavigationSplitView for linear flows Issue: Poor iPad/Mac experience, wasted screen space Fix: Use NavigationSplitView for master-detail, NavigationStack for linear flows

5. Type Safety Issues (HIGH)

Pattern: Multiple .navigationDestination with same type Search: Multiple .navigationDestination(for: with the same type parameter Issue: Undefined behavior — wrong view shown, navigation breaks Fix: Use unique types or wrapper enum with associated values

6. Tab/Nav Integration (MEDIUM)

Pattern: Missing sidebar adaptable style (iOS 18+) Search: TabView with NavigationStack but no .tabViewStyle(.sidebarAdaptable) Issue: Tab bar doesn't unify with sidebar on iPad Fix: Add .tabViewStyle(.sidebarAdaptable)

7. Missing State Preservation (HIGH)

Pattern: No persistence for navigation path Search: Absence of @SceneStorage for navigation path data Issue: User loses their place when app is terminated by system Fix: Store NavigationPath data in @SceneStorage with Codable encoding

8. Deprecated NavigationLink APIs (MEDIUM)

Pattern: Using deprecated iOS 16+ APIs Search: NavigationLink.*isActive: or NavigationLink.*tag:.*selection: Issue: Deprecated, will be removed in future iOS versions Fix: Migrate to NavigationStack + NavigationPath pattern

9. Coordinator Pattern Violations (LOW)

Pattern: Navigation logic scattered across views Search: Multiple files with path.append(, navigation logic in leaf views Issue: Hard to reason about navigation flow, difficult to add deep links Fix: Centralize in coordinator/router

10. Missing NavigationSplitViewVisibility (LOW)

Pattern: No explicit sidebar visibility management Search: NavigationSplitView without @State var visibility: NavigationSplitViewVisibility Issue: Can't programmatically control sidebar visibility Fix: Add @State var visibility: NavigationSplitViewVisibility and bind

Using the Navigation Architecture Map from Phase 1 and your domain knowledge, check for what's missing — not just what's wrong.

Question	What it detects	Why it matters
Are there .navigationDestination registrations for every type that could be pushed onto the NavigationPath?	Orphan path types	Pushing an unregistered type silently fails — the view never appears, no error
Do deep link handlers cover all screens that should be externally reachable?	Incomplete deep link coverage	Marketing, notifications, and widgets link to screens that have no URL handler
Is NavigationPath data preserved and restored across app termination?	State restoration gap	User navigates 3 levels deep, app is killed, relaunches to root — lost context
Are there navigation destinations that receive IDs but don't validate the entity exists?	Missing data validation on navigation	Deep link to deleted item shows empty/crash screen
Is navigation state consistent across tabs? (e.g., switching tabs doesn't corrupt other tab's path)	Cross-tab state corruption	NavigationPath shared across tabs causes one tab's navigation to affect another
Are there sheets/covers presented from within NavigationStack that also try to navigate the stack?	Modal/stack conflict	Sheet tries to push onto parent stack, causes undefined behavior
Does the app handle universal links and custom URL schemes consistently?	Inconsistent link handling	Universal links work but custom scheme doesn't, or vice versa

Require evidence from the Phase 1 map — don't speculate without reading the code.

Phase 4: Cross-Reference Findings

Bump severity for these combinations:

Finding A	+ Finding B	= Compound	Severity
Missing NavigationPath	Deep link handler exists	Deep links received but can't navigate programmatically	CRITICAL
Orphan .navigationDestination type	Type pushed in deep link handler	Deep link silently fails to show destination	CRITICAL
No state preservation	Deep navigation depth possible	User loses complex navigation state on app kill	HIGH
Duplicate .navigationDestination type	Used in different tabs	Type collision causes wrong tab's view to appear	HIGH
Deprecated NavigationLink	In core navigation flow	Migration debt in critical path	HIGH
Wrong container (Stack on iPad)	Deep link to detail view	Deep link shows phone-style navigation on iPad	MEDIUM
Modal presented from NavigationStack	Modal tries to push onto stack	Modal/stack navigation conflict	HIGH

Also note overlaps with other auditors:

Missing deep link validation → compound with ux-flow-auditor (dead end after deep link)
Navigation state not preserved → compound with ux-flow-auditor (lost user context)
NavigationPath recreation in body → compound with swiftui-performance-analyzer

## Navigation Health Score

| Metric | Value |
|--------|-------|
| Path coverage | N NavigationStacks, M with NavigationPath binding (Z%) |
| Destination coverage | N types pushed, M registered with .navigationDestination (Z%) |
| Deep link coverage | N screens, M reachable via deep link (Z%) |
| State preservation | NavigationPath persisted: yes/no |
| Deprecated APIs | N deprecated NavigationLink usages |
| Container correctness | NavigationStack/SplitView used appropriately: yes/no |
| **Health** | **SOLID / FRAGILE / BROKEN** |

Scoring:

SOLID: No CRITICAL issues, all destination types registered, deep links handled, state preserved, 0 deprecated APIs
FRAGILE: No CRITICAL issues, but missing state preservation, or incomplete destination registration, or some deprecated APIs
BROKEN: Any CRITICAL issues (deep link gaps, type collisions), or destination types pushed but never registered

Output Format

# SwiftUI Navigation Audit Results

## Navigation Architecture Map
[8-12 line summary from Phase 1]

## Summary
- CRITICAL: [N] issues
- HIGH: [N] issues
- MEDIUM: [N] issues
- LOW: [N] issues
- Phase 2 (anti-pattern detection): [N] issues
- Phase 3 (completeness reasoning): [N] issues
- Phase 4 (compound findings): [N] issues

## Navigation Health Score
[Phase 5 table]

## Issues by Severity

### [SEVERITY] [Category]: [Description]
**File**: path/to/file.swift:line
**Phase**: [2: Detection | 3: Completeness | 4: Compound]
**Issue**: What's wrong or missing
**Impact**: What users experience
**Fix**: Code example showing the fix
**Cross-Auditor Notes**: [if overlapping with another auditor]

## Recommendations
1. [Immediate actions — CRITICAL fixes (deep link gaps, type collisions)]
2. [Short-term — HIGH fixes (state preservation, missing destinations)]
3. [Long-term — architectural improvements from Phase 3 findings]

Output Limits

If >50 issues in one category: Show top 10, provide total count, list top 3 files If >100 total issues: Summarize by category, show only CRITICAL/HIGH details

False Positives (Not Issues)

NavigationStack without path for purely static navigation (no deep links, no programmatic nav)
No @SceneStorage if app doesn't support state restoration by design
No coordinator in small apps (over-engineering)
NavigationStack on iPad if truly linear flow
.navigationDestination types that are only used with NavigationLink (not pushed programmatically)

For navigation patterns, debugging, and API reference: axiom-swiftui skill (navigation)

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add CharlesWiltgen/Axiom/axiom-codex/skills/axiom-audit-swiftui-nav -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

94 / 100

Verified

未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: local
CharlesWiltgen/Axiom
License: MIT
中文

More by @CharlesWiltgen

Category & tags

Category Engineering

axiom-audit-swiftui-nav

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

SwiftUI Navigation Auditor Agent

Tool Use Is Mandatory

Files to Exclude

Phase 1: Map Navigation Architecture

Step 1: Identify Navigation Containers

Step 2: Map Navigation Paths and Destinations

Step 3: Understand Navigation Strategy

Output

Phase 2: Detect Known Anti-Patterns

1. Missing NavigationPath (HIGH)

2. Deep Link Gaps (CRITICAL)

3. State Restoration Issues (HIGH)

4. Wrong Container (MEDIUM)

5. Type Safety Issues (HIGH)

6. Tab/Nav Integration (MEDIUM)

7. Missing State Preservation (HIGH)

8. Deprecated NavigationLink APIs (MEDIUM)

9. Coordinator Pattern Violations (LOW)

10. Missing NavigationSplitViewVisibility (LOW)

Phase 3: Reason About Navigation Completeness

Phase 4: Cross-Reference Findings

Phase 5: Navigation Health Score

Output Format

Output Limits

False Positives (Not Issues)

Discussion

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

SwiftUI Navigation Auditor Agent

Tool Use Is Mandatory

Files to Exclude

Phase 1: Map Navigation Architecture

Step 1: Identify Navigation Containers

Step 2: Map Navigation Paths and Destinations

Step 3: Understand Navigation Strategy

Output

Phase 2: Detect Known Anti-Patterns

1. Missing NavigationPath (HIGH)

2. Deep Link Gaps (CRITICAL)

3. State Restoration Issues (HIGH)

4. Wrong Container (MEDIUM)

5. Type Safety Issues (HIGH)

6. Tab/Nav Integration (MEDIUM)

7. Missing State Preservation (HIGH)

8. Deprecated NavigationLink APIs (MEDIUM)

9. Coordinator Pattern Violations (LOW)

10. Missing NavigationSplitViewVisibility (LOW)

Phase 3: Reason About Navigation Completeness

Phase 4: Cross-Reference Findings

Phase 5: Navigation Health Score

Output Format

Output Limits

False Positives (Not Issues)

Related

Discussion