Own product · In production
A personal frontend kit: the full set of stock shadcn components, an authored library of blocks and template pages on top of it, and a gallery to preview all of it. The kit sits on disk next to the project rather than being installed from a remote registry.
The pain
Every new screen started from nothing: its own components, colours and spacing. A block that worked did not travel to the next project - it was nailed to its own theme.
Now
A library of authored sections and template pages on top of stock shadcn components. A block transfers as a file: data arrives through props and the colour comes from the receiving app’s theme.
A description of a screen is first matched to the nearest of some two hundred reference pages and only then assembled from blocks: that way the screen has a model to follow rather than only an idea of one.
The layers are kept strictly apart: stock components are never customized, authored blocks take data through props only and never import fixtures, and template pages own their data. Customization is blocks and pages, never an edit to the stock layer.
Token discipline is not a matter of taste but the condition of portability: a block with a raw colour inside stays foreign in someone else’s theme. So the ban is enforced by a separate command over blocks and pages, while the stock layer is exempt.
The primitives here are Base UI, not Radix, and a separate warning says so: examples from training data are almost always Radix. A button rendered as a link without the right flag only complains in a live browser - neither types nor the linter will catch it.
The kit is not installed from a remote registry: it lies on disk nearby, and Claude Code reads the block source and carries it into the project by the recipe - reinstalling the stock components on the receiving side. What is published as an open registry is something else - this site’s theme and components: the showcase behind the link shows them live, while a machine reads them at /r/registry.json.
Me. The kit repository is private; what is open is this site’s showcase of the theme and the components - it carries the install command too.
Internal system · In production
Management finance loop
The same system pays off across 3 more steps
Internal system · In production
Product portal
The same system pays off across 2 more steps
Open source · In production
Starter application template
two of the three systems - on the day of the first commit
The same system pays off on one more step
Open source · In production
Deploy from chat
