Ux Modals And Dialogs logo

Ux Modals And Dialogs

Organization
Uxcel-Lab
ux-modals-and-dialogs

Design or critique modals, dialogs, alerts, popovers, and bottom sheets — gate WHEN interrupting users is justified, then apply dismissal, title/button, and focus best practices. Trigger when the user asks to design or review a modal, dialog, popup, overlay, confirmation, alert, permission request, lightbox, or bottom sheet — or asks whether something should be a modal at all.

Overview

PublisherUxcel-Lab
Repositoryproduct-skills
Skill nameux-modals-and-dialogs
Stars
35
Forks
8
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Uxcel-Lab on GitHub. Read the source before you install it.

Installation

Install the Ux Modals And Dialogs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Uxcel-Lab/product-skills/tree/main/ux/components/modals-and-dialogs
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Uxcel-Lab/product-skills.git /tmp/product-skills
mkdir -p .claude/skills
cp -r /tmp/product-skills/ux/components/modals-and-dialogs .claude/skills/ux-modals-and-dialogs
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ux Modals And Dialogs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ux Modals And Dialogs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ux Modals And Dialogs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Modals & Dialogs Skill

How this skill behaves (read first)

This is a generative skill. The default failure modes: interrupting for everything (modals for success messages, tips, newsletters — attention spent like it's free), trapping users (no visible close, no Esc, stacked modals), and vague choices ("Are you sure?" → Yes/No). A modal takes the whole interface hostage — that's justified only in high-stakes moments, and the price is paid back with crystal-clear purpose and effortless exit. This skill gates:

  1. Gate the interruption itself — is a modal even justified here? The most important decision happens before any design.
  2. Apply the always-true core — purpose in the title, explicit buttons, easy dismissal, focus management.
  3. Surface the type and timing decisions (popup/fullscreen/popover/bottom sheet, permission priming) with trade-offs.

Then it hands off to ux-heuristics-audit, ux-accessibility-audit, ux-aesthetics-audit, ux-microcopy-audit, and ux-dark-patterns-audit for validation.


Step 0 — Gate the interruption (the decision that matters most)

A modal blocks everything. It earns that only for high-stakes moments:

  • Confirming destructive or irreversible actions (delete account, discard draft) — show impact ("12 files will be deleted").
  • Critical errors or warnings (system restart, unsaved changes at risk).
  • Information required to continue the current task (login to save, payment details).

Everything else — success messages, tips, FYIs, promotions — uses non-modal patterns: inline messages, toasts, banners, popovers. Also establish:

  • Who triggers it? User-initiated modals (clicked a button) are expected; system-initiated modals (timed popups, upgrade nags) interrupt without warning — avoid unless truly urgent (session expiry, critical update).
  • Timing — never interrupt high-stakes flows in progress (mid-checkout is the classic crime).
  • Platform — desktop alert vs. iOS alert / Android dialog conventions; bottom/action sheets for mobile action lists.

If the content fails the high-stakes test, stop designing a modal and recommend the inline/toast alternative.


The always-apply core (correct for every modal that survives the gate)

Purpose, title, buttons

  • The title carries the whole message — users skim or skip body text. "Discard draft?" not "Warning." Body text adds the why and context; nothing vital lives only in the body.
  • Explicit button labels answering the title: ❌ "Yes" / "No" / "Cancel" ✅ "Discard draft" / "Keep editing." Users must know what each button does without reading anything else.
  • Maximum two action buttons. A third ("Learn more") leaks users out of the decision.
  • Never blame or shame in opt-out labels ("No thanks, I hate saving money" → dark-patterns flag).

Dismissal is a right, not a feature

  • Multiple visible exits: Close/Cancel button + the × in the corner + Esc on desktop / Back on mobile.
  • Click/tap outside closes it — when no entered data would be lost; suppress only when dismissal would destroy work.
  • Never stack modals. A modal on a modal is a hostage situation with extra steps.

Focus and attention mechanics

  • Dark overlay behind the modal — focuses attention, blocks outside interaction, doubles as a close target.
  • Keyboard focus moves into the modal on open (onto the primary action); all controls keyboard-reachable.
  • Centered placement — dead-center on mobile; horizontally centered and slightly above center on desktop (stable under window resizing).
  • Critical alerts look critical: red accents and an alert icon for destructive/urgent confirmations, so habituated users don't dismiss on autopilot.

The context-dependent decisions (surface, don't auto-apply)

DecisionApply whenAvoid / adapt whenDefault recommendation
Popup modalThe standard high-stakes interrupt over dimmed contentContent that needs a whole pageDefault modal type
Fullscreen modalComplex focused tasks: multi-step forms, payments, T&Cs, mobile spotlight momentsSimple confirmations (overkill); anything users may need to escape fast — make dismissal obviousOnly when the task genuinely fills a screen
PopoverExtra detail/options anchored to an element, without blocking the pageCritical information (too easy to miss)The non-modal default for contextual help
LightboxImage/video magnification with navigation, captions, zoomNon-media contentMedia-rich products only
Bottom / action sheet (mobile)Lists of related actions or share targets, per OS conventionCritical confirmations (use an alert/dialog)Android bottom sheet / iOS action sheet for action lists
Success feedbackInline or on-page statesSuccess modals — interrupting to say "it worked"Modal success only if users must acknowledge before continuing
Permission requestsIn context, at the moment the feature needs it; primed with a pre-permission explainer; one permission at a time; a compelling reason (+81% grant likelihood)At first launch, in batches, with "Recommended" pressure labels, or mid-taskPrime → contextual ask → graceful path to reverse a denial
System-initiated modalsTruly urgent: session expiry, security, data lossSubscription nags, timed promos, rating begsAlmost never; use banners/badges instead

Validate the result (orchestration)

Hand-offs name each lens by its installable skill name. Invoke one only if that skill is installed; if it isn't, this skill's own core already carries these rules — proceed without it rather than blocking.

After generating or revising, hand the result to the audit lenses rather than declaring it done. These are candidate lenses — posture is set by docs/orchestration-policy.md, or route the whole thing through ux-design-review. Here, heuristics, microcopy, and dark-patterns are Tier A (auto-run); accessibility, aesthetics, and mobile-responsiveness are Tier B (offered) — under an existing design system aesthetics is suppressed and accessibility narrows to usage; mobile-responsiveness applies only on mobile. If the user invoked this skill for one specific thing, respect that scope.

  • ux-heuristics-audit (Tier A) — user control and freedom (exits), error prevention (explicit confirmations), match to expectations (platform conventions).
  • ux-accessibility-audit (Tier B — offer; narrow under a design system) — focus trap correctness, keyboard dismissal, screen-reader announcement, contrast of overlay content.
  • ux-aesthetics-audit (Tier B — offer; suppress under a design system) — modal visual hierarchy, overlay treatment, alert-styling restraint.
  • ux-microcopy-audit (Tier A) — title clarity, button explicitness, body brevity, permission-reason wording.
  • ux-dark-patterns-audit (Tier A) — this skill's interruptions are prime dark-pattern territory: nagging system modals, shame opt-outs, permission pressure, hard-to-find dismissal.
  • ux-mobile-responsiveness-audit (Tier B — offer; applies only on mobile) — when the context is mobile: sheet conventions, dismissal gestures, fullscreen behavior.

If the audits surface a conflict (e.g., growth wants a signup modal on page load vs. user control), resolve back toward the primary task: the user was doing something — the modal must either protect that task or get out of its way.


Common do/don't patterns

❌ Don't✅ Do
Modal for a success message or a tipInline state / toast; modals for high-stakes only
Timed subscription popup mid-readingUser-initiated modals; system interrupts only for urgency
"Are you sure?" → Yes / No"Discard draft?" → "Discard" / "Keep editing"
Three+ buttons including "Learn more"Two actions, aligned to the title
No × , no Esc, no outside clickClose button + Esc/Back + outside click (when safe)
Modal opens on top of another modalOne modal at a time, ever
Vital info buried in body textThe title carries the message
Permission batch on first launchPrimed, contextual, one-at-a-time requests with reasons
"No thanks, I like missing out"Neutral, respectful opt-out labels
Focus stays on the page behindFocus moves into the modal, onto the primary action
Ship without checkingHand off to heuristics + accessibility + aesthetics + microcopy + dark-patterns

Source lessons (Uxcel)

Frequently asked questions

What does the Ux Modals And Dialogs AI skill do?

Design or critique modals, dialogs, alerts, popovers, and bottom sheets — gate WHEN interrupting users is justified, then apply dismissal, title/button, and focus best practices. Trigger when the user asks to design or review a modal, dialog, popup, overlay, confirmation, alert, permission request, lightbox, or bottom sheet — or asks whether something should be a modal at all.

Why use Ux Modals And Dialogs on TypingMind?

Because you install it once and use it with any model. Ux Modals And Dialogs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ux Modals And Dialogs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Uxcel-Lab/product-skills/tree/main/ux/components/modals-and-dialogs. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ux Modals And Dialogs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ux Modals And Dialogs?

As many as you like. As long as a model supports skills, you can use Ux Modals And Dialogs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ux Modals And Dialogs AI skill free?

Yes. It is published on GitHub by Uxcel-Lab under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇