routing-navigation-design

What problem does it solve?

It prevents broken or insecure navigation flows by specifying route guards, redirect rules, deep-link loading states, and browser history behavior for every changed URL.

Core Features & Use Cases

• Guard classification contract: Defines unauthenticated vs unauthorized vs unavailable vs not-found outcomes with explicit resource-existence disclosure policy.
• Loop-free redirect and returnTo safety: Limits redirect depth, preserves return destinations across auth flows, and requires same-origin validation to mitigate open redirects.
• Deep-link state recovery: Ensures direct-entry URLs implement loading, success, permission-denied, deleted/archived recovery, and never-existed 404 handling.
• Route-table parameter validation: Requires strict, routing-layer validation for path parameters before any data fetch begins.
• History discipline for back-button resilience: Specifies push vs replace semantics to avoid resubmission traps and dead-state wizard navigation.
• Route-level error boundary scope: Contains failures within affected subtrees so partial 404s or nested errors do not collapse the entire app.

Quick Start

Ask routing-navigation-design to produce a complete route-table, redirect map, guard classification, deep-link state plan, validation rules, and route-level tests for the specific route changes you are implementing.