hotwire-native-path-config

Configure and debug URL path-configuration rules for Hotwire Native iOS and Android apps.

1|Updated Jan 8, 2026

Search Tags:#debugging #routing rules #path configuration #hotwire native #ios navigation #android deep links #modal presentation

Ready to run

npx skills add https://github.com/LaunchPadLab/ai-bank --skill hotwire-native-path-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hotwire-native-path-config
Source: https://github.com/LaunchPadLab/ai-bank/tree/main/claude/skills/hotwire-native-path-config
Command: npx skills add https://github.com/LaunchPadLab/ai-bank --skill hotwire-native-path-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves broken or confusing navigation behavior in Hotwire Native iOS/Android apps by helping you correctly configure and debug URL-to-screen routing using path-configuration rules.

Core Features & Use Cases

Consistent routing across platforms: Guides you to keep iOS and Android path configuration files aligned so screens behave the same way everywhere.
Rules-first debugging: Helps you diagnose modal vs push navigation, pull-to-refresh behavior, and unexpected destinations by reasoning about sequential rule matching and overrides.
Platform-specific correctness: Ensures Android deep-link rules include the required uri that maps to registered Fragments, while iOS rules use the right presentation properties.

Quick Start

Configure the correct sequential rules in all bundled/remote path configuration files for your Hotwire Native app (including Android uri mappings) so the target screen routes as the intended modal or navigation style.

Frequently Asked Questions about hotwire-native-path-config

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

FAQPage Schema

How do I fix incorrect screen routing and navigation presentation in Hotwire Native apps?▼

To fix Hotwire Native navigation, configure and debug URL path-configuration rules by ensuring sequential rule ordering, correct pattern matching, and platform-specific properties. This aligns routing behaviors across iOS and Android platforms.

Why does my Android deep link navigation crash in my Hotwire Native app?▼

Android deep-link navigation crashes occur when path-configuration rules omit the required `uri` property mapping URLs to registered Fragments. Adding the correct `uri` mapping resolves the crash and ensures proper deep-link routing.

How do I configure a modal presentation instead of a push navigation for a specific URL?▼

Configuring modal presentation requires adding a path-configuration rule with the correct iOS presentation or context properties for the target URL pattern. Rules are evaluated sequentially, so positioning determines the final navigation style.

Do I need to synchronize local bundled path-configuration files with remote configs in Hotwire Native?▼

Yes, you must keep bundled local path-configuration files synchronized with versioned remote configs. Synchronization ensures consistent routing behavior and prevents unexpected navigation discrepancies across app versions.

How do I diagnose pull-to-refresh issues using Hotwire Native path-configuration rules?▼

Diagnose pull-to-refresh issues by reasoning about sequential path-configuration rule matching and overrides. Incorrectly ordered rules or conflicting pattern matches can override intended behaviors, causing navigation or refresh anomalies.

What is the best way to keep iOS and Android path configuration aligned for Hotwire Native?▼

The best way to keep iOS and Android path configuration aligned is to review both path-configuration.json files together, ensuring platform-specific properties like Android `uri` and iOS presentation attributes match shared URL routing patterns.