Ruixen UI is the largest single-author set in the catalogue at 382 public components, which puts it in a different category from a registry with forty. That size is the story: it is not a curated shelf, it is a working library, and the way to use it is to search it rather than to browse it.
The strongest pieces
CardStack is a 3D card stack with fan-out, drag gestures and auto-advance, and it is the most-taken component in the set. Coverflow Carousel and Gallery Hover Carousel are the other two rails, all three covered in the carousel guide.
Stack Feature Section, IntegrationHero and Globe Feature Section are the marketing blocks, and ScrollTiltedGrid and Image Stream Hero are the scroll-driven ones.
The parts that are harder to find elsewhere
A set this size covers the unglamorous middle that most registries skip.
Smart Breadcrumb collapses the middle of a long trail, which is the only part of a breadcrumb that needs a component, per the breadcrumb guide. Wheel Pagination and Notifications Filter are the product pieces, Heatmap Calendar and Monthly Heatmap Calendar cover the contribution-graph shape, and RuixenContributorsTable is a real data table.
Feature Accordion Section, Progressive Flux Loader and Arc Preloader Hero round out the set.
How to use a set this large
Three habits, and they are the same ones the ReUI guide recommends for a large general registry.
Search, do not browse. Three hundred and eighty components is a catalogue, and scrolling it is the wrong interaction. Search by what the screen needs.
Take components, not the set. There is no benefit to adopting a large set wholesale, and there is a cost: four components from one author share an aesthetic, forty share a bundle.
Check each one's dependencies. In a set this size the components differ from each other. The scroll and 3D pieces bring more than the breadcrumb does, and the component page lists what installs alongside it.
Where else to look
The honest list, because the answer is not always us:
| Source | Best for | Trade-off |
|---|---|---|
| The registry directory | Comparing registries by size, stars and last commit | Only registries that publish an index |
| ReUI | The largest general registry, for product surfaces | Large enough that browsing is the wrong approach |
| shadcn/ui | The primitives underneath | Deliberately small |
| 21st | This set with previews, searchable beside everything else | Quality varies by author, so preview before you take it |
Taking one
Every component page has a live preview and the code. Installing goes through the shadcn CLI against our registry:
That key comes from your 21st account, and installs require a membership. Set API_KEY_21ST once in your shell and the command works for anything in the catalogue.
Frequently asked
- How do you use a set of nearly four hundred components?
- Search it rather than browse it, take individual components rather than adopting the set, and check each one's dependencies separately, because in a set that size the scroll and 3D pieces bring far more than the breadcrumb does.
- What is worth taking from Ruixen UI?
- The rails, since CardStack and Coverflow Carousel are among the better answers to a carousel in a narrow column, and the unglamorous middle: a breadcrumb that collapses long trails, heatmap calendars, a real contributors table and a notifications filter, which most registries skip.
- Is a large author set the same as a large registry?
- In practice yes: both are catalogues rather than curated shelves, and both reward search over browsing. The difference is that one author's set is more likely to share a visual language than a registry assembled from many contributors.
- Should you adopt a large set wholesale?
- No benefit, and a real cost. Four components from one source share an aesthetic; forty share a bundle. Take what the screen needs and leave the rest, which is the same advice the long-tail guide gives for small registries.