Forms

Slider

Range slider with fill track, value display, min/max labels, and custom thumb styling

Quick Preview

Volume60

0100

Installation

// Copy the Slider component from
src/components/forms/Slider.tsx

Usage

'use client'
import { useState } from 'react'
import { Slider } from '@/components/forms/Slider'

export default function Example() {
  const [volume, setVolume] = useState(60)
  return (
    <Slider
      value={volume}
      onChange={setVolume}
      label="Volume"
      showValue
    />
  )
}

Examples

Custom Step

Step: 1050

0100

Custom Min / Max

Temperature (°C)22

1630

Multiple Sliders

Brightness80

0100

Contrast50

0100

Saturation60

0100

Disabled

Locked40

0100

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 forms component named Slider in React/Next.js.
Goal: recreate the same overall UI and behavior as the Slider reference from a component gallery.
What it needs to communicate: Range slider with fill track, value display, min/max labels, and custom thumb styling.

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:
- Support label, helper, error, disabled, and validation states.
- Ensure keyboard usability and accessible form semantics.
- 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:
- value: number — required — Current slider value
- onChange: (value: number) => void — required — Value change handler
- min: number — default 0 — Minimum value
- max: number — default 100 — Maximum value
- step: number — default 1 — Step increment
- label: string — Label text above the slider
- showValue: boolean — Show current value beside label
- disabled: boolean — Disable the slider

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

Feature expectations:
- Custom fill track (primary color)
- Custom styled thumb
- Label and live value display
- Min / Max labels below track
- Keyboard accessible (arrow keys)
- Client Component

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
`value`*	`number`	-	Current slider value
`onChange`*	`(value: number) => void`	-	Value change handler
`min`	`number`	`0`	Minimum value
`max`	`number`	`100`	Maximum value
`step`	`number`	`1`	Step increment
`label`	`string`	-	Label text above the slider
`showValue`	`boolean`	-	Show current value beside label
`disabled`	`boolean`	-	Disable the slider

Features

✓Custom fill track (primary color)
✓Custom styled thumb
✓Label and live value display
✓Min / Max labels below track
✓Keyboard accessible (arrow keys)
✓Client Component