Bones that travel to the width of the words about to land in them, and hand over in order.
The prompt13,117 characters
Add the "Skeleton" 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 Skeleton, 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-2
--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.
6. AVATARS is a stub
— notboring's own pictures are not licensed to
travel. Point it at this project's images, or
leave the placeholder and tell me.
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.
--- Skeleton.tsx ---
import { useEffect, useLayoutEffect, useRef, useState } from "react";
/* ══ Skeleton ═════════════════════════════════════════════
The shape of the thing that is coming, and the moment it
gives way to the thing itself.
THE BONES BECOME THE TEXT — THEY ARE NOT SWAPPED FOR IT. A
skeleton and its content are two different rectangles in
almost every implementation, and the swap is a jump: three
gray bars of arbitrary length disappear and three lines of
real text of different lengths appear. Here each bone
travels to the width of the words that are about to land in
it, and only then hands over. The line that was a quarter
too long visibly shortens, which is the one honest moment
in the whole idea: the guess was a guess, and you watch it
be corrected.
THE WIDTHS ARE MEASURED, NOT GUESSED. The real text is in
the DOM the whole time, invisible, so the bone's target is
the actual width of the actual sentence in the actual font.
Nothing here is a percentage that looked right once.
THEY GIVE WAY IN ORDER, TOP TO BOTTOM, 70ms apart — the way
a page paints, and the way an eye reads.
The rest — the source and its comments — is what the plan opens.