What problem does it solve? Teams frequently misuse links for actions that change data or state, build fake links from divs and click handlers, or write vague labels like "Click here" that break screen reader navigation. This Skill encodes the Recursica design system's rules for the link component so every navigational element is semantic, accessible, and consistent. ## Core Features & Use Cases - Link vs. button decision rules: Distinguishes navigation (link) from state-changing actions (button), including table rows, modals, and CTAs. - Label and behavior standards: Enforces destination-naming labels, real href attributes, external-link marking, and the prohibition on disabled links and automatic new tabs. - Accessibility requirements: Covers screen reader announcements, keyboard and focus behavior, and multi-channel signaling for external links. - Use Case: When adding a "View invoice" link to a table row, use this Skill to confirm it should be a real anchor naming its destination, persistently visible, and never disabled. ## Quick Start Ask the AI to review or add a link in your UI using the Recursica link guidelines, for example to check whether an element should be a link or a button.