app-routing

Configure React Router BrowserRouter for Fusebase Apps to fix broken navigation.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill app-routing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-routing
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/.agents/skills/app-routing
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill app-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about app-routing

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

FAQPage Schema
Why does client-side routing break with 404 errors after deploying my Fusebase App?▼

Client-side routing breaks because Fusebase Apps are served from subdomain roots, requiring path-based BrowserRouter configuration instead of HashRouter to prevent 404 errors post-deployment.

How do I fix navigation state loss following OAuth or SSO redirects in React Router?▼

To fix navigation state loss after OAuth redirects, implement React Router's BrowserRouter for path-based routing and use Link components for internal navigation to preserve state across redirects.

What is the best way to configure React Router for a multi-page Fusebase App?▼

The best way to configure React Router for a Fusebase App is enforcing path-based BrowserRouter, avoiding the reserved /api route prefix, and using Link components for internal navigation.

Does HashRouter work for Fusebase Apps deployed to dedicated subdomain roots?▼

HashRouter does not work correctly for Fusebase Apps because dedicated subdomain roots require path-based BrowserRouter implementation to maintain navigation state and avoid deployment 404 errors.

What are the limitations when defining routes for a Fusebase App?▼

Route limitations in Fusebase Apps include avoiding the reserved /api prefix, preventing hardcoded absolute paths, and strictly using React Router Link components instead of standard anchor tags for internal navigation.