Common Components

Empty State

A friendly placeholder shown when a list or page has no content — with icon, title, description, and optional CTA.

Quick Preview

📭

No messages yet

When you receive messages, they will appear here.

Installation

// Copy EmptyState.tsx to your components/common/ folder
// src/components/common/EmptyState.tsx

Usage

import { EmptyState } from '@/components/common/EmptyState'

<EmptyState
  icon="🔍"
  title="No results found"
  description="Try adjusting your search or filter to find what you're looking for."
  action={<Button variant="outline">Clear filters</Button>}
/>

Examples

Common Scenarios

🔍

No results found

Try a different search term.

🛒

Your cart is empty

Add items to get started.

🔔

All caught up!

No new notifications.

Sizes

📁

Small empty state

Size sm

📁

Medium empty state

Size md (default)

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 common component named Empty State in React/Next.js.
Goal: recreate the same overall UI and behavior as the Empty State reference from a component gallery.
What it needs to communicate: A friendly placeholder shown when a list or page has no content — with icon, title, description, and optional CTA..

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:
- Design the component so it can be dropped into landing and application pages without refactoring.
- Preserve clear content hierarchy and comfortable spacing.
- 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:
- title: string — required — Primary heading text
- icon: React.ReactNode — Icon or emoji displayed above the title
- description: string — Supporting body text
- action: React.ReactNode — Optional CTA button or link
- size: "sm" | "md" | "lg" — default "md" — Controls spacing and text size

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

Feature expectations:
- Three sizes with proportional spacing
- Optional icon, description, and action
- Server Component (no client state needed)
- Flexible icon slot (emoji, Lucide icons, SVG)

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
`title`*	`string`	-	Primary heading text
`icon`	`React.ReactNode`	-	Icon or emoji displayed above the title
`description`	`string`	-	Supporting body text
`action`	`React.ReactNode`	-	Optional CTA button or link
`size`	`"sm" \| "md" \| "lg"`	`"md"`	Controls spacing and text size

← Back to Common Components