An application whole, drawn small: the rail, and the page set into it like a porthole.
The prompt16,961 characters
Add the "Shell" 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 Shell, from the source below.
2. Install what it needs: npm i framer-motion lucide-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
--ground
--ink
--ink-2
--ink-3
--ink-4
--ink-5
--ink-rgb
--on-ink
--pane-edge
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.
--- Shell.tsx ---
import { useEffect, useLayoutEffect, useRef, useState } from "react";
import { AnimatePresence, motion, useSpring } from "framer-motion";
import { Bell, ChevronRight, Folder, Home, Inbox, Search, Settings, type LucideIcon } from "lucide-react";
/* ══ Shell ════════════════════════════════════════════════
An application, whole and small: the rail, the bar, and
the page — and the page is a card you look through.
THE PAGE IS A PORTHOLE. The rail is the window's own
surface, edge to edge on the left; the page is a card set
in from the top, the right and the bottom by eight pixels,
rounded on all four corners, so the rail seems to hold it
the way a frame holds a photograph. A page that runs to
the window's edges reads as the window; a page with air
around it reads as content in a place, which is what a
dashboard is.
Everything is the size it would be seen from across the
room: eleven-pixel type, thirty-pixel rows. This block is
the grammar — take the full-size pieces from their own
blocks — and the one thing that moves is the thumb in the
rail, while the page crossfades in place with a 6px rise
and the trail's last word rolls to match. */
The rest — the source and its comments — is what the plan opens.