What problem does it solve? Rango routes normally render React Server Components, but applications also need plain JSON APIs, text endpoints, XML feeds, and image or streaming responses. This Skill explains how to define non-RSC response routes with typed payloads, structured errors, and client-side type safety. ## Core Features & Use Cases - Typed response route tags: Use path.json(), path.text(), path.html(), path.xml(), path.md(), path.image(), path.stream(), and path.any() inside any urls() callback, with automatic content-type wrapping or full Response pass-through. - Structured error handling: Throw RouterError to emit RFC 9457 problem+json bodies, or return/throw a Response directly as control flow with header and cookie merging. - End-to-end type safety: Look up response payload types with RouteResponse or the ambient Rango.PathResponse, and link to response routes with href.json() for hard navigation. - Use Case: Mount a blog module exposing /blog/api/stats and /blog/api/:slug/likes as JSON endpoints alongside RSC pages, then consume them from a typed fetch wrapper whose return type is inferred from the URL path. ## Quick Start Add a JSON API endpoint to my Rango app by defining a path.json route inside my urls() callback with a typed handler and named route.
