Navigation

CommandBar

Keyboard-first command palette — search, navigate, and trigger actions with ↑↓ and Enter.

Quick Preview

Pages

Components

Actions

☀️

Toggle Theme

⌘T

🚀

Open Tracks

⌘P

Help

↑↓ Navigate↵ SelectEsc Close

Installation

// Copy from
src/components/navigation/CommandBar.tsx

// Dependencies
npm install lucide-react

Usage

import CommandBar from '@/components/navigation/CommandBar'

const items = [
  { icon: '🏠', label: 'Home', href: '/', category: 'Pages' },
  { icon: '⚡', label: 'Animations', href: '/components/animations', category: 'Components' },
  { icon: '☀️', label: 'Toggle Theme', category: 'Actions', shortcut: ['⌘', 'T'] },
]

export default function App() {
  return <CommandBar items={items} placeholder="Search commands…" />
}

Examples

Components only

Filtered to a single category

Components

↑↓ Navigate↵ SelectEsc Close

Keyboard shortcuts

Items with shortcut badges visible at a glance

Actions

☀️

Toggle Theme

⌘T

🚀

Open Tracks

⌘P

↑↓ Navigate↵ SelectEsc Close

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 navigation component named CommandBar in React/Next.js.
Goal: recreate the same overall UI and behavior as the CommandBar reference from a component gallery.
What it needs to communicate: Keyboard-first command palette — search, navigate, and trigger actions with ↑↓ and Enter..

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:
- Handle hover, active, selected, keyboard, and mobile states with clear feedback.
- Keep structure tidy so it feels production-ready rather than demo-only.
- 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:
- items: CommandBarItem[] — required — Array of {icon?, label, href?, category?, shortcut?, onSelect?}
- placeholder: string — default 'Search commands…' — Input placeholder

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

Feature expectations:
- Fuzzy search
- Category groups
- Keyboard navigation
- Keyboard shortcuts display

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
`items`*	`CommandBarItem[]`	-	Array of {icon?, label, href?, category?, shortcut?, onSelect?}
`placeholder`	`string`	`'Search commands…'`	Input placeholder