UI Components

AvatarStack

A row of overlapping user avatars with auto-generated initials, color coding, and an overflow "+N" badge.

Quick Preview

6 members, showing 4

Installation

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

Usage

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

// Text-only (auto-generates initials + colors)
<AvatarStack
  avatars={[
    { name: 'Alice Johnson' },
    { name: 'Bob Smith' },
  ]}
  max={4}
/>

// With images
<AvatarStack
  avatars={[
    { name: 'Alice', src: '/alice.jpg' },
    { name: 'Bob', src: '/bob.jpg' },
  ]}
/>

Examples

Sizes

Team Assignment (Linear-style)

Dashboard Redesign

Due in 3 days

API Integration

Due tomorrow

User Testing

Due next week

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 AvatarStack in React/Next.js.
Goal: recreate the same overall UI and behavior as the AvatarStack reference from a component gallery.
What it needs to communicate: A row of overlapping user avatars with auto-generated initials, color coding, and an overflow "+N" badge..

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:
- avatars: Array<{ name: string; src?: string; color?: string }> — required — List of avatar data objects
- max: number — default 4 — Maximum avatars shown before +N badge
- size: "sm" | "md" | "lg" — default "md" — Size of each avatar

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

Feature expectations:
- Auto-generates initials from name
- Automatic distinct color assignment
- Supports image avatars via src
- Overflow "+N" badge
- Three sizes (sm, md, lg)
- White ring separator between avatars

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
`avatars`*	`Array<{ name: string; src?: string; color?: string }>`	-	List of avatar data objects
`max`	`number`	`4`	Maximum avatars shown before +N badge
`size`	`"sm" \| "md" \| "lg"`	`"md"`	Size of each avatar

← Back to UI Components