What problem does it solve? Building breadcrumb trails in nested route hierarchies normally requires manually threading navigation state through layouts and pages. This Skill documents Rango's built-in Breadcrumbs handle, which lets each route segment push its own crumb and automatically collects them in parent-to-child order. ## Core Features & Use Cases - Server-side crumb pushing: Handlers and loader bodies push items via ctx.use(Breadcrumbs), with support for async content and deferred resolution via .defer() for values produced by deep components. - Client-side consumption: Read the accumulated trail with useHandle(Breadcrumbs) in client components, with optional selectors to re-render only on relevant changes. - Automatic deduplication: The built-in collect function deduplicates items by href, so sibling routes sharing a crumb never produce duplicates. - Use Case: On a route like /shop/widget, a root layout pushes "Home", a nested layout pushes "Shop", and the route handler pushes the product slug — the rendered trail is Home / Shop / widget with no manual prop threading. ## Quick Start Show me how to add a breadcrumb trail to my nested Rango routes using the built-in Breadcrumbs handle.
