axiom-deep-link-debugging

Route iOS simulator navigation to specific screens via debug URL schemes.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-deep-link-debugging-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-deep-link-debugging
Source: https://github.com/pradeepmouli/swift-template/tree/main/.agents/skills/axiom-deep-link-debugging
Command: npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-deep-link-debugging-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug deep links provide a controlled way to navigate an iOS app in a simulator or test environment, enabling closed-loop debugging without production deep link implementations.

Core Features & Use Cases

  • Pattern-based debug URL schemes that route to specific screens or states
  • Integration with existing navigation flows to avoid duplicating routing logic
  • State configuration links for testing error, empty, and advanced scenarios
  • Info.plist configuration that registers the debug URL scheme only in debug builds
  • Simulator testing workflows with /axiom:screenshot and simulator-tester integrations

Quick Start

Define your debug URL patterns, wrap code in #if DEBUG, register the debug URL scheme, and test each link in the simulator.

Frequently Asked Questions about axiom-deep-link-debugging

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

FAQPage Schema
How do I debug deep links for iOS simulator testing?

Debug deep links route iOS simulator apps to specific screens via a debug URL scheme registered in Info.plist. You wrap code in #if DEBUG and integrate with existing navigation to enable closed-loop testing without production links.

What is a debug URL scheme and how does it work in iOS?

A debug URL scheme is a custom routing pattern registered in Info.plist for debug builds only. It applies pattern-based URLs to navigate specific app screens, allowing state configuration for testing error or empty scenarios without affecting production.

Can I test error and empty states using deep links in an iOS simulator?

Yes, state configuration deep links route iOS apps to error, empty, and advanced scenarios. By applying debug URL patterns integrated with existing navigation, you test specific screen states during simulator-based closed-loop debugging.

Do I need to duplicate routing logic to test deep links in iOS?

No, debug deep linking integrates with your existing navigation system to avoid duplicating routing logic. You define debug URL patterns and wrap them in #if DEBUG, leveraging current navigation flows for simulator testing.

How do I keep debug deep link code out of production iOS builds?

Wrap debug deep link code in #if DEBUG and register the debug URL scheme in Info.plist exclusively for debug builds. This ensures deep link routing patterns and state configurations remain isolated from production environments.

What's the best way to automate screenshot verification across iOS app screens?

Use debug deep links with simulator testing workflows and /axiom:screenshot integrations. By routing to specific screens via debug URL patterns, you achieve automated closed-loop screenshot verification across settings, profile, and detail views.