dialogs-slice

Centralize global dialog open/close state with type-safe DialogId registries.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill dialogs-slice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dialogs-slice
Source: https://github.com/Ledger-Wallet-LLC/ledgerwallet/tree/main/.cursor/skills/dialogs-slice
Command: npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill dialogs-slice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes global dialog open/close state management across MVVM-based apps, reducing per-dialog state boilerplate and ensuring consistent UX.

Core Features & Use Cases

  • Centralized Redux-like slice for all global dialogs
  • Type-safe DialogId registry and a single mount point for rendering
  • Simple pattern to add new dialogs without touching existing reducers
  • Ideal for root-mounted dialogs triggered from anywhere in the component tree

Quick Start

Register the new dialog by adding its ID to DIALOG_IDS, create its feature dialog file, and mount it in GlobalDialogs.

Frequently Asked Questions about dialogs-slice

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

FAQPage Schema
How do I manage global dialog state in an MVVM app without prop drilling?

Centralize global dialog state by using a single dialogs slice for open/close management, allowing root-mounted dialogs to be triggered from distant components without prop drilling.

What is the best way to centralize open/close state for root-mounted dialogs?

The best way to centralize open/close state is implementing a single Redux-like slice with a GlobalDialogs mount point, ensuring a consistent UX and a single source of truth for dialog visibility.

How do I add a new dialog to a centralized global state without modifying existing reducers?

Register the new dialog by adding its ID to the DIALOG_IDS registry, create a per-feature dialog wrapper, and mount it within the GlobalDialogs component to avoid touching existing reducers.

Does centralized dialog management work with type-safe IDs in Redux architectures?

Yes, centralized dialog management implements a type-safe DialogId registry via DIALOG_IDS, ensuring that global dialog open/close actions are validated within Redux-like architectures.

When should I use a centralized dialogs slice instead of local component state?

Use a centralized dialogs slice when root-mounted dialogs must be opened from distant components across the tree, requiring a single source of truth to reduce per-dialog state boilerplate.