# Find Time (Notchset): prompt.md (v1.0.0)

- id: `find-time` · version 1.0.0 · block · pro (Pro)
- category: Application UI
- build: Base UI (one set of files; its dependencies follow the build)
- install (this build): `npx shadcn@latest add @beautiful-ui-pro/find-time`
- npm dependencies: class-variance-authority@^0.7
- registry dependencies: utils, @beautiful-ui/segmented-control, https://beautiful-ui.dev/r/notchset-foundation.json
- docs: https://beautiful-ui.dev/components/find-time
- The install command carries everything this item needs (files, CSS, tokens, npm and registry dependencies). Prefer it to copying source by hand.

A meeting-time finder across time zones: a length, five days that each count the slots that work for everyone, lanes of working hours and busy blocks in one zone with an ALL FREE row, a selection frame that glides to its start and turns signal on a conflict while naming who and why, up to five best times, and a confirm that sends with a scanner then lists who was invited.

## Build it
- Stack: React 19 (`ref` is a plain prop), TypeScript, Tailwind CSS v4 utilities, a shadcn-initialised project with the `@/*` alias.
- Packages: `class-variance-authority@^0.7`.
- Files: `components/ui/notchset/blocks/find-time.tsx`; shared code: `lib/beautiful-ui/notchset/instrument.tsx`, `lib/beautiful-ui/notchset/root.ts`, `lib/beautiful-ui/notchset/button-variants.ts`.
- Registry dependencies, installed with it automatically: shadcn `utils` (cn), `segmented-control`, `notchset-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: `FindTime`, and every exported type.
- CSS: the install adds the notchset foundation (tokens, keyframes, motion levels) to your global stylesheet 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 `--notchset-*` custom properties (`--notchset-check`, `--notchset-control-edge`, `--notchset-draw-from`, `--notchset-ease-bloom`, `--notchset-ease-glide`, `--notchset-ease-key-down`, `--notchset-ease-key-up`, `--notchset-ease-travel`, `--notchset-fade`, `--notchset-focus-color`, `--notchset-focus-inset`, `--notchset-grow-to`, `--notchset-key-down`, `--notchset-key-up`, `--notchset-life-from`, `--notchset-life-ms`, `--notchset-node-blink`, `--notchset-node-bloom`, `--notchset-node-delay`, `--notchset-plate-color`, `--notchset-rise-from`, `--notchset-rule`, `--notchset-scan-to`, `--notchset-scroll`, `--notchset-signal`, `--notchset-sweep-to`, `--notchset-travel`). Never add Tailwind colour classes inside the component.

```tsx
import { FindTime, type FindTimeDay, type FindTimePerson, type FindTimeSlot } from "@/components/ui/notchset/blocks/find-time";
```

## Parts

| Part | data-slot | What it is for |
|---|---|---|
| `FindTime` | `find-time` | Length, days, lanes, best times and the confirm row. |

Style a part with `[data-slot="<slot>"]` selectors or its `className`; keep the attributes when editing.

## 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 `SoundProvider` once (install: `npx shadcn@latest add https://beautiful-ui.dev/r/notchset-sound.json`, import from `@/components/ui/notchset/sound-provider`); `useSound()` gives `muted` and `setMuted` for a mute control. Without a provider the audio engine never loads.

## Match the original
- Read `components/ui/notchset/blocks/find-time.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
- find a time, meeting scheduler, time zones, availability, free busy, schedule meeting, calendar overlap, Notchset
- Scheduling a meeting for a few people in different time zones
- Showing why a proposed time does not work

### Not when
- Booking against a public calendar: use a booking page
- More than about six people: the lanes get too many to read

## Mistakes
- Convert every person's calendar to the block's zone before passing it
- Check the slot again on the server before sending invites

## Usage

```tsx
import { FindTime, type FindTimeDay, type FindTimePerson, type FindTimeSlot } from "@/components/ui/notchset/blocks/find-time";

export function Schedule({ days, people }: { days: FindTimeDay[]; people: FindTimePerson[] }) {
  return (
    <FindTime
      title="Planner v15 review"
      zone="ZÜRICH"
      days={days}
      people={people}
      onConfirm={(slot: FindTimeSlot) => fetch("/api/invites", { method: "POST", body: JSON.stringify(slot) })}
    />
  );
}
```

## Props

| Prop | Type | Default | What it does |
|---|---|---|---|
| `people` | `{ initials, name, city, offset, hours, busy, me? }[]` |  | Hours and busy blocks are in the block's zone; offset (hours) gives each person's local time; busy has one list per day. |
| `days` | `{ weekday, date, month }[]` |  | The days to pick from, in the order busy lists them. |
| `zone / title / eyebrow` | `string` |  | The zone every time is shown in, and the header. |
| `lengths / from / to` | `number[] / number` |  | Meeting lengths in minutes (30, 45, 60) and the hours on the lanes (8 to 19). |
| `onConfirm` | `(slot) => Promise` |  | Send the invites; a rejection shows COULD NOT SEND and lets them try again. |

Full docs: https://beautiful-ui.dev/components/find-time

## Customising
- Colours: the component reads your shadcn tokens (`--background`, `--foreground`, `--border` …), refined by the `--notchset-*` tokens. The signal colour is `--notchset-signal` (it falls back to `--destructive`). Set tokens on `:root`, or on any container to retheme one area.
- 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 |
|---|---|
| ← → | Change the length or day; on the lanes, move 30 minutes |
| Home / End | Jump to the first or last start on the lanes |
| Enter | Pick a best time, confirm |

## Performance

- Free slots are worked out per render from a few dozen half hours; nothing runs while idle.

## Responsive

- Under 640px (container width) the lanes keep 600px and scroll sideways; day buttons drop the word TIMES under 520px.

## Motion inventory

| Interaction | What moves |
|---|---|
| Pick | The frame and conflict outlines glide to the new start (300ms) |
| Day counts | Each count rolls, 60ms apart |
| Best times | Chips rise in (320ms) |
| Confirm | A scanner while sending, then the invited names |

## Accessibility contract (preserve when editing)
- Length and day are radio groups; each day is named with how many times work for everyone
- The lanes are a slider whose value text gives the time and who is busy or outside hours
- The summary line is a polite live region: free, the first conflict with its reason, or who was invited

## Install

```bash
npx shadcn@latest add @beautiful-ui-pro/find-time
```

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 notchset 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/notchset-foundation.json.