UI Components

Collapsible

A single-item expandable panel with animated height transition — perfect for FAQs, descriptions, and settings.

Quick Preview

Installation

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

Usage

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

// Basic usage
<Collapsible trigger="Click to expand">
  Hidden content shown when expanded
</Collapsible>

// Open by default
<Collapsible trigger="Initially open" defaultOpen>
  This content is visible by default
</Collapsible>

Examples

FAQ Style

We accept Visa, Mastercard, and all major payment methods.

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 Collapsible in React/Next.js.
Goal: recreate the same overall UI and behavior as the Collapsible reference from a component gallery.
What it needs to communicate: A single-item expandable panel with animated height transition — perfect for FAQs, descriptions, and settings..

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 — Content shown in the header/toggle area
- children: React.ReactNode — required — Content revealed when expanded
- defaultOpen: boolean — default false — Whether the panel starts open
- open: boolean — Controlled open state
- onOpenChange: (open: boolean) => void — Called when open state changes

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

Feature expectations:
- CSS max-height animation (no extra deps)
- Chevron rotation indicator
- Controlled & uncontrolled modes
- Keyboard accessible (button role)
- aria-expanded attribute

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`	-	Content shown in the header/toggle area
`children`*	`React.ReactNode`	-	Content revealed when expanded
`defaultOpen`	`boolean`	`false`	Whether the panel starts open
`open`	`boolean`	-	Controlled open state
`onOpenChange`	`(open: boolean) => void`	-	Called when open state changes

← Back to UI Components