UI Components

Tooltip

Hover and focus triggered tooltip with four position options

Quick Preview

Installation

// Copy the Tooltip component from
src/components/ui/Tooltip.tsx

Usage

import { Tooltip } from '@/components/ui/Tooltip'

// Wrap any element — it becomes the trigger
<Tooltip content="Delete this item" position="top">
  <button aria-label="Delete">🗑</button>
</Tooltip>

Examples

Four Positions

Icon Toolbar

Help Icon

API Key

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 Tooltip in React/Next.js.
Goal: recreate the same overall UI and behavior as the Tooltip reference from a component gallery.
What it needs to communicate: Hover and focus triggered tooltip with four position options.

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:
- content: string — required — Tooltip label text
- position: "top" | "bottom" | "left" | "right" — default "top" — Tooltip placement relative to trigger
- children: React.ReactNode — required — The trigger element
- className: string — Additional CSS classes for the tooltip

Reference usage patterns:
- Basic

```tsx
<Tooltip content="Delete item"><button>🗑</button></Tooltip>
```

- Bottom position

```tsx
<Tooltip content="More info" position="bottom"><Info size={16} /></Tooltip>
```

Feature expectations:
- Four positions: top, bottom, left, right
- Mouse hover and keyboard focus triggers
- role="tooltip" for accessibility
- Wraps any element as trigger
- No external dependencies
- Client 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
`content`*	`string`	-	Tooltip label text
`position`	`"top" \| "bottom" \| "left" \| "right"`	`"top"`	Tooltip placement relative to trigger
`children`*	`React.ReactNode`	-	The trigger element
`className`	`string`	-	Additional CSS classes for the tooltip

Features

✓Four positions: top, bottom, left, right
✓Mouse hover and keyboard focus triggers
✓role="tooltip" for accessibility
✓Wraps any element as trigger
✓No external dependencies
✓Client Component