Hosting
No registry to run.
Publish uploads your files once. Catalogs serves them to every agent that asks, with your guide and your license alongside, and to the shadcn CLI in the registry form it expects.
For makers
Ship components without running a registry.
You write the component. Catalogs hosts the files, shows them working, and gets them to people through their coding agent. Catalogs takes care of hosting and presentation, so you can focus on your work.
my-components/
├ catalogs.yaml your team, your license├ catalog/items/│ ├ pricing-table.item.yaml│ ├ bar-chart.item.yaml│ └ card-grid.item.yaml└ src/components/ ├ pricing-table.tsx ├ bar-chart.tsx └ card-grid.tsx
$ ctlgs publish3 items · live on catalogs.dev/you
What you skip
Everything that is not the component.
Sharing a component today means standing up a registry, writing a docs site, and telling people it exists. Catalogs takes those three off your plate, and leaves the part that is yours.
Docs
No site to build.
Your item page shows the component working, the props, and what it needs. A short guide in plain words is the whole documentation.
Reach
Get discovered through Catalogs.
Put your work in reach of people exploring possibilities with their coding agents. They can see what you’ve made and choose it for their projects.
What you keep
Your code, your license, your name.
The catalog manifests live in your repo and describe what you publish. Rename an item and the old address forwards. Remove one and its previews stay safe until you say otherwise. Already have a shadcn registry? Keep it, and Catalogs points at it instead of hosting the files. Either way your items answer the shadcn CLI as well as an agent.
youClaimed · 3 items · MIT
Pricing table
Bar chart
Card grid
How it works
Your agent does the paperwork.
Once you are in, the setup is a phrase you paste into your coding agent. It creates the catalog, describes each component from the code, and publishes when you say so.
01 · Connect
Your agent joins Catalogs.
One phrase from your welcome page, and your agent is signed in as you.
02 · Describe
It writes the catalog from your code.
A file per component: what it is, what it needs, where the demo lives. You read it and fix the words you want changed.
03 · Publish
One command, and it is findable.
Publish shows the plan, you confirm, and your page is live with previews. Change the code, publish again.
During the beta
Publishing is invite only.
Send a link to the component and a sentence about it. Every application is read by a person.