Skip to content

Docs

Skills

Teach your AI assistant DavinciUI once — then stop pasting docs links. The skill gives assistants like Claude Code project-aware context about every animated component, so you describe the outcome in plain words and it finds, installs, and composes the right pieces with the correct APIs for your project.

Install the skill#

One command installs the DavinciUI skill into your project. Your assistant loads it automatically whenever you work with components:

# pnpm
pnpm dlx skills add https://github.com/sorkhademanthan/davinciui --skill davinciui

# npm
npx skills add https://github.com/sorkhademanthan/davinciui --skill davinciui

# yarn
yarn dlx skills add https://github.com/sorkhademanthan/davinciui --skill davinciui

# bun
bunx --bun skills add https://github.com/sorkhademanthan/davinciui --skill davinciui

Success looks like: a davinciui skill in your agent's skills list. From then on, just ask — no setup per conversation.

Tip

You can also browse and verify the skill source on skills.sh. The skill file itself lives at skills/davinciui/SKILL.md in the DavinciUI repo — readable, forkable, yours to inspect.

What your assistant learns#

The skill is a compact briefing your assistant reads before it writes code. Here is what is inside:

  • Project context. On every task it runs shadcn info --json to read your components.json — framework, Tailwind version, aliases, icon library, installed components, and resolved file paths. Code lands in the right folder the first time, not the assumed one.
  • CLI commands. The full workflow — add, view, search, docs — including dry-run inspection before installing and --overwrite when you want a newer registry version. See CLI.
  • Theming and composition rules. Semantic tokens over hardcoded colors, dark-mode pairs for every override, transform-and-opacity motion, and how DavinciUI pieces compose with your existing shadcn/ui primitives. See Theming.
  • Registry awareness. Every component is a registry item under the @davinciui namespace with declared files and dependencies — so the assistant installs framer-motion or lucide-react when the item needs it, instead of guessing. See Registry.

Try it#

With the skill installed, prompts like these just work — copy one into your assistant:

Landing hero

"Add a landing hero with a plasma background and a text-morph headline."

Animated section

"Add a stats section with count-up cards and a scroll reveal."

Polish an existing page

"Add a magnetic button and a cursor trail to my pricing page — keep my theme tokens."

The assistant will view or search the registry, show you what it plans to add, then run add @davinciui/… and wire up the import — respecting your aliases and theme.

How it works#

  • Project detection. The skill activates when it finds a components.json file — that is how it knows you are in a shadcn-style project.
  • Context injection. It reads your project configuration into context, so generated imports, paths, and dependency installs match your setup instead of a generic template.
  • Discovery before code. It checks the registry — search, view, component docs — before writing anything, so it never hand-rebuilds a component from memory.
  • Your code, your rules. Installing is a one-time copy into your repo. The assistant edits your files like any teammate would — nothing updates silently, and everything is reviewable in git.

Skills vs MCP vs llms.txt#

DavinciUI meets assistants three ways. Pick the one that matches how you work:

  • Skills (this page) — best for everyday building. Procedural knowledge baked into the agent: which command to run, where files go, how to theme. Install once, benefit forever.
  • MCP server — best for live registry access. Lets a connected agent search, browse, and install components directly from the registry during the session.
  • llms.txt — best for lightweight or offline-capable assistants. The whole registry as plain text at davinciui.com/llms.txt — paste it, or point any assistant at it, no integration needed.

Info

Skills and MCP complement each other: the skill teaches the workflow, MCP provides the live catalog. Install the skill first; add MCP when you want the agent to browse the registry itself.

Troubleshooting#

  • Assistant ignores your aliases — the skill could not read components.json. Make sure you ran shadcn init and the file sits at the project root.
  • Wrong component installed — slugs are exact and kebab-cased. Ask the assistant to view the candidate first, or copy the slug from the Components page.
  • Skill not loading — confirm it appears in your agent's skills list after install, then restart the session. Skills load at session start.