Forms

Number Input

A stepper input with increment / decrement buttons, min/max/step constraints, and three sizes.

Quick Preview

Quantity

Installation

// Copy NumberInput.tsx to your components/forms/ folder
// src/components/forms/NumberInput.tsx

Usage

import { NumberInput } from '@/components/forms/NumberInput'

const [count, setCount] = useState(0)

<NumberInput
  value={count}
  onChange={setCount}
  min={0}
  max={100}
  step={1}
  label="Count"
/>

Examples

Sizes

Small

Medium

Large

E-commerce Cart Quantity

of 10 in stock

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 Number Input in React/Next.js.
Goal: recreate the same overall UI and behavior as the Number Input reference from a component gallery.
What it needs to communicate: A stepper input with increment / decrement buttons, min/max/step constraints, and three sizes..

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 numeric value
- onChange: (value: number) => void — required — Called with new value on change
- min: number — default -Infinity — Minimum allowed value
- max: number — default Infinity — Maximum allowed value
- step: number — default 1 — Amount added/subtracted per click
- label: string — Optional label displayed above the input
- disabled: boolean — Disable all interactions
- size: "sm" | "md" | "lg" — default "md" — Size of the input

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

Feature expectations:
- Increment/decrement buttons
- Min/max/step constraints
- Direct keyboard input
- Three sizes (sm, md, lg)
- Disabled state
- Focus ring on container
- Hides native spin buttons

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 numeric value
`onChange`*	`(value: number) => void`	-	Called with new value on change
`min`	`number`	`-Infinity`	Minimum allowed value
`max`	`number`	`Infinity`	Maximum allowed value
`step`	`number`	`1`	Amount added/subtracted per click
`label`	`string`	-	Optional label displayed above the input
`disabled`	`boolean`	-	Disable all interactions
`size`	`"sm" \| "md" \| "lg"`	`"md"`	Size of the input

← Back to Forms