Patterns

CookieBanner

GDPR-style cookie consent banner with Accept/Decline and dismiss state.

Quick Preview

🍪

We use cookies

We use cookies to enhance your browsing experience, analyze site traffic, and personalize content.

Installation

# No extra dependencies

// Copy component from
src/components/patterns/CookieBanner.tsx

Usage

import CookieBanner from '@/components/patterns/CookieBanner'

// Renders as a sticky bottom banner until the user accepts or declines
<CookieBanner
  onAccept={() => enableAnalytics()}
  onDecline={() => console.log('Declined')}
/>

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 CookieBanner in React/Next.js.
Goal: recreate the same overall UI and behavior as the CookieBanner reference from a component gallery.
What it needs to communicate: GDPR-style cookie consent banner with Accept/Decline and dismiss state..

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:
- title: string — Banner title
- description: string — Banner description text
- onAccept: () => void — Accept callback
- onDecline: () => void — Decline callback
- position: 'bottom' | 'top' — default 'bottom' — Banner position
- className: string — Additional CSS classes

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

Feature expectations:
- Accept/Decline actions
- Dismissed state
- Top or bottom position

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`	-	Banner title
`description`	`string`	-	Banner description text
`onAccept`	`() => void`	-	Accept callback
`onDecline`	`() => void`	-	Decline callback
`position`	`'bottom' \| 'top'`	`'bottom'`	Banner position
`className`	`string`	-	Additional CSS classes