Creative Tim UI Blocks
creativetimofficial/ui
Helps install, generate and review Creative Tim UI blocks: shadcn/ui-based React and Tailwind sections that follow a restrained, production-minded design philosophy.
A skill your agent uses whenever the user wants to build or modify a chat, agent, or tool-calling UI in a React 19 + Tailwind v4 project — especially if the code imports from…
$ npx skills add 21st-dev/agent-elements --skill agent-elements -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install 21st-dev/agent-elements agent-elements --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/21st-dev/agent-elements.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-elements .claude/skills/agent-elements && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agent-elements" agent skill from https://github.com/21st-dev/agent-elements/tree/main/skills/agent-elements into .claude/skills/agent-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-elements", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/21st-dev/agent-elements/tree/main/skills/agent-elementsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add 21st-dev/agent-elements --skill agent-elements -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install 21st-dev/agent-elements agent-elements --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/21st-dev/agent-elements.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agent-elements .agents/skills/agent-elements && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agent-elements" agent skill from https://github.com/21st-dev/agent-elements/tree/main/skills/agent-elements into .agents/skills/agent-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-elements", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 21st-dev/agent-elements --skill agent-elements -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install 21st-dev/agent-elements agent-elements --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/21st-dev/agent-elements.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agent-elements .cursor/skills/agent-elements && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agent-elements" agent skill from https://github.com/21st-dev/agent-elements/tree/main/skills/agent-elements into .cursor/skills/agent-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-elements", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/21st-dev/agent-elements.git --path skills/agent-elements--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add 21st-dev/agent-elements --skill agent-elements -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install 21st-dev/agent-elements agent-elements --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/21st-dev/agent-elements.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agent-elements .gemini/skills/agent-elements && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agent-elements" agent skill from https://github.com/21st-dev/agent-elements/tree/main/skills/agent-elements into .gemini/skills/agent-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-elements", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install 21st-dev/agent-elements agent-elementsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add 21st-dev/agent-elements --skill agent-elements -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/21st-dev/agent-elements.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agent-elements .github/skills/agent-elements && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agent-elements" agent skill from https://github.com/21st-dev/agent-elements/tree/main/skills/agent-elements into .github/skills/agent-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-elements", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 21st-dev/agent-elements --skill agent-elements -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install 21st-dev/agent-elements agent-elements --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/21st-dev/agent-elements.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agent-elements .opencode/skills/agent-elements && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agent-elements" agent skill from https://github.com/21st-dev/agent-elements/tree/main/skills/agent-elements into .opencode/skills/agent-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-elements", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
agent-elementsA skill your agent uses whenever the user wants to build or modify a chat, agent, or tool-calling UI in a React 19 + Tailwind v4 project — especially if the code imports from…
Agent Elements is an agent skill from 21st-dev/agent-elements. Use whenever the user wants to build or modify a chat, agent, or tool-calling UI in a React 19 + Tailwind v4 project — especially if the code imports from @/components/agent-elements/ or the project has that folder on disk. Triggers: "agent chat", "tool call UI", "streaming chat", "plan approval", "AgentChat", "InputBar", "tool renderer", mentions of Agent Elements, or requests to add a new agent surface with shadcn. Do NOT use for plain chat UIs that don't need tool/plan/approval cards, or for projects already…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Frontend & Design, covering Design systems and Structured output and tool calling. It works with shadcn/ui, React and Tailwind CSS. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b04b36c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npxFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
agent-elements.21st.devFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Agent Elements loads about 2.3k tokens when it runs. Until then it costs about 144 tokens; SKILL.md has 668 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from 21st-dev/agent-elements at commit b04b36c, republished under its MIT licence (© 21st-dev). 668 words, ~2,343 tokens.
.claude/skills/agent-elements/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Project-aware context for building chat and agent UIs with Agent Elements —
an open-source shadcn registry at https://agent-elements.21st.dev.
When this skill loads, you know:
npx shadcn@latest add https://agent-elements.21st.dev/r/<component>.json.
Files land under components/agent-elements/ (the library's internal
components/ prefix is stripped — see Paths below).UIMessage[] from ai, status is ChatStatus. useChat() plugs in
directly.Consider this project "Agent Elements-ready" if any of these are true:
components/agent-elements/ exists on diskcomponents.json includes an alias or registry reference to Agent Elementspackage.json dependencies include ai + @tabler/icons-react and the user
mentions Agent ElementsIf the folder does not exist yet, install on demand with:
npx shadcn@latest add https://agent-elements.21st.dev/r/agent-chat.jsonagent-chat transitively pulls every other component it needs via
registryDependencies (MessageList, InputBar, tool renderers, shared utils).
After shadcn add, files sit under @/components/agent-elements/ with this
shape:
components/agent-elements/
agent-chat.tsx
message-list.tsx
input-bar.tsx
markdown.tsx
user-message.tsx
error-message.tsx
text-shimmer.tsx
spiral-loader.tsx
input/
attachment-button.tsx
send-button.tsx
file-attachment.tsx
suggestions.tsx
model-picker.tsx
mode-selector.tsx
tools/
bash-tool.tsx
edit-tool.tsx
search-tool.tsx
todo-tool.tsx
plan-tool.tsx
tool-group.tsx
subagent-tool.tsx
mcp-tool.tsx
thinking-tool.tsx
generic-tool.tsx
question/
question-tool.tsx
hooks/use-tool-complete.ts
utils/cn.ts
types.tsImport rule: always import from the exact file, never from a barrel.
// ✅
import { AgentChat } from "@/components/agent-elements/agent-chat";
import { BashTool } from "@/components/agent-elements/tools/bash-tool";
// ❌ — no barrel exists
import { AgentChat } from "@/components/agent-elements";MessageList + InputBar,
handles tool invocations via toolRenderers, shows an empty state with
optional suggestions. Props: messages, status, onSend, onStop,
toolRenderers?, suggestions?, attachments?, classNames?, slots?.toolRenderers and showCopyToolbar.Markdown streams safely (external links get rel="noreferrer" by default).status, onSend({ content }), onStop,
value? + onChange? (controlled), attachedImages/attachedFiles with
their remove handlers, leftActions/rightActions slots, suggestions?,
questionBar?, infoBar?.leftActions. Both
accept a simple { id, name, version? } / { id, label, icon?, description? }
shape. Do not import CLAUDE_MODELS — it was removed; supply your own array.All tool cards accept a part prop of type
Extract<UIMessage["parts"][number], { type: \tool-<Name>` }>from the AI SDK. Register them viatoolRenderersonAgentChat/MessageList`:
<AgentChat
toolRenderers={{
Bash: BashTool,
Edit: EditTool,
Write: EditTool, // Write reuses EditTool
Search: SearchTool,
WebSearch: SearchTool,
TodoWrite: TodoTool,
PlanWrite: PlanTool,
Task: SubagentTool,
Thinking: ThinkingTool,
}}
/>Cards available:
input.old_string/input.new_string or
output.structuredPatch, plus an approval footer via input.approval.results or use output.results.input.todos vs output.oldTodos.parseMcpToolType from
@/components/agent-elements/tools/tool-registry to get mcpInfo."use client";
import { AgentChat } from "@/components/agent-elements/agent-chat";
import { BashTool } from "@/components/agent-elements/tools/bash-tool";
import { EditTool } from "@/components/agent-elements/tools/edit-tool";
import { SearchTool } from "@/components/agent-elements/tools/search-tool";
import { useChat } from "@ai-sdk/react";
export default function Chat() {
const { messages, status, sendMessage, stop } = useChat();
return (
<AgentChat
messages={messages}
status={status}
onSend={({ content }) => sendMessage({ text: content })}
onStop={stop}
toolRenderers={{
Bash: BashTool,
Edit: EditTool,
Write: EditTool,
Search: SearchTool,
}}
/>
);
}import { InputBar } from "@/components/agent-elements/input-bar";
import { ModeSelector } from "@/components/agent-elements/input/mode-selector";
import { ModelPicker } from "@/components/agent-elements/input/model-picker";
import { IconBulb, IconCursor } from "@tabler/icons-react";
const modes = [
{ id: "agent", label: "Agent", icon: IconCursor },
{ id: "plan", label: "Plan", icon: IconBulb },
];
const models = [
{ id: "sonnet", name: "Sonnet", version: "4.6" },
{ id: "opus", name: "Opus", version: "4.7" },
];
<InputBar
status="ready"
onSend={handleSend}
onStop={handleStop}
leftActions={
<>
<ModeSelector modes={modes} defaultValue="agent" />
<ModelPicker models={models} defaultValue="sonnet" />
</>
}
/>toolRenderers values are React components that receive { part, chatStatus }.
Return whatever UI you want; reuse GenericTool as a fallback shell.
Agent Elements reads these Tailwind CSS vars (shadcn-style). Do not remove or rename them in the consumer theme:
--an-foreground, --an-background, --an-primary-color--background, --foreground, --border,
--muted, --muted-foreground, --accent, --primary, etc.Customising a component is just editing the installed file. Prefer that over wrapping — the code is yours now.
assistant-ui, ai-elements, copilotkit, or another kit —
don't mix.InputBar + your own
message rendering may be enough; skip AgentChat.npx shadcn@latest init if
components.json is missing, then
npx shadcn@latest add https://agent-elements.21st.dev/r/agent-chat.json.components/agent-elements/input/send-button.tsx directly. Tokens live on
--an-* CSS vars.toolRenderers; fall back to
GenericTool for unknown tools.messages and status straight through,
translate sendMessage/stop to onSend({ content })/onStop.https://agent-elements.21st.dev/r/index.jsonhttps://agent-elements.21st.dev/r/<id>.jsonhttps://agent-elements.21st.dev/llms-full.txt© 21st-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/agent-elements of 21st-dev/agent-elements.
Open the folder on GitHubat commit b04b36c
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in 21st-dev/agent-elements, which our catalogue first saw on October 7, 2026.
Agent Elements next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agent Elements this skill21st-dev/agent-elements | 104 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Creative Tim UI Blockscreativetimofficial/ui | 12k | — | ~2.1k | Automated safety check: Notes | MIT | |
| Cosscrafter-station/petdex | 4.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ss Learnbitjaru/styleseed | 970 | — | ~1.3k | Automated safety check: Pass | MIT | |
| UithingBayBreezy/ui-thing | 729 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Animated React Component LibrariesHainrixz/editor-pro-max | 260 | 1 repos | ~5.7k | Automated safety check: Pass | Custom licence |
creativetimofficial/ui
Helps install, generate and review Creative Tim UI blocks: shadcn/ui-based React and Tailwind sections that follow a restrained, production-minded design philosophy.
crafter-station/petdex
Helps implement coss UI components correctly. An agent skill from crafter-station/petdex.
bitjaru/styleseed
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or…
BayBreezy/ui-thing
Manages UI Thing components, prose, blocks, themes, shortcuts, docs, and MCP-driven workflows in Nuxt projects and in the UI Thing source repo.
Hainrixz/editor-pro-max
Helps choose and drop in animated React components from Magic UI and React Bits for landing pages, marketing sites and dashboards, instead of hand-coding animations.
Manavarya09/design-extract
Extract the full design language from any website URL. An agent skill from Manavarya09/design-extract.
Works with
Categories
A skill your agent uses whenever the user wants to build or modify a chat, agent, or tool-calling UI in a React 19 + Tailwind v4 project — especially if the code imports from…. Agent Elements is an agent skill from 21st-dev/agent-elements. Use whenever the user wants to build or modify a chat, agent, or tool-calling UI in a React 19 + Tailwind v4 project — especially if the code imports from @/components/agent-elements/ or the project has that folder on disk.
Agent Elements fits situations like: the user wants to build; tool-calling UI in a React 19 + Tailwind v4 project — especially if the code imports from @/components/agent-elements/; the project has that folder on disk; plain chat UIs that dont need tool/plan/approval cards.
Run `npx skills add 21st-dev/agent-elements --skill agent-elements -a claude-code`. Or copy the skill folder (skills/agent-elements in 21st-dev/agent-elements) into .claude/skills/agent-elements in your project. Claude Code loads it when a task matches its description.
Run `npx skills add 21st-dev/agent-elements --skill agent-elements -a codex`. Or copy the skill folder (skills/agent-elements in 21st-dev/agent-elements) into .agents/skills/agent-elements in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 21st-dev/agent-elements --skill agent-elements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-elements, .gemini/skills/agent-elements, .github/skills/agent-elements and .opencode/skills/agent-elements in your project.
Going by SKILL.md and its folder, Agent Elements needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
SKILL.md names 1 domain. In commands or code: agent-elements.21st.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Agent Elements is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Agent Elements: Creative Tim UI Blocks (creativetimofficial/ui, 12k stars), Coss (crafter-station/petdex, 4.2k stars), Ss Learn (bitjaru/styleseed, 970 stars) and Uithing (BayBreezy/ui-thing, 729 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
21st-dev (a GitHub organization) maintains it in 21st-dev/agent-elements, which has 104 GitHub stars. The repository was last updated on April 24, 2026.
Source: 21st-dev/agent-elements on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.