Leavn Navigation Debugger

VerifiedSafe

Debug navigation issues in Leavn: NotificationCenter routing, deep links, tab selection, AppCoordinator, and modal presentations. Use this skill when navigation is broken, wrong screen appears, deep links fail, or tab routing problems occur.

Sby Skills Guide Bot
DevelopmentIntermediate
906/2/2026
Claude Code
#navigation#debugging#leavn#notification-center#deep-links

Recommended for

Our review

This skill helps diagnose and fix navigation bugs in the Leavn app, including NotificationCenter routing, deep links, tab selection, AppCoordinator, and modal presentations.

Strengths

  • Systematic check of .onReceive() handlers
  • Analysis of NotificationCenter and AppCoordinator flow
  • Concrete instructions with Swift code examples

Limitations

  • Specific to Leavn architecture, not generalizable
  • Requires codebase knowledge to interpret logs
  • Does not cover performance or memory issues
When to use it

Use this skill when navigation is broken, wrong screens appear, deep links fail, or tab routing has issues.

When not to use it

Do not use for non-navigation bugs (business logic, API, static UI) or in apps other than Leavn.

Security analysis

Safe
Quality score78/100

No execution of external commands or dangerous operations; only static analysis and debugging advice within an app.

No concerns found

Examples

Debug deep link failure
The deep link 'leavn://open/book/Genesis/1' is not navigating to the Bible view. Debug the navigation using the navigation-debugger skill.
Fix tab selection bug
When tapping the 'Bible' tab, it navigates to the 'Journal' tab instead. Use the navigation-debugger to find the issue.

name: navigation-debugger description: Debug Leavn navigation issues - NotificationCenter routing, deep links, tab selection, AppCoordinator, modal presentations allowed-tools: Read, Edit, Grep disable-model-invocation: false context: fork user-invocable: true argument-hint: "[context]"

Navigation Debugger

Fix navigation bugs in Leavn:

  1. Check notification handling:

    • Search for notification name in ContentView
    • Verify .onReceive() handlers exist
    • Check AppCoordinator navigation methods
  2. Common Leavn patterns:

    // Post navigation
    NotificationCenter.default.post(
        name: .OpenBibleReference,
        userInfo: ["book": "Genesis", "chapter": 1]
    )
    
    // Handle in ContentView
    .onReceive(NotificationCenter.default.publisher(for: .OpenBibleReference)) {
        // Navigate to Bible
    }
    
  3. Debug steps:

    • Add AppLog in notification handlers
    • Verify userInfo parsing
    • Check tab selection works
    • Test deep link URLs

Use when: Navigation broken, wrong screen, deep links fail, tab routing issues

Related skills