# Outcomes (Notchset): prompt.md (v1.0.0)

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

Customer outcomes by tab: a quote with the person and their scale, three measures with before, a rolling after and the change (points, a multiple or a percent, computed from the numbers), each over a ruler where a hollow before dot and a filled after dot slide to new places as you switch customers, how they did it in three dated steps, and a link to the case study.

## 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/outcomes.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), `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: `Outcomes`, 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-sheet-from`, `--notchset-signal`, `--notchset-sweep-to`, `--notchset-travel`). Never add Tailwind colour classes inside the component.

```tsx
import { Outcomes, type CustomerOutcome } from "@/components/ui/notchset/blocks/outcomes";
```

## Parts

| Part | data-slot | What it is for |
|---|---|---|
| `Outcomes` | `outcomes` | Customer tabs, the quote and the measured outcomes. |

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://notchset.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/outcomes.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
- case studies, customer results, outcomes, before and after, ROI, social proof, customer stories, Notchset
- A results section for named customers
- Showing measured before/after impact

### Not when
- Quotes without numbers: use Testimonials
- A single long case study: write the page

## Mistakes
- Set each ruler's min and max so both values sit well inside it
- Publish only figures the customer approved

## Usage

```tsx
import { Outcomes, type CustomerOutcome } from "@/components/ui/notchset/blocks/outcomes";

export function Results({ customers }: { customers: CustomerOutcome[] }) {
  return <Outcomes customers={customers} />;
}
```

## Props

| Prop | Type | Default | What it does |
|---|---|---|---|
| `customers` | `{ id, name, industry, quote, person, role, scale, measures, steps, mark?, href? }[]` |  | measures: { label, before, after, min, max, prefix?, suffix?, decimals?, lowerIsBetter? }; steps: { when, text }. |

Full docs: https://notchset.dev/components/outcomes

## 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://notchset.dev/r/changelog.json

## Keyboard

| Keys | Action |
|---|---|
| ← → | Switch customer |
| Tab then Enter | Open how they did it, read the case study |

## Performance

- Plain DOM and CSS transitions.

## Responsive

- Under 760px (container width) the quote sits above the measures; tab labels stack under 560px.

## Motion inventory

| Interaction | What moves |
|---|---|
| Switch customer | Before dots and segments glide (620ms); the after dot settles with an overshoot (720ms) |
| Tabs | The underline stretches, its leading edge 80ms ahead |
| After values | Roll |

## Accessibility contract (preserve when editing)
- Customers are tabs (arrow keys move) controlling a labelled tab panel
- Every value is text in the table; the rulers are decorative
- HOW … DID IT is a button with aria-expanded

## Install

```bash
npx shadcn@latest add @notchset-pro/outcomes
```

Pro item: needs the `@notchset-pro` registry in `components.json` and `NOTCHSET_TOKEN` in `.env.local` (https://notchset.dev/account). Setup: https://notchset.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://notchset.dev/r/notchset-foundation.json.