I built a 100% free, open-source shadcn registry of PDF components for React.
Features:
Give it a ⭐ on GitHub: https://github.com/shadcn-labs/pdfcn
I built a 100% free, open-source shadcn registry of PDF components for React.
Features:
Website: https://pdfcn.dev
Give it a ⭐ on GitHub: https://github.com/shadcn-labs/pdfcn
I built a 100% free, open-source shadcn registry of email components for React.
Features:
Website: https://emailcn.run
Give it a ⭐ on GitHub: https://github.com/shadcn-labs/emailcn
I built a 100% free, open-source shadcn registry of email components for React.
Features:
Website: https://emailcn.run
Give it a ⭐ on GitHub: https://github.com/shadcn-labs/emailcn
I built a 100% free, open-source animated icon library for React.
Website: https://heroicons-animated.com
Give it a ⭐ on GitHub: https://github.com/heroicons-animated/heroicons-animated
Still can't believe a project I started just 4 months ago has crossed 1k+ ⭐️ on GitHub.
Thank you all for the incredible support, it truly means a lot. ❤️
Big updates for termcn are dropping next week. Trust me, you're going to love what's coming.
Been exploring MCP apps lately and noticed that building polished interfaces for ChatGPT, Claude, and other MCP-powered apps still means wiring up layouts, primitives, and interaction patterns from scratch.
So I built mcpcn 🔌 — a shadcn/ui-style registry for building MCP app interfaces.
Some of the features:
If you're building ChatGPT/Claude/MCP apps, this should make the UI side a lot less painful.
GitHub: https://github.com/shadcn-labs/mcpcn
Docs: https://www.mcpcn.dev
Over the past few weeks, I've seen more teams adopt StyleX.
Linear shared how they're migrating to StyleX, and Polar is building their next-generation design system with it.
That made me realize there wasn't a familiar shadcn/ui experience for people making the switch.
So I built shadcn-cssinjs.
Some of the features:
100% free and open source.
It's still early, and I'm planning to port more components over time. I'd love to hear your feedback, especially if you're already using or thinking about using StyleX.
GitHub: https://github.com/shadcn-labs/shadcn-cssinjs
Docs: https://shadcn-cssinjs.com
Over the past few weeks, I've seen more teams adopt StyleX.
Linear shared how they're migrating to StyleX, and Polar is building their next-generation design system with it.
That made me realize there wasn't a familiar shadcn/ui experience for people making the switch.
So I built shadcn-cssinjs.
Some of the features:
100% free and open source.
It's still early, and I'm planning to port more components over time. I'd love to hear your feedback, especially if you're already using or thinking about using StyleX.
GitHub: https://github.com/shadcn-labs/shadcn-cssinjs
Docs: https://shadcn-cssinjs.com
A few weeks ago, I launched agentcn with support for Eve and Flue.
The goal was simple: make production-ready AI agent recipes as easy to install as shadcn/ui components.
Since then, a lot of people have asked for Mastra support. So I spent the last few weeks porting the entire catalog.
Today, agentcn supports Mastra with 19 production-ready recipes, bringing the registry to 57 recipes across Eve, Flue, and Mastra.
A few weeks ago, I launched agentcn with support for Eve and Flue.
The goal was simple: make production-ready AI agent recipes as easy to install as shadcn/ui components.
Since then, a lot of people have asked for Mastra support. So I spent the last few weeks porting the entire catalog.
Today, agentcn supports Mastra with 19 production-ready recipes, bringing the registry to 57 recipes across Eve, Flue, and Mastra.
GitHub: https://github.com/shadcn-labs/agentcn
Docs: https://www.agentcn.run
I found myself bookmarking a ton of great shadcn-related content every week — new components, libraries, tutorials, and interesting projects.
So I decided to turn it into a simple weekly email.
The first issue goes out on July 13.
If that sounds useful, you can subscribe here: https://shadcnweekly.com
And if there’s anything you’d especially like to see covered, I’d love to hear it.
introducing Shadcn Weekly
the best links from the shadcn ecosystem, in one email
news, tutorials, projects, tools
100% free, every Monday, no fluff
issue #1 goes live july 13
subscribe → https://shadcnweekly.com
A few days ago, I shared that framecn got a dedicated collection of typography components.
Yesterday, Paper open-sourced their new shaders library, and the effects were so good that I knew they had to be available as framecn components for creating insane launch videos.
I've now added all 18 shader components to framecn, so you can use them out of the box in your own projects.
GitHub: https://github.com/shadcn-labs/framecn
Docs: https://www.framecn.dev
A few weeks ago, I shared that framecn got a dedicated collection of caption components.
While working on those, I realized captions were just one piece of the puzzle. Product videos, demos, and tutorials also rely heavily on animated text effects to make intros, feature highlights, and transitions feel more engaging.
So I spent the last few days building a dedicated collection of typography components for framecn.
framecn now includes 15+ typography components out of the box, including Typewriter, Matrix Decode, Blur Reveal, Tracking In, Infinite Marquee, RGB Glitch Text, and more.
GitHub: https://github.com/shadcn-labs/framecn
Docs: https://www.framecn.dev
A few days ago I came across Eve on X, a filesystem-first framework for building AI agents that feels a lot like Next.js and deploys directly to Vercel Functions.
While exploring it, I also found Flue, an open agent framework powered by Pi, the open agent harness.
After playing around with both for a bit, I realized they'd fit really nicely into the shadcn/ui ecosystem, so I built agentcn.
Some of the features:
It's still early days and only has a handful of recipes right now, but I'm planning to add more. I'd love to hear any feedback, especially from people already building with Eve or Flue.
GitHub: https://github.com/shadcn-labs/agentcn
Docs: https://agentcn.run
A while back I launched ogimagecn - a shadcn/ui-style registry for Open Graph images built with Satori.
With so many shadcn registries popping up lately, I spent the last few days building a dedicated collection of OG image components tailored specifically for registry authors.
GitHub: https://github.com/shadcn-labs/ogimagecn
Docs: https://www.ogimagecn.com
A few days ago I came across eve on X, a filesystem-first framework for building AI agents that feels a lot like Next.js and deploys directly to Vercel Functions.
While exploring it, I also found Flue, an open agent framework powered by Pi, the open agent harness.
After playing around with both for a bit, I realized they'd fit really nicely into the shadcn/ui ecosystem, so I built agentcn.
Some of the features:
It's still early days and only has a handful of recipes right now, but I'm planning to add more. I'd love to hear any feedback, especially from people already building with Eve or Flue.
GitHub: https://github.com/shadcn-labs/agentcn
Docs: https://agentcn.vercel.app
Over the last few months I've launched a handful of shadcn registries, and one thing became pretty clear:
Building the registry is usually the easy part.
The harder part is everything that comes after which is validating the registry, submitting it to directories, getting listed in awesome lists, writing launch posts, and generally figuring out where and how to share it.
After repeating the same process multiple times, I decided to turn it into an open-source skill called launch-shadcn-registry.
Given a registry, it helps with:
The goal is simple: make launching a shadcn registry as straightforward as building one.
Skill: https://www.skills.sh/shadcn-labs/skills/launch-shadcn-registry
GitHub: https://github.com/shadcn-labs/skills/tree/main/skills/launch-shadcn-registry
Over the last few months I've launched a handful of shadcn registries, and one thing became pretty clear:
Building the registry is usually the easy part.
The harder part is everything that comes after which is validating the registry, submitting it to directories, getting listed in awesome lists, writing launch posts, and generally figuring out where and how to share it.
After repeating the same process multiple times, I decided to turn it into an open-source skill called launch-shadcn-registry.
Given a registry, it helps with:
The goal is simple: make launching a shadcn registry as straightforward as building one.
Skill: https://www.skills.sh/shadcn-labs/skills/launch-shadcn-registry
GitHub: https://github.com/shadcn-labs/skills/tree/main/skills/launch-shadcn-registry
