What problem does it solve? Breadcrumbs are frequently misused as primary navigation, built with the current page as a link, or rendered inaccessible to screen readers. This Skill defines when a breadcrumb is warranted, what belongs in the trail, and the exact accessibility requirements for building one in the Recursica design system. ## Core Features & Use Cases - Usage Rules: Defines when a breadcrumb is appropriate (genuinely nested structures) versus when headings, tabs, or steppers are the right choice, and enforces that a breadcrumb is never primary navigation. - Token Inventory: Documents the component's two properties (padding and item-gap) and explicitly flags what is undefined — separators, truncation, content axes — so nothing is invented. - Accessibility Requirements: Specifies a named navigation region, semantic list markup, a programmatically marked current page, silent separators, and correct keyboard behavior. - Use Case: When adding a breadcrumb to a deep settings page, use this Skill to verify the trail reflects the hierarchy, the last item is unlinked and marked current, and separators are hidden from assistive technology. ## Quick Start Use the breadcrumb skill to review my breadcrumb implementation for correct hierarchy, linking, and screen-reader accessibility.
