What ships next

The package is written, versioned and documented, and the name is still unclaimed on the public registry — so every `npx hoverlab` line in the docs currently describes something you cannot yet install. This is the single most consequential unfinished thing on the list, and it is blocked on publishing rather than on building.

A VS Code, Cursor and Windsurf sidebar over all five tiers exists in the repository and contributes the MCP server so agent mode needs no config file. It cannot be packaged for the marketplace until the CLI above is on npm, because every write it performs is delegated to that binary.

Today we publish frames — flat, pixel-accurate, and not a component library. Preline and Flowbite both give theirs away, and `/compare` records it as the row we lose outright. Turning frames into components with variants and tokens is the work, and it is genuine design work rather than a generator.

The page is built and deliberately empty. It fills up one verified entry at a time, and it will not be seeded with our own deployments wearing customers’ names.

Addresses are collected, the sequences are written and reviewed in the repository, and the digest is composed from the same git-derived ledger the changelog and the feed use. What is missing is a sending key, which is a dashboard decision rather than a build.

Aceternity sells a private room as a feature of its licence, and `/compare` concedes the point: published response targets are not a substitute for people who already solved your problem. Opening one is easy; keeping one alive is not, which is why it is here and not above.

Shadcnblocks sells these at $379 each, which says the demand is real. Whether it is real for a catalog whose pages are already plain React files that a developer can paste anywhere is the open question.

21st.dev ships one. We already run our own design rules against our own code in the CLI, so pointing them at somebody else’s diff is a smaller step for us than for most — but a reviewer that is wrong is worse than no reviewer, and that bar is high.

A single CSS hover state, a React control, a page section, a whole route, a scaffoldable project. Every rung installs the same way and composes with the one below it.

The whole catalog under the @hoverlab namespace, installable with the shadcn CLI. Supports dynamic search on the registry index itself.

Search and install as agent tools, plus packaged skill files that teach an agent this catalog’s conventions. Free, with no key.

Unauthenticated, CORS-open, no key. Search and resolve any artifact on any rung, and read the design tokens behind it.

Accent, neutrals, typeface and corner radius, applied to the whole catalog at once and exported as nine lines of CSS or a shadcn theme.

Compose a page from blocks and export it. Entirely URL-driven, so a composition is a link you can send someone.

Emit artifacts as plain HTML, Vue, Svelte and Astro rather than assuming everyone is on React.

Animated icons, seeded avatars, invented company logos and isometric illustrations. No account, no attribution, outside the licence entirely.

Machine-checked WCAG 2.2 results for every artifact, published including what fails. Regenerated on every build, so it cannot drift from the catalog.

Logical properties throughout, an icon ledger that fails the build when a directional icon is not mirrored, and an RTL preview on every artifact.

What you get when something breaks, by plan, stated as business-day targets from a small team rather than dressed up as an SLA.

Four bands plus a rupee price for India that is charged in rupees rather than converted. The discount is decided server-side from the request, so it cannot be claimed by anyone it is not for.

Asked for often, and the answer is no. A marketplace is a moderation, payouts and tax problem that happens to have components in it, and doing it badly would damage the catalog that pays for everything. `/for-authors` says the same thing in the first email rather than after three.

React Bits’ builder does this and ours will not. The moment a builder owns your content it owns your project, and the whole proposition here is that what you install is plain source you keep. Export it and edit it in your editor, where your version control is.

Recurring revenue would buy a bigger roadmap — 21st.dev’s entry in `/compare` says exactly that, and it is true. It would also mean the thing you bought stops working when you stop paying, which is the opposite of what a one-time licence on MIT source is for.