You are fine, and you keep saying so.
Sleep comes late and leaves early.
The thing you enjoyed has become a task.
You rehearse conversations that never happen.
Rest feels like something you have to earn.
You have been meaning to call someone for months.
Recognising the pattern is most of the first session. You have already started.
A self-recognition list: a sticky column with a serif heading that settles in word by word, an intro and a pill action, beside ruled serif statements that each blur in as they reach the viewport, marked with a small ringed check, and a closing line beneath.
A recognition checklist: a sticky column of heading, intro and pill beside ticked statements set at serif size, closed by a line that names what recognising them means.
Upgrade to Pro
Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.
Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.
Radix flavor
npx shadcn add "https://ui.beste.co/r/usecase55?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/usecase55?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/usecase55.tsx plus the button22 sliding-marker pill and the text1 word stagger it uses.
The installed file exports usecase55Demo alongside the block: the exact props behind the preview above. Spread it to get a working checklist section in one line.
import { Usecase55, usecase55Demo } from "@/components/beste/block/usecase55";
export default function Page() {
return <Usecase55 {...usecase55Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Usecase55 } from "@/components/beste/block/usecase55";
export default function Page() {
return (
<Usecase55
eyebrow="Is this you"
heading="If three of these sound familiar, it is probably time."
description="None of them is a crisis. Together they are a pattern."
button={{ label: "Talk it through", href: "/call", tone: "dark" }}
statements={[
"You are fine, and you keep saying so.",
"Sleep comes late and leaves early.",
"Rest feels like something you have to earn.",
]}
closing="Recognising the pattern is most of the first session."
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
eyebrow | string | – | Small-caps line above the heading |
heading | string | – | Section heading, rendered as an h2 through Text1 |
description | string | – | Intro in the sticky column |
button | ActionButton | – | Pill action under the intro |
statements | string[] | [] | Ticked statements, in the order given |
closing | string | – | Line printed under the list |
className | string | – | Extra classes for the outer <section> |
type ActionButton = {
label: string;
href: string;
tone?: "primary" | "light" | "dark" | "outline";
};ol, so the order is real; the ticks are decorative marks inside it rather than checkboxes, since nothing here is interactive.0.1s delay rather than a growing stagger, so a list of six does not leave the last line arriving seconds after the reader gets there.-15% viewport margin than the header, so a statement settles once it is properly inside the reading area.size-7 circle with shrink-0 and a mt-1 nudge, so a statement that wraps keeps its mark on the first line.md:sticky md:top-28 and returns to normal flow below md, where a sticky column would cover the list.closing sits outside the ruled list, so the section ends on a sentence rather than on another rule.