What problem does it solve? Choosing and implementing transient notifications is error-prone: teams misuse toasts for field errors, blocking decisions, or critical alerts, and often ship toasts that screen readers never announce or that auto-dismiss before keyboard users can reach an undo action. This Skill encodes the Recursica design system's rules for when a toast is the right channel and how to implement it accessibly. ## Core Features & Use Cases - Usage decision rules: Defines when a toast is correct (success confirmation, global undo, unattached errors) and when to use a modal, field error state, or in-place undo instead. - Token inventory constraints: Documents the exact default, success, and error styles from the Recursica UI kit, with no warning style, no size or position axis, and component-owned padding, elevation, and colors. - Accessibility requirements: Specifies live region behavior (polite vs assertive announcement), keyboard reachability, focus management, and the rule that an undo must never live only inside an auto-dismissing toast. - Use Case: When adding a "Saved" confirmation after a form submit, use this Skill to confirm a toast is the right channel, pass only the success variant, write text that names what happened, and wire a pre-existing live region so screen readers announce it politely without moving focus. ## Quick Start Ask the AI to review or implement a toast notification for a completed action using the Recursica toast guidelines, including its accessibility and undo requirements.
