SkillsAdd

thedaviddias/ux-patterns-for-developers

popover

Use when you need to display focused content or actions.

First seen Mar 15, 2026

Installation

$ npx skills add thedaviddias/ux-patterns-for-developers --skill popover
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from thedaviddias/ux-patterns-for-developers · top by installs.

npx skills add thedaviddias/ux-patterns-for-developers
ux-patterns 51 sidebar 22 skeleton 19 table 18 progress-indicator 17 navigation-menu 17 wizard 17 form-validation 17 empty-states 17 ai-loading-states 16

Browse all from thedaviddias/ux-patterns-for-developers

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 240
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
id
popover
category
content-management
pattern
Popover
source
uxpatterns.dev
url
https://uxpatterns.dev/patterns/content-management/popover
sourcePath
apps/web/content/patterns/content-management/popover.mdx

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,744 B
  • docs SUMMARY.md 71 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

SKILL.md

Popover

Display focused content or actions

What it solves

Popovers overlay the main content to give users additional information or actions. Popovers display contextual content while keeping the surrounding page visible. Unlike modals blocking page interaction, popovers deliver contextual help or shortcuts while the main interface stays visible and interactive.

When to use

Use popovers for context-specific information or quick actions that complement the main view without needing full user focus. Common scenarios include:

  • Contextual help needs additional details about data fields
  • Quick actions or shortcuts like editing options or extra buttons
  • Compact toolbars or menus with filters or settings appearing on demand
  • Preview or supplementary info shows image or text previews on hover/focus

When to avoid

  • Critical information must stay persistently visible
  • Large forms or complex interactions work better as modals
  • Context needs full-page takeover for clarity

Implementation workflow

  1. Confirm the pattern matches the problem and constraints before copying the example.
  2. Start from the anatomy and examples in references/pattern.md, then choose the smallest viable variation.
  3. Apply accessibility, performance, and interaction guardrails before layering visual polish.
  4. Use the testing guidance to verify behavior across keyboard, screen reader, responsive, and failure scenarios.

Accessibility guardrails

ARIA Attributes

Required ARIA attributes:

  • aria-haspopup="true" on the trigger element.
  • aria-expanded on the trigger element to reflect open/closed state.
  • role="dialog" (or role="menu" if used as a menu) on the popover container.
  • Ensure focus management so that keyboard users receive context.

Keyboard Interaction Pattern

The following table outlines the standard keyboard interactions for popover components.

Key Action

Related patterns

For full implementation detail, examples, and testing notes, see references/pattern.md.

Pattern page: https://uxpatterns.dev/patterns/content-management/popover