Nothing yet, the one thing to do about it, and a list you can go on filling — three at a time, each one undoable.
The prompt27,510 characters
Add the "Projects" 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 Projects, 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
--danger
--danger-rgb
--font-ui
--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.
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.
--- Projects.tsx ---
import { useEffect, useRef, useState } from "react";
import { AnimatePresence, motion } from "framer-motion";
import { Folder, Plus } from "lucide-react";
/* ══ Projects ═════════════════════════════════════════════
A list that starts with nothing in it, and every step
between nothing and three.
AN EMPTY STATE IS THE FIRST STEP, NOT A PICTURE OF NONE.
A line that says what is missing, a line that says what it
costs to fix, and the button that fixes it. No illustration
of an empty box: the card is the empty box. Press the
button and the same card becomes the field that takes the
name, and then the list with its first row — three states
of one object, crossfading in place, never three pages.
AND IT DOES NOT STOP AT ONE. That was the whole fault of
this block before: it demonstrated the step out of empty
and then sat there, a list of one with nowhere to go, which
is a screenshot of a transition rather than a component.
A list that can be filled has to be fillable — so the head
carries a plus from the moment there is anything to add to,
and the row you are naming OPENS IN THE LIST, at the end,
where the project will be. The field and the finished row
The rest — the source and its comments — is what the plan opens.