Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

ai-elements · vercel — Claude Code skill: AI chat components, how to install

React component library for AI interfaces: messages, conversation history, prompt inputs, tool call displays. Built on shadcn/ui.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vercel/ai-elements --skill ai-elements -a claude-code
Open on GitHub

What ai-elements does

The skill adds ready-made components like Message, MessageContent, MessageResponse for building AI assistant chat interfaces fast. Component code lands in @/components/ai-elements/ — you see the full implementation, can edit Tailwind CSS styles and logic directly in the files. Integrates with useChat from AI SDK.

Requires Node.js 18+, Next.js with AI SDK installed, and shadcn/ui (if shadcn/ui is missing, the CLI installs it automatically). Vercel recommends using AI Gateway with AI_GATEWAY_API_KEY in .env.local — gives $5 free model usage per month, no separate provider keys needed.

Components extend standard HTML attributes (Message extends HTMLDivElement), so further customization is straightforward — pass any props you'd pass to a div.

What it helps with

  • build an AI chat interface without coding UI from scratch
  • display conversation history with user and assistant roles
  • show tool calls and their results in chat
  • customize message component UI to match the project
  • integrate AI SDK with a ready visual layer

Example prompts for the agent

  • Add a chat interface using `ai-elements` components
  • Use `Message` and `MessageContent` to display conversation history
  • Install `ai-elements`: `npx skills add vercel/ai-elements --skill ai-elements -a claude-code`

How to install ai-elements

1Skills CLI (Vercel)

npx skills add vercel/ai-elements --skill ai-elements -a claude-code

2Manually: put the files in place

~/.claude/skills/ai-elements/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ai-elements/

Other versions of ai-elements

Similar

core vercel-labs Defines the schema and component catalog for json-render and builds the system prompt that makes an AI emit JSON UI specs. Claude Code CX Codex Cursor +1 15,000installs winui-app official openai This skill helps create, configure, and review WinUI 3 apps built with C# and the Windows App SDK. Use it for new projects or XAML issues. Claude Code CX Codex Cursor +1 3,200installs text-to-lottie diffusionstudio Generates, edits, and debugs Lottie JSON animations for the local Skia Skottie player. Helps create UI microinteractions, loaders, and animated charts. Claude Code CX Codex Cursor +1 10,600installs markdown-to-html official github This skill guides Markdown-to-HTML conversion and custom conversion scripts. Use it for HTML documentation, static sites, or rendering .md files for preview. GitHub Copilot 9,899installs shadcn-svelte huntabyte A skill for working with shadcn-svelte: adding components, building interfaces, fixing styles, and debugging projects. Use it if you're building UI with shadcn-svelte on Svelte or planning to start. Claude Code CX Codex Cursor +1 6,700installs motion-design LottieFiles This skill guides UI animation choices, from timing and easing to choreography. Use it when planning micro-interactions, loading states, or page transitions. Claude Code CX Codex Cursor +1 19,700installs frontend-design official anthropics This skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. Claude Code Claude.ai 1,025,790installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. Claude Code CX Codex Cursor +1 673,100installs

Questions about ai-elements

How to install ai-elements in Claude Code?

Run npx skills add vercel/ai-elements --skill ai-elements -a claude-code in the project root. The skill will appear at ~/.claude/skills/ai-elements/SKILL.md.

What does ai-elements do?

Adds React components for AI chat interfaces to your project: messages with roles, input fields, tool call displays. Component code is copied into your project, so you can modify styles and logic.

Does ai-elements require shadcn/ui?

Yes, ai-elements is built on top of shadcn/ui. If shadcn/ui is not installed, the CLI installs it automatically when you add the skill.

Source text

SKILL.md · Apache-2.0
---
name: ai-elements
description: Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
---

# AI Elements

[AI Elements](https://www.npmjs.com/package/ai-elements) is a component library and custom registry built on top of [shadcn/ui](https://ui.shadcn.com/) to help you build AI-native applications faster. It provides pre-built components like conversations, messages and more.

Installing AI Elements is straightforward and can be done in a couple of ways. You can use the dedicated CLI command for the fastest setup, or integrate via the standard shadcn/ui CLI if you've already adopted shadcn's workflow.

> **IMPORTANT:** Run all CLI commands using the project's package runner: `npx ai-elements@latest`, `pnpm dlx ai-elements@latest`, or `bunx --bun ai-elements@latest` — based on the project's `packageManager`. Examples below use `npx ai-elements@latest` but substitute the correct runner for the project.

## Prerequisites

Before installing AI Elements, make sure your environment meets the following requirements:

- [Node.js](https://nodejs.org/en/download/), version 18 or later
- A [Next.js](https://nextjs.org/) project with the [AI SDK](https://ai-sdk.dev/) installed.
- [shadcn/ui](https://ui.shadcn.com/) installed in your project. If you don't have it installed, running any install command will automatically install it for you.
- We also highly recommend using the [AI Gateway](https://vercel.com/docs/ai-gateway) and adding `AI_GATEWAY_API_KEY` to your `env.local` so you don't have to use an API key from every provider. AI Gateway also gives $5 in usage per month so you can experiment with models. You can obtain an API key [here](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%2Fapi-keys&title=Get%20your%20AI%20Gateway%20key).

## Installing Components

You can install AI Elements components using either the AI Elements CLI or the shadcn/ui CLI. Both achieve the same result: adding the selected component’s code and any needed dependencies to your project.

The CLI will download the component’s code and integrate it into your project’s directory (usually under your components folder). By default, AI Elements components are added to the `@/components/ai-elements/` directory (or whatever folder you’ve configured in your shadcn components settings).

After running the command, you should see a confirmation in your terminal that the files were added. You can then proceed to use the component in your code.

## Usage

Once an AI Elements component is installed, you can import it and use it in your application like any other React component. The components are added as part of your codebase (not hidden in a library), so the usage feels very natural.

## Example

After installing AI Elements components, you can use them in your application like any other React component. For example:

```tsx title="conversation.tsx"
"use client";

import {
  Message,
  MessageContent,
  MessageResponse,
} from "@/components/ai-elements/message";
import { useChat } from "@ai-sdk/react";

const Example = () => {
  const { messages } = useChat();

  return (
    <>
      {messages.map(({ role, parts }, index) => (
        <Message from={role} key={index}>
          <MessageContent>
            {parts.map((part, i) => {
              switch (part.type) {
                case "text":
                  return (
                    <MessageResponse key={`${role}-${i}`}>
                      {part.text}
                    </MessageResponse>
                  );
              }
            })}
          </MessageContent>
        </Message>
      ))}
    </>
  );
};

export default Example;
```

In the example above, we import the `Message` component from our AI Elements directory and include it in our JSX. Then, we compose the component with the `MessageContent` and `MessageResponse` subcomponents. You can style or configure the component just as you would if you wrote it yourself – since the code lives in your project, you can even open the component file to see how it works or make custom modifications.

## Extensibility

All AI Elements components take as many primitive attributes as possible. For example, the `Message` component extends `HTMLAttributes<HTMLDivElement>`, so you can pass any props that a `div` supports. This makes it easy to extend the component with your own styles or functionality.

## Customization

After installation, no additional setup is needed. The component’s styles (Tailwind CSS classes) and scripts are already integrated. You can start interacting with the component in your app immediately.

For example, if you'd like to remove the rounding on `Message`, you can go to `components/ai-elements/message.tsx` and remove `rounded-lg` as follows:

```tsx title="components/ai-elements/message.tsx" highlight="8"
export const MessageContent = ({
  children,
  className,
  ...props
}: MessageContentProps) => (
  <div
    className={cn(
      "flex flex-col gap-2 text-sm text-foreground",
      "group-[.is-user]:bg-primary group-[.is-user]:text-primary-foreground group-[.is-user]:px-4 group-[.is-user]:py-3",
      className
    )}
    {...props}
  >
    <div className="is-user:dark">{children}</div>
  </div>
);
```

## Troubleshooting

### Why are my components not styled?

Make sure your project is configured correctly for shadcn/ui in Tailwind 4 - this means having a `globals.css` file that imports Tailwind and includes the shadcn/ui base styles.

### I ran the AI Elements CLI but nothing was added to my project

Double-check that:

- Your current working directory is the root of your project (where `package.json` lives).
- Your components.json file (if using shadcn-style config) is set up correctly.
- You’re using the latest version of the AI Elements CLI:

```bash title="Terminal"
npx ai-elements@latest
```

If all else fails, feel free to open an [issue on GitHub](https://github.com/vercel/ai-elements/issues).

### Theme switching doesn’t work — my app stays in light mode

Ensure your app is using the same data-theme system that shadcn/ui and AI Elements expect. The default implementation toggles a data-theme attribute on the `<html>` element. Make sure your tailwind.config.js is using class or data- selectors accordingly.

### The component imports fail with “module not found”

Check the file exists. If it does, make sure your `tsconfig.json` has a proper paths alias for `@/` i.e.

```json title="tsconfig.json"
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["./*"]
    }
  }
}
```

### My AI coding assistant can't access AI Elements components

1. Verify your config file syntax is valid JSON.
2. Check that the file path is correct for your AI tool.
3. Restart your coding assistant after making changes.
4. Ensure you have a stable internet connection.

### Still stuck?

If none of these answers help, open an [issue on GitHub](https://github.com/vercel/ai-elements/issues) and someone will be happy to assist.

## Available Components

See the `references/` folder for detailed documentation on each component.

© vercel · Apache-2.0 · vercel/ai-elements

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor