cult-ui: Open-source animated components for shadcn/ui projects.
What problem it solves
Design engineers need animated interface components that can be added to existing shadcn/ui projects without relying on a packaged component dependency. Cult UI addresses this by distributing components as registry items whose source is copied directly into the project.
Key features
Source-owned components — Components are installed as shadcn/ui registry items, and the CLI copies their source into the project so the code remains under the project's ownership.
Source: README
Tailwind and Motion integration — Components use Tailwind CSS v4 and shadcn theme tokens, while most components animate with Motion. Each component documentation page lists its dependencies.
Source: README
Agent-readable documentation — Documentation is prepared for both people and coding agents, with page indexes, a combined documentation file, Markdown pages, and an MCP server for searching and installing components.
Source: README
Quick start
Copied verbatim from the project's README.
npx shadcn@latest add @cult-ui/shift-cardWho it may suit
This may suit design engineers and developers building shadcn/ui projects who want source-controlled animated components. It may also suit teams using AI-assisted coding tools that can search and install components through the documented MCP server.
Topics to discuss
Which animated component categories should the library prioritize next?
How can component ownership and customization be improved after CLI installation?
What contribution workflow would make new components easier to document and maintain?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/nolly-studio/cult-ui#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…