UI Components

Hover Card

A rich preview card that appears on hover with configurable delay, side placement, and portal rendering.

Quick Preview

Installation

// Copy HoverCard.tsx to your components/ui/ folder
// src/components/ui/HoverCard.tsx

Usage

import { HoverCard, HoverCardContent } from '@/components/ui/HoverCard'

<HoverCard
  trigger={<button>Hover me</button>}
  side="bottom"
  openDelay={300}
  closeDelay={150}
>
  <HoverCardContent>
    <p>Rich preview content here</p>
  </HoverCardContent>
</HoverCard>

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a ui component named Hover Card in React/Next.js.
Goal: recreate the same overall UI and behavior as the Hover Card reference from a component gallery.
What it needs to communicate: A rich preview card that appears on hover with configurable delay, side placement, and portal rendering..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Keep the API concise and reusable.
- Make visual states feel polished and consistent across variants and sizes.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- trigger: React.ReactNode — required — Element that activates the hover card
- children: React.ReactNode — required — Card content (use HoverCardContent)
- side: 'top' | 'bottom' | 'left' | 'right' — default 'bottom' — Side to display the card
- sideOffset: number — default 8 — Distance in pixels from the trigger
- openDelay: number — default 300 — Milliseconds before card opens
- closeDelay: number — default 150 — Milliseconds before card closes

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Open/close hover delay
- Four placement sides
- Portal rendering (never clipped)
- Mouse-over card keeps it open
- Smooth fade + translate animation
- HoverCardContent sub-component

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`trigger`*	`React.ReactNode`	-	Element that activates the hover card
`children`*	`React.ReactNode`	-	Card content (use HoverCardContent)
`side`	`'top' \| 'bottom' \| 'left' \| 'right'`	`'bottom'`	Side to display the card
`sideOffset`	`number`	`8`	Distance in pixels from the trigger
`openDelay`	`number`	`300`	Milliseconds before card opens
`closeDelay`	`number`	`150`	Milliseconds before card closes

← Back to UI Components