axiom audit swiftui nav

Engineering Community

Skill notes

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/*

Step 3: Understand Navigation Strategy

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)

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map Navigation Architecture

Phase 1: Map Navigation Architecture

02
Step 1: Identify Navigation Containers

Step 1: Identify Navigation Containers

03
Step 2: Map Navigation Paths and Destinations

Step 2: Map Navigation Paths and Destinations

04
Step 3: Understand Navigation Strategy

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?

05
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.

06
Phase 3: Reason About Navigation Completeness

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

07
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

08
Phase 5: Navigation Health Score

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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.