feat: add docs to shadcn components

[thomasyuill-livekit]

Summary

• Add documentation generation for shadcn components - New doc-gen.ts script uses react-docgen-typescript to extract and output prop types to prop-types.json
• Improve JSDoc comments across agents-ui components - Added detailed prop descriptions and examples to AgentSessionProvider, AgentChatTranscript, AgentChatIndicator, AgentDisconnectButton, StartAudioButton, visualizers, and track controls
• Enhance Storybook controls - Updated argTypes for better interactivity in stories (flattened nested controls, added missing prop controls, fixed control types)
• Fix component prop forwarding - Added ...props spread and ComponentProps<'element'> types to properly forward HTML attributes
• Normalize registry naming - Updated component titles for consistency (e.g., "Audio Bar Visualizer" → "Agent Audio Visualizer Bar")
• Add shadcn README

Related to https://github.com/livekit/web/pull/2798

• new

Testing

• Copy .env.example and update DEST vars
• Run pnpm registry:build to verify doc generation works
• Verify dist/prop-types.json contains expected component documentation
• Run Storybook and confirm controls work correctly for updated stories

[changeset-bot]

⚠️ No Changeset found

Latest commit: b05eec2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

size-limit report 📦

Path	Size
LiveKitRoom only	6 KB (0%)
LiveKitRoom with VideoConference	32.46 KB (0%)
All exports	43.39 KB (0%)

[lukasIO]

how and where are we planning to consume the prop-types.json ?
Asking because we already have an automated doc generation workflow as part of this repo based on api-extractor

[thomasyuill-livekit]

how and where are we planning to consume the prop-types.json ?

https://github.com/livekit/web/pull/2798

We use it in

• apps/docs/markdoc/schema/ShadcnComponentPropRenderer.markdoc.ts
• and the demos (eg. apps/docs/lib/shadcn/demos/agent-audio-visualizer-bar.tsx)

[1egoman]

Generally makes sense to me. I'm assuming you are holding off on all the argTypes todos for a future pull request?

[thomasyuill-livekit]

I'm assuming you are holding off on all the argTypes todos for a future pull request?

Ahh good catch, I'll clean that up

I had an agent review the stories and make note of the props we weren't being exposed.
I then decided against exposing all of them because some of them don't provide value

For instance

• tailwind wont pick up classnames passed in that havent already been used
• you can't provide a custom callback