What problem does it solve? When routes in a Rango application do not match as expected, resolve to the wrong handler, or lose their parent layout, developers need visibility into the generated route tree. This Skill explains how to inspect the route manifest programmatically to verify parent relationships, shortCodes, loaders, and intercept registrations. ## Core Features & Use Cases - Programmatic Manifest Access: Call router.debugManifest() to retrieve routes, layouts, totalRoutes, and totalLayouts as structured JSON. - ShortCode Decoding: Understand the M/L/C/R/P prefix format (Mount, Layout, Cache, Route, Parallel slot) to verify nesting depth and hierarchy. - Manifest Diffing: Use serializeManifest, compareManifests, and formatManifestDiff from @rangojs/router/__internal to compare manifests before and after route changes. - Use Case: A modal route stops rendering as an overlay. Inspect the manifest to confirm interceptCount > 0 and that the route's parentShortCode points to the expected layout rather than null. ## Quick Start Ask the AI to call router.debugManifest() in development and check whether my route has the correct parentShortCode and hierarchy.
