Four seats and one dot, which travels between them and is pinched at its narrowest halfway.
The prompt11,620 characters
Add the "Radio" component from notboring to my project.
It is licensed for use in my projects — notboring.dev/license. Please:
1. Create the component at a sensible path for this
project, named Radio, from the source below.
2. It needs nothing beyond React.
3. Add the CSS to the project's stylesheet.
4. THE PART THAT NEEDS YOUR JUDGMENT. The CSS reads
these custom properties and does not define them:
--card
--font-ui
--ink
--ink-3
--ink-4
--ink-rgb
They are notboring's design tokens. Map each one to
whatever this project already uses for the same
job — its own ink, ground, surface and UI font —
rather than defining them as new globals. If the
project has no equivalent, define it locally on
the component's own root so nothing leaks out.
Anything ending -rgb wants three bare numbers,
because the CSS builds rgba() from it.
5. IF YOU CHANGE IT, GO ALL THE WAY. This block is
built for every state its object can really be
in — empty, one, full, refused, undone, pressed
twice, interrupted halfway — and not only the one
the demo opens on. Adapt it and the same standard
holds: work out that list before you write, and
build the whole of it. Never settle for the
minimum that makes the screenshot right. A
component somebody has to come back and finish is
the thing this was written to replace.
Keep the comments. They say why the numbers are what
they are, and they are most of what makes this worth
copying rather than rewriting.
--- Radio.tsx ---
import { useEffect, useRef, useState } from "react";
/* ══ Radio ════════════════════════════════════════════════
Four seats and one dot, which travels between them.
THE DOT DOES NOT TRAVEL. It did, between the rings, and it
was the wrong idea well executed: a radio group is four
seats where one is taken, and a single dot sliding between
them turns a state into a journey — you watch the ink
instead of reading the list, and the row you pressed is the
last thing you look at. The dot belongs to its own ring. It
scales in where it is chosen and out where it is not, which
is 200ms of nothing much, and that is right: the answer is
the list, not the animation.
WHAT MOVES IS THE HIGHLIGHT, and it moves because your
pointer does. One wash, traveling to the row under the
hand — the same single highlight the Select and the Menu
use, for the same reason: two washes crossing is never
mistaken for one thing moving. It fades where it stands
when the pointer leaves, because a highlight sliding out
to nowhere is a highlight pointing at nothing. */
const W = 280;
The rest — the source and its comments — is what the plan opens.