agents-ui
Build React frontends for LiveKit voice AI agents. Use this skill when creating web interfaces for voice assistants using LiveKit's shadcn-based Agents UI components. Covers AgentSessionProvider, audio visualizers, media controls, chat transcripts, and customization with Tailwind CSS.
What this skill does
# LiveKit Agents UI
Build React frontends for LiveKit voice AI agents with shadcn-based components.
## LiveKit MCP server tools
This skill works alongside the LiveKit MCP server, which provides direct access to the latest LiveKit documentation, code examples, and changelogs. Use these tools when you need up-to-date information that may have changed since this skill was created.
**Available MCP tools:**
- `docs_search` - Search the LiveKit docs site
- `get_pages` - Fetch specific documentation pages by path
- `get_changelog` - Get recent releases and updates for LiveKit packages
- `code_search` - Search LiveKit repositories for code examples
- `get_python_agent_example` - Browse 100+ Python agent examples
**When to use MCP tools:**
- You need the latest API documentation or feature updates
- You're looking for recent examples or code patterns
- You want to check if a feature has been added in recent releases
- The local references don't cover a specific topic
**When to use local references:**
- You need quick access to core concepts covered in this skill
- You're working offline or want faster access to common patterns
- The information in the references is sufficient for your needs
Use MCP tools and local references together for the best experience.
## References
Consult these resources as needed:
- ./references/livekit-overview.md -- LiveKit ecosystem overview and how these skills work together
- ./references/components.md -- All component APIs, props, and usage examples
## Prerequisites
- Node.js >= 18
- React 19
- Tailwind CSS 4
- shadcn/ui initialized in your project
## Installation
### 1. Add the LiveKit registry to your shadcn config
In your `components.json`:
```json
{
"registries": {
"@agents-ui": "https://livekit.io/ui/r/{name}.json"
}
}
```
### 2. Install components
```bash
# Install individual components
npx shadcn@latest add @agents-ui/agent-session-provider
npx shadcn@latest add @agents-ui/agent-control-bar
npx shadcn@latest add @agents-ui/agent-audio-visualizer-bar
# Or install multiple at once
npx shadcn@latest add @agents-ui/agent-session-provider @agents-ui/agent-control-bar
```
Components are copied to your `components/agents-ui/` directory for full customization.
## Quick start
### Installation
Agents UI components require both `livekit-client` and `@livekit/components-react`:
```bash
npm install livekit-client @livekit/components-react
```
### Setting up a TokenSource
Before using Agents UI components, you need a `TokenSource` from `livekit-client` to handle authentication.
**For development** (using LiveKit Cloud Sandbox):
```tsx
import { TokenSource } from 'livekit-client';
const tokenSource = TokenSource.sandboxTokenServer({
sandboxId: 'your-sandbox-id',
});
```
**For production** (using your own token endpoint):
```tsx
import { TokenSource } from 'livekit-client';
const tokenSource = TokenSource.endpoint('/api/token');
```
### Basic voice agent interface
Create a session using `useSession` from `@livekit/components-react`, then pass it to `AgentSessionProvider`:
```tsx
'use client';
import { useRef, useEffect } from 'react';
import { useSession } from '@livekit/components-react';
import { TokenSource, TokenSourceConfigurable } from 'livekit-client';
import { AgentSessionProvider } from '@/components/agents-ui/agent-session-provider';
import { AgentControlBar } from '@/components/agents-ui/agent-control-bar';
import { AgentAudioVisualizerBar } from '@/components/agents-ui/agent-audio-visualizer-bar';
export function VoiceAgent() {
// Use useRef to prevent recreating TokenSource on each render
const tokenSource: TokenSourceConfigurable = useRef(
TokenSource.sandboxTokenServer({ sandboxId: 'your-sandbox-id' })
).current;
// Create session using useSession hook (required for AgentSessionProvider)
const session = useSession(tokenSource, {
agentName: 'your-agent-name',
});
// Auto-start session with cleanup
useEffect(() => {
session.start();
return () => session.end();
}, []);
return (
<AgentSessionProvider session={session}>
<div className="flex flex-col items-center gap-8 p-8">
<AgentAudioVisualizerBar />
<AgentControlBar />
</div>
</AgentSessionProvider>
);
}
```
### Production example with token endpoint
```tsx
'use client';
import { useRef, useEffect } from 'react';
import { useSession } from '@livekit/components-react';
import { TokenSource, TokenSourceConfigurable } from 'livekit-client';
import { AgentSessionProvider } from '@/components/agents-ui/agent-session-provider';
import { AgentControlBar } from '@/components/agents-ui/agent-control-bar';
import { AgentAudioVisualizerBar } from '@/components/agents-ui/agent-audio-visualizer-bar';
export function VoiceAgent() {
const tokenSource: TokenSourceConfigurable = useRef(
TokenSource.endpoint('/api/token')
).current;
const session = useSession(tokenSource, {
roomName: 'my-room',
participantIdentity: 'user-123',
participantName: 'John',
agentName: 'my-agent',
});
useEffect(() => {
session.start();
return () => session.end();
}, []);
return (
<AgentSessionProvider session={session}>
<div className="flex flex-col items-center gap-8 p-8">
<AgentAudioVisualizerBar />
<AgentControlBar />
</div>
</AgentSessionProvider>
);
}
```
## Core components
### AgentSessionProvider
Required wrapper that provides session state to all child components. It wraps `SessionProvider` from `@livekit/components-react` and includes `RoomAudioRenderer` for audio playback.
You must create a session using `useSession` from `@livekit/components-react` and pass it to `AgentSessionProvider`:
```tsx
import { useRef, useEffect } from 'react';
import { useSession } from '@livekit/components-react';
import { TokenSource, TokenSourceConfigurable } from 'livekit-client';
import { AgentSessionProvider } from '@/components/agents-ui/agent-session-provider';
function MyApp() {
// Create tokenSource with useRef to prevent recreation
const tokenSource: TokenSourceConfigurable = useRef(
TokenSource.endpoint('/api/token')
).current;
// Create session using useSession hook (required)
const session = useSession(tokenSource, { agentName: 'your-agent' });
// Start session when component mounts
useEffect(() => {
session.start();
return () => session.end();
}, []);
return (
<AgentSessionProvider session={session}>
{/* All Agents UI components must be inside this provider */}
</AgentSessionProvider>
);
}
```
### AgentControlBar
Combined media controls with visualizer:
```tsx
<AgentControlBar />
```
### Audio visualizers
Five visualization styles:
```tsx
// Bar visualizer (horizontal bars)
<AgentAudioVisualizerBar />
// Grid visualizer (dot matrix)
<AgentAudioVisualizerGrid />
// Radial visualizer (circular)
<AgentAudioVisualizerRadial />
// Wave visualizer (waveform)
<AgentAudioVisualizerWave />
// Aura visualizer (ambient glow effect)
<AgentAudioVisualizerAura />
```
### Media controls
Individual track controls:
```tsx
// Toggle microphone
<AgentTrackToggle source="microphone" />
// Toggle camera
<AgentTrackToggle source="camera" />
// Toggle screen share
<AgentTrackToggle source="screen_share" />
// Full track control with label
<AgentTrackControl source="microphone" />
```
### Chat components
Display conversation transcripts:
```tsx
// Full chat transcript
<AgentChatTranscript />
// Typing/thinking indicator
<AgentChatIndicator />
```
### Session controls
```tsx
// Disconnect button
<AgentDisconnectButton />
// Start audio (for browsers requiring user interaction)
<StartAudioButton />
```
## Agent states
The AgentSessionProvider tracks these states:
- `initializing` - Agent is starting up
- `listening` - Agent is listening for user input
- `thinking` - Agent is processing/generating response
- `speaking` - Agent is speaking
Use these stRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.