Introduction

How components work

Each component lives on its own page with a live preview, its props, and its full source. There is no package to install and no version to track: the CLI copies the file into your project, so from that point on it is your code to read, change, or delete.

Components read their colors and easing curves from a small set of tokens, so they need a one-time theme setup in your project before the first one is added.

Installation

Once the theme is set up, add any component with its shadcn command, swapping in that component's name:

Working with a coding agent? See the agent guide for the MCP server, an installable skill, and the machine-readable endpoints.

The stack

• Next.js 16 and React 19 The site and every component.
• Tailwind CSS v4 Utility classes plus the color and easing tokens components read from.
• Motion For gestures, layout animation, and shared transitions where CSS alone isn't enough.
• TypeScript Every component ships a documented props interface.
• Bun Package management, the dev server, and the test runner.

Why it exists

Most component libraries ship as a package you import and can't easily change. easeUI ships through the shadcn CLI instead, so every component lands in your own repo, in your own style, ready to edit.

The animations follow one small set of rules everywhere: animate transform and opacity, ease out fast, and turn everything off under reduced motion. See CONTRIBUTING.md for the full list.