Skip to content

Docs

Introduction

DavinciUI is a collection of animated React components you add to your own codebase. There is no runtime package to install and no version to upgrade — the shadcn CLI copies component source into your project, and from that point the code is yours to read, edit, and maintain.

What DavinciUI is#

DavinciUI follows the shadcn open-code model: instead of shipping a JavaScript bundle, it ships readable component source. You pick a component, the CLI writes its files into @/components/ui, and you import it like any file you wrote yourself.

  • Stack: React 19, Tailwind CSS v4, Framer Motion for animated components, and the shadcn CLI for installs.
  • Who it is for: developers building marketing sites, dashboards, or product UI who want polished motion without adopting a heavyweight component framework.
  • What you own: the full source of every component you add, its styles, and its behavior — including the right to modify or delete anything.

If you are new to this model, read how the registry works before installing.

Quick start#

From an existing React project with shadcn initialized, one command adds a component:

pnpm dlx shadcn@latest add @davinciui/text-morph

Then render it from where the CLI placed it:

import { TextMorph } from "@/components/ui/text-morph"

export default function Page() {
  return <TextMorph words={["Design", "Animate", "Delight"]} />
}

Tip

First time here? Start with Installation for prerequisites, and Configuration for aliases and registry setup.

How it works#

  • Registry: every component is a JSON item at davinciui.com/r/[name].json describing its files and npm dependencies.
  • Install: the CLI resolves @davinciui/[slug], downloads the files, and writes them into your repo.
  • Ownership: installed files are plain project files. They do not update automatically and do not phone home — re-run the add command to pick up a newer version.

This is the key difference from a traditional package: installing a component is a one-time copy, not an ongoing dependency. Your bundle includes only the code you added, and debugging means reading your own files.

Documentation map#

  • Getting Started — install, configure, theme, and drive the CLI.
  • Components — the catalog: previews, install commands, source, and props per component.
  • Foundations — colors, typography, spacing, radius, shadows, motion, and the other design tokens components are built on.
  • Registry — the distribution model: items, namespaces, updates, and troubleshooting.
  • Skills — teach your AI assistant DavinciUI so it installs and composes components for you.
  • MCP — connect the registry to your AI coding assistant.

Press ⌘K to search anything.