popup-patterns

Standardize popup component styling and behavior across dropdown menus, selects, comboboxes, and popovers.

3|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/keystone-ui/react --skill popup-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: popup-patterns
Source: https://github.com/keystone-ui/react/tree/main/.claude/skills/popup-patterns
Command: npx skills add https://github.com/keystone-ui/react --skill popup-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents popup components from drifting into inconsistent sizing, styling, and motion patterns across the UI library.

Core Features & Use Cases

It defines a shared system for item height, container styling, animation timing, and separator treatment across DropdownMenu, Select, Combobox, and Popover. Use it when creating or editing popup-related components in packages/ui/ so the design language stays aligned and accessible. It also clarifies which shared utilities and class recipes must be reused instead of hardcoded per component.

Quick Start

Apply this skill when updating a popup component in packages/ui/ to reuse the shared height, container, animation, and separator conventions.

Frequently Asked Questions about popup-patterns

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

FAQPage Schema
How do I keep popup component styling consistent across dropdown menus, selects, and comboboxes?

To keep popup component styling consistent, standardize item height, container recipes, animations, and separators using shared utilities like POPUP_ITEM_HEIGHT and synchronized animation tokens across all UI components. This prevents visual drift and maintains a unified design language across the library.

What is the best way to standardize Tailwind popup item sizing and container styling?

The best way to standardize Tailwind popup item sizing is to apply shared class recipes and a consistent POPUP_ITEM_HEIGHT variable across dropdowns and popovers. This ensures uniform item dimensions, ring and shadow classes, and size-aware data attributes throughout the UI library.

How do I align animation timing and separator treatment across popover and dropdown menu components?

Align animation timing and separator treatment by reusing synchronized animation tokens and shared container recipes across popover and dropdown menu components. This approach replaces hardcoded per-component styling with a unified system for consistent motion and visual separation.

Do I need to use shared utilities when editing popup components in a UI library?

Yes, you need to use shared utilities when editing popup components in a UI library to prevent styling drift. Reusing shared height variables, container recipes, and animation tokens ensures that dropdown menus, selects, and comboboxes remain visually aligned and accessible.

Why do my UI library popup components have inconsistent sizing and motion patterns?

Popup components have inconsistent sizing and motion patterns when shared utilities are bypassed for hardcoded per-component styling. Using shared POPUP_ITEM_HEIGHT values, size-aware data attributes, and synchronized animation tokens eliminates this drift across dropdowns, selects, comboboxes, and popovers.