# Question Card (Lumen Halo): prompt.md (v1.0.0)

- id: `lumen-question-card` · version 1.0.0 · component · pro (Pro)
- category: AI interfaces
- build: Base UI (one set of files; its dependencies follow the build)
- install (this build): `npx shadcn@latest add @beautiful-ui-pro/lumen-question-card`
- npm dependencies: none
- registry dependencies: utils, @beautiful-ui/lumen-button, @beautiful-ui/lumen-input, @beautiful-ui/lumen-textarea, https://beautiful-ui.dev/r/lumen-foundation.json
- docs: https://beautiful-ui.dev/components/lumen-question-card
- The install command carries everything this item needs (files, CSS, tokens, npm and registry dependencies). Prefer it to copying source by hand.

An agent asks before it goes on: pick one option or several, write your own under Other, or answer in words. Number keys choose, Enter sends, and the card folds to your answer with Change to reopen it.

## Build it
- Stack: React 19 (`ref` is a plain prop), TypeScript, Tailwind CSS v4 utilities, a shadcn-initialised project with the `@/*` alias.
- Packages: none beyond React.
- Files: `components/ui/lumen/controls/question-card.tsx`.
- Registry dependencies, installed with it automatically: shadcn `utils` (cn), `lumen-button`, `lumen-input`, `lumen-textarea`, `lumen-foundation`.
- Builds: one set of files for both, but its dependencies come in Base UI and Radix builds. Install the one that matches the project (see Install): a free item's bare URL installs the Base UI build of it and its dependencies.
- Exports to keep: `QuestionCard`, and every exported type.
- CSS: the install merges this item's rules (the registry `css` field) into your global stylesheet, in `@layer components`, and adds the lumen foundation (tokens, keyframes, motion levels) once. Nothing to import by hand.
- Re-running `add` (or `--overwrite`) re-applies those rules: put overrides in your own CSS, never in the installed rules.
- Tokens: retheme with the `--lumen-*` custom properties (`--lumen-accent`, `--lumen-accent-foreground`, `--lumen-accent-text`, `--lumen-bad`, `--lumen-bad-text`, `--lumen-chart-accent`, `--lumen-chart-accent-foreground`, `--lumen-chart-accent-text`, `--lumen-focus`, `--lumen-good`, `--lumen-good-text`, `--lumen-hairline`, `--lumen-ink`, `--lumen-muted-ink`, `--lumen-series-1`, `--lumen-series-2`, `--lumen-series-3`, `--lumen-series-4`, `--lumen-series-5`, `--lumen-series-6`, `--lumen-warn`, `--lumen-warn-text`); this item's CSS also reads `--lumen-font-mono`, `--lumen-font-sans`, `--lumen-radius-k`. Never add Tailwind colour classes inside the component.

```tsx
import { QuestionCard } from "@/components/ui/lumen/controls/question-card";
```

## Parts

| Part | data-slot | What it is for |
|---|---|---|
| `QuestionCard` | — | The card (data-state asking or answered); each option is question-card-option. |

## Sound
- Keep every `data-slot` and `data-sound` attribute: the sound layer reads them.
- Installing this item adds no audio. Nothing plays until the app mounts `GlassSoundProvider` once (install: `npx shadcn@latest add https://beautiful-ui.dev/r/glass-sound.json`, import from `@/components/beautiful-ui/glass-sound`); `GlassSoundToggle` is its mute control. Without a provider the audio engine never loads.

## Match the original
- Read `components/ui/lumen/controls/question-card.tsx` as the reference implementation before changing or recreating anything, and match it: sizes, colours per theme, motion timings, copy and behaviour.
- If you deviate (a prop you can't honour, a style you changed, a dependency you swapped), say so in your reply, part by part.
- Keep the accessibility contract, the keyboard map and the motion levels listed below.

## Use it when
- agent asks a question, clarifying question, multiple choice prompt, human input request, AI needs input, Lumen
- An agent needs a choice or a detail before continuing
- Clarifying questions inside a chat thread

### Not when
- Long forms: use Field and the form controls
- Approving a whole plan: use Plan Card

## Mistakes
- Ask one thing per card; several questions belong in a form
- Keep option values stable: they're what onAnswer returns

## Usage

```tsx
"use client";

import { QuestionCard } from "@/components/ui/lumen/controls/question-card";

export function DeployQuestion({ reply }: { reply: (answer: string) => void }) {
  return (
    <QuestionCard
      question="Where should I deploy this build?"
      description="Production needs a second approval."
      options={[
        { value: "preview", label: "Preview", description: "A link for this branch only" },
        { value: "staging", label: "Staging" },
        { value: "production", label: "Production" },
      ]}
      allowOther
      onAnswer={({ values, text }) => reply(text ?? values[0] ?? "")}
      onSkip={() => reply("skip")}
    />
  );
}
```

## Props

| Prop | Type | Default | What it does |
|---|---|---|---|
| `question / description` | `ReactNode` |  | What it asks, and why. |
| `options` | `QuestionOption[] ({ value, label, description? })` |  | Without options the answer is free text. |
| `multiple` | `boolean` | `false` | Several options can be chosen. |
| `allowOther` | `boolean` | `false` | Add Other, with a field for the person's own answer. |
| `answer / defaultAnswer / onAnswer` | `QuestionAnswer \| null ({ values, text? })` |  | Controlled or not. Once answered, the card folds to the answer. |
| `onSkip` | `() => void` |  | Shows Skip. |
| `locked` | `boolean` | `false` | No Change once answered (the agent already moved on). |
| `labels` | `Partial<QuestionCardLabels>` |  | Every word on the card, for other languages. |

Full docs: https://beautiful-ui.dev/components/lumen-question-card

## Customising
- Colours: set the `--lumen-*` tokens on `:root`, or on a container with the `lumen-scope` class to retheme one area. Add the `lumen-inherit` class to follow your shadcn palette instead (`--chart-N`, `--destructive`).
- Dark mode follows the `.dark` class on an ancestor (the shadcn and next-themes convention).
- Update later by re-running the install with `--overwrite` (review the diff if you edited it). Changelog: https://beautiful-ui.dev/r/changelog.json

## Keyboard

| Keys | Action |
|---|---|
| 1–9 | Choose that option (toggle it when several are allowed) |
| Arrows | Move between options (single choice) |
| Enter | Send (Cmd/Ctrl+Enter from a text field) |

## Motion inventory

| Interaction | What moves |
|---|---|
| Choose | The tile takes an ink edge and the indicator fills; no travel |

## Accessibility contract (preserve when editing)
- Options are real radios or checkboxes in a fieldset whose legend is the question
- Each option's number key is in aria-keyshortcuts; Other gets its own named field
- The folded card reads the question and "Your answer" before the answer

## Install

```bash
npx shadcn@latest add @beautiful-ui-pro/lumen-question-card
```

Pro item: needs the `@beautiful-ui-pro` registry in `components.json` and `BEAUTIFUL_UI_TOKEN` in `.env.local` (https://beautiful-ui.dev/account). Setup: https://beautiful-ui.dev/docs/pro. Your components.json `style` picks the build: radix-*, new-york and default get Radix, base-* gets Base UI.

## Credits
- Built on shadcn/ui (https://ui.shadcn.com)

The lumen foundation (the tokens listed above, keyframes and motion levels) installs once with the first component; its CSS is public at https://beautiful-ui.dev/r/lumen-foundation.json.