modal-toast-dialog-stinger

Select accessible React overlay primitives and audit focus, ARIA, and stacking behavior.

72|28|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/that-git-life --skill modal-toast-dialog-stinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modal-toast-dialog-stinger
Source: https://github.com/legioncodeinc/that-git-life/tree/main/.claude/skills/modal-toast-dialog-stinger
Command: npx skills add https://github.com/legioncodeinc/that-git-life --skill modal-toast-dialog-stinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the complexity of designing accessible React overlays by providing consistent guidance for selecting primitives, handling focus behavior, and avoiding common modal and notification UX failures.

Core Features & Use Cases

  • Overlay Primitive Selection: Choose the right implementation pattern for dialogs, alert dialogs, drawers, toasts, and command palettes using established React libraries.
  • Accessibility Auditing: Apply the accessible-modal contract covering focus traps, keyboard behavior, ARIA attributes, scroll locking, and focus restoration.
  • Use Case: Review a React application's overlay system to identify accessibility issues, select better primitives, and standardize modal, toast, and drawer behavior.

Quick Start

Ask the skill to audit my React overlays and recommend accessible primitives and fixes for any focus, ARIA, or stacking issues.

Frequently Asked Questions about modal-toast-dialog-stinger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build accessible React overlays that handle focus trapping and ARIA semantics correctly?

To build accessible React overlays, you must implement an accessible modal contract covering focus traps, keyboard behavior, ARIA attributes, scroll locking, and focus restoration. This Skill audits your implementation and recommends appropriate primitive patterns to ensure compliance.

When should I use a modal dialog versus a toast or drawer in my React application?

You should select a modal dialog for critical interactions requiring immediate focus, a drawer for secondary navigation, and a toast for transient notifications. This Skill guides primitive selection by matching overlay patterns to specific React use cases and accessibility requirements.

What is the accessible modal contract for React overlay components?

The accessible modal contract for React requires proper portal mounting, ARIA semantics, focus trapping, scroll locking, and focus restoration upon close. This Skill applies these rules to review your overlay architecture and identify missing accessibility contracts.

How do I fix focus management and stacking issues in React dialogs and toasts?

Fixing focus management and stacking issues in React dialogs requires applying correct portal mounting and z-index stacking rules alongside focus restoration logic. This Skill audits your overlay system to debug focus behavior and standardize component stacking.

Does this React overlay guidance work with Radix primitives and similar libraries?

Yes, this React overlay guidance applies framework-specific component selection for established libraries including Radix. It helps you choose and implement the right primitive patterns for dialogs, drawers, toasts, and command palettes using your preferred React toolkit.

Why does my React modal lose focus or fail keyboard navigation after closing?

Your React modal loses focus or fails keyboard navigation because it lacks proper focus restoration and focus trap mechanisms defined in the accessible modal contract. This Skill audits your overlay behavior to identify and recommend fixes for these specific accessibility failures.