What problem does it solve?
Fusebase Apps are served from dedicated subdomain roots, so incorrect routing configuration (such as using hash-based routing) breaks navigation, causes 404 errors post-deployment, and leads to lost user state during OAuth or SSO redirects.
Core Features & Use Cases
- Path-Based Routing Enforcement: Mandates use of React Router's BrowserRouter to preserve navigation state across redirects.
- Configuration Guidance: Provides ready-to-use setup examples for integrating React Router into Fusebase Apps.
- Pitfall Prevention: Flags common mistakes including hardcoded absolute paths, use of HashRouter, and defining routes under the reserved /api prefix.
- Use Case: When building a multi-page Fusebase App with user profiles and settings pages, this skill ensures routes function correctly after deployment and authentication flows.
Quick Start
Use the app-routing skill to configure correct path-based routing for your Fusebase App's pages and resolve broken navigation after OAuth redirects.