Patterns

UserProfileCard

Profile card with avatar, bio, stats, social links, and follow button.

Quick Preview

Alex Johnson

@alexj

Senior Engineer at DesignUI. Open source contributor and design system enthusiast.

Bangkok, THexample.comJoined Jan 2022

2.4K

Followers

342

Following

Projects

Installation

npm install lucide-react

// Copy from
src/components/patterns/UserProfileCard.tsx

Examples

Compact variant

Sam Lee

@samlee

Product designer & frontend enthusiast.

Posts

1.2K

Likes

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 patterns component named UserProfileCard in React/Next.js.
Goal: recreate the same overall UI and behavior as the UserProfileCard reference from a component gallery.
What it needs to communicate: Profile card with avatar, bio, stats, social links, and follow button..

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:
- Build the full multi-part interaction, not just the outer shell.
- Preserve realistic spacing, affordances, and task flow.
- 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:
- name: string — required — Display name
- username: string — @handle
- bio: string — Short biography text
- avatarInitials: string — Fallback avatar initials
- location: string — Location string
- website: string — Personal website URL
- joinedDate: string — Joined date string
- stats: UserStat[] — Stats to display (label + value)
- socialLinks: SocialLink[] — GitHub/Twitter links
- variant: 'default' | 'compact' — default 'default' — Card size variant
- onFollow: () => void — Follow button callback
- following: boolean — default false — Is currently following
- className: string — Additional CSS classes

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

Feature expectations:
- Cover image
- Avatar initials
- Stats grid
- Follow button
- Social icons

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
`name`*	`string`	-	Display name
`username`	`string`	-	@handle
`bio`	`string`	-	Short biography text
`avatarInitials`	`string`	-	Fallback avatar initials
`location`	`string`	-	Location string
`website`	`string`	-	Personal website URL
`joinedDate`	`string`	-	Joined date string
`stats`	`UserStat[]`	-	Stats to display (label + value)
`socialLinks`	`SocialLink[]`	-	GitHub/Twitter links
`variant`	`'default' \| 'compact'`	`'default'`	Card size variant
`onFollow`	`() => void`	-	Follow button callback
`following`	`boolean`	`false`	Is currently following
`className`	`string`	-	Additional CSS classes