← Atlas · Topics: components, motion
Great UI
- Site
- great-ui.com
- Type
- component registry
- Verdict
- Niche
- Licence
- Conditional licence, source available
source-availablefree for personal and commercial projects under a custom "Great UI Custom License Agreement" that forbids reselling or republishing the components as a kit, template or derivative library; the README badge says MIT, which does not match the licence file - Agent channels
- registry
- Pricing
- free
- Reviewed
What it is
A copy-paste library of animated React components built with TypeScript, Tailwind CSS v4 and Motion by a solo developer, Saurabh Sharma. The registry held 50 items at review. Its most distinctive group is transitions: 11 page transitions (curtain, venetian blinds, sine wave, pixel swipe, cross blur and others) and 4 ways to animate a light and dark theme switch. The rest covers scroll-driven text, social profile cards, device mockups and small UI pieces. The repo started in July 2026, had about 230 stars at review, and ships new components every week or so according to its changelog. Blocks are marked "coming soon".
When to open it
When you want a route change or theme toggle to feel like an event, for example a curtain wipe between pages or a circular reveal when dark mode turns on. It is also a quick source of scroll-reveal text effects for a portfolio.
Most useful
- Staggered Page Transition: a dark, rounded documentation stage centers a white instruction line above four direction controls. Selecting one triggers a full-screen curtain of staggered panels; the preview exposes columns, duration, stagger and exit direction as props.
- Page transitions, from a simple staggered wipe to a canvas-drawn pixel swipe with dithered edges
- Theme transition providers (circular, split, swipe, blur fade) that animate the switch instead of snapping
- Scroll text effects: text on a path, word focus, blur reveal, split-line fly-in
- A pixel-to-ASCII image effect and a scrambled install-command snippet
Using it with agents
A standard shadcn index lives at /r/registry.json, with a description per item, and components install by URL with npx shadcn@latest add https://www.great-ui.com/r/<slug>.json. There is no llms.txt. Component pages render in the browser only, so an agent should read the registry JSON instead of scraping the docs.
Watch out for
- Licence mismatch: the README badge shows MIT, but the
LICENSEfile is a custom agreement that bans redistributing the code as a UI library or template - Some components are named after other libraries or brands (an "aceternity" button, LinkedIn, Facebook and Instagram cards); check trademarks before shipping look-alikes
- A one-person project a few months old; APIs may change between weekly releases
Reusable ideas
- Give a full-screen transition a stable demo stage, direction controls and tunable stagger/duration props so its timing and coverage can be reviewed before adoption.
- Treat the theme switch as a transition worth designing, not an instant swap
- Offer several page-transition styles behind one API so a site can change its mood without new plumbing
- Generate a per-component Markdown summary (install, dependencies, usage, props) from the same metadata as the docs
Related
Transitions.dev, React Bits, Aceternity UI, Skiper UI, Animate UI, Magic UI