ai-elements
Install AI UI components from the Elements registry. Use when user needs chat interfaces, agentic UIs (tool calls, reasoning, plans), multi-agent dashboards, or AI devtools. Triggers on "AI component", "chat UI", "agent UI", "tool call component", "streaming text", "agentic", "multi-agent", "AI SDK", "chat input", "message bubble", "thinking indicator".
- Installs
- 53
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/crafter-station/elements --skill ai-elements- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ai-elements automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
AI Elements
35 AI UI components across 4 subcategories. Built for Vercel AI SDK patterns.
Install Pattern
npx shadcn@latest add @elements/ai-{name}
Chat (11 components)
Conversational UI primitives.
| Component | Install |
|---|---|
| Chat (full) | @elements/ai-chat |
| Chat Input | @elements/ai-chat-input |
| Message Bubble | @elements/ai-message-bubble |
| Messages | @elements/ai-messages |
| Model Selector | @elements/ai-model-selector |
| Response Actions | @elements/ai-response-actions |
| Streaming Text | @elements/ai-streaming-text |
| Suggested Actions | @elements/ai-suggested-actions |
| Temperature Slider | @elements/ai-temperature-slider |
| Thinking Indicator | @elements/ai-thinking-indicator |
| Token Counter | @elements/ai-token-counter |
Agentic (8 components)
Tool use, reasoning, and planning UI.
| Component | Install |
|---|---|
| Artifact | @elements/ai-artifact |
| Chain of Thought | @elements/ai-chain-of-thought |
| Confirmation | @elements/ai-confirmation |
| Plan | @elements/ai-plan |
| Reasoning | @elements/ai-reasoning |
| Sources | @elements/ai-sources |
| Task List | @elements/ai-task-list |
| Tool Call | @elements/ai-tool-call |
Multi-Agent (8 components)
Agent orchestration and monitoring.
| Component | Install |
|---|---|
| Agent Context | @elements/ai-agent-context |
| Agent Roster | @elements/ai-agent-roster |
| Agent Status | @elements/ai-agent-status |
| Guardrails | @elements/ai-guardrails |
| Handoff Chain | @elements/ai-handoff-chain |
| Memory Viewer | @elements/ai-memory-viewer |
| Pipeline | @elements/ai-pipeline |
| Routing Indicator | @elements/ai-routing-indicator |
Devtools (8 components)
AI debugging and inspection.
| Component | Install |
|---|---|
| Conversation Tree | @elements/ai-conversation-tree |
| Latency Meter | @elements/ai-latency-meter |
| Model Info | @elements/ai-model-info |
| Prompt Diff | @elements/ai-prompt-diff |
| Request Inspector | @elements/ai-request-inspector |
| Stream Debugger | @elements/ai-stream-debugger |
| Token Viewer | @elements/ai-token-viewer |
| Tool Inspector | @elements/ai-tool-inspector |
Quick Patterns
# Chat interface
npx shadcn@latest add @elements/ai-chat @elements/ai-chat-input @elements/ai-message-bubble @elements/ai-messages @elements/ai-streaming-text
# Agentic UI
npx shadcn@latest add @elements/ai-tool-call @elements/ai-reasoning @elements/ai-plan @elements/ai-confirmation
# Multi-agent dashboard
npx shadcn@latest add @elements/ai-agent-roster @elements/ai-agent-status @elements/ai-pipeline @elements/ai-handoff-chain
# AI debugging
npx shadcn@latest add @elements/ai-request-inspector @elements/ai-stream-debugger @elements/ai-token-viewer
Discovery
Browse https://tryelements.dev/docs/ai-elements
Component Not Found?
Generate a pre-filled GitHub issue:
https://github.com/crafter-station/elements/issues/new?title=[Component%20Request]%20Add%20AI%20{Name}&labels=enhancement,ai-elements
FAQ
What does the ai-elements skill do?
Install AI UI components from the Elements registry. Use when user needs chat interfaces, agentic UIs (tool calls, reasoning, plans), multi-agent dashboards, or AI devtools. Triggers on "AI component", "chat UI", "agent UI", "tool call component", "streaming text", "agentic", "multi-agent", "AI SDK", "chat input", "message bubble", "thinking indicator".
How do I install ai-elements?
Run npx skills add https://github.com/crafter-station/elements --skill ai-elements in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ai-elements/ (personal) or .claude/skills/ai-elements/ (project).
Which AI agents can use ai-elements?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ai-elements safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ai-elements?
It is published by crafter-station in crafter-station/elements. It has 53 recorded installs.
More from crafter-station/elements
logo-with-variants
crafter-station/elements
Open the skill to read its SKILL.md instructions.
create-element
crafter-station/elements
Create new UI elements for tryelements.dev registry. Use when: (1) Adding new UI components (buttons, inputs, cards), (2) Building integration components (Clerk, Stripe, Uploadthing), (3) Creating theme-related elements, (4) Any shadcn-style registry component. IMPORTANT: For logo components with variants (icon/wordmark/logo + dark/light), use the logo-with-variants skill instead. This skill includes scaffolding, registry schema, and component patterns. ALWAYS use Context7 MCP to fetch latest dependency docs before implementing.
theme-elements
crafter-station/elements
Install theme switcher components from the Elements registry. Use when user needs dark mode toggles, theme switchers, light/dark buttons, or theme dropdowns. Triggers on "theme switcher", "dark mode", "light mode", "theme toggle", "theme button", "switch theme", "dark mode toggle".
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.