Custom components
Build custom shadcn/ui components with the DS Manager agent, edit them like built-in ones and publish them in your shadcn registry. Pro feature.
Custom components are components shadcn/ui does not ship, such as a color picker or a product tour. You describe one to the agent, it writes the code, and the component gets the same page as a Button: matrix, demo, Style and Utilities tabs, and layer tree.
Pro accounts can build, change and fix custom components with the agent.
Building a component
- In the left nav, click the + (Add new component) at the right of the Custom components heading. With no components yet, you can also click Start prompting in the group.
- The Agent tab opens a new chat with "Build a custom component: " typed in. Finish the sentence, for example "a color picker with a hex input and recent colors", and send it.
- The agent builds the best version it can without asking questions first. Its reply names the main choices it made.
- The component appears under Custom components in the left nav, and in the components table with a Custom tag.
If the result is not what you wanted, keep talking to the agent in the same chat, or use Change with the agent later (see below).

House rules
The agent writes real React and TypeScript, and DS Manager checks the code against a set of rules before saving it:
- Imports are limited to React, your system's shadcn/ui components and icons,
class-variance-authorityand a short list of approved packages (react-colorfuland@floating-ui/react-dom), each at a pinned version. - Variants and sizes use cva the way the built-in components do, so you can edit them in the Variant and Size menus.
- Every style lives in editable rules. The code only carries class names that point at them, which is why the Style tab works on the component.
- Colors come from your theme. Palette shades like
bg-blue-500and literal colors likebg-[#f00]are refused. - The code can't reach outside the component: no network requests, no storage, no scripts, no iframes.
- A built-in component's
variantorsize, written out, has to be one your system has. - No export can take a built-in part's name, such as
CardTitle.
If the check fails, the agent fixes the code and tries again. After four failed attempts, the component is saved as a draft.
Editing a custom component
A custom component's page works like any other component page. See Editing components and Variants and states. The canvas opens on Demo, which the agent writes with every build, and Matrix shows its variants and sizes.
Edits on this page change only the custom component's own rules. When it uses a built-in component inside, such as a Popover or an Input, that part is read-only here: edit it on its own page, and the change reaches the custom component too.
Renaming
The Name field is the first row of the Style tab.
- Click the field and type the new name, or choose Rename in the component menu.
- Press Enter.
The page address follows the name: Line Chart lives at /components/custom/line-chart. Old addresses still open the page. A name already used by another custom component or a built-in one is refused, with the reason in red under the field.
The code keeps the name it was built under, so projects that installed the component keep importing it. When the two names differ, a Code row under Name shows the code's name.
Component menu
The three-dot button in the rail's title row opens the component menu:
- Reset changes puts every edited rule of the component back to what the agent built, in one undo step. It shows the count, such as "Reset changes (3 rules)".
- Change with the agent opens a new chat with "Change the Line Chart component: " typed in, for you to finish.
- Rename puts the cursor in the Name field.
- Move to group files the component in a group. See Groups.
- Archive takes the component out of your system without deleting it, and Restore brings it back. See Archive.
- Delete component asks first: "Its style edits and added variants go with it, and the next publish drops it from your registry. You can undo this."
Groups
Groups are folders for your custom components in the left nav.
- Open the component menu and choose Move to group.
- Pick a group, or New group… to make one. In the New group dialog, type a Group name of up to 40 characters and click Create group.
To take a component out of its group, choose Move to group > No group. A group exists while it holds at least one component, so it goes away when you move its last component out.
Under Custom components, the groups come first as folders, open by default. Ungrouped components follow, then the Archived folder.

Archive
Archive in the component menu sets a component aside without deleting it. An archived component:
- keeps its page, its group and your edits
- is left out of publish and install, share links, the All components page and the Figma lists
- can't be changed with the agent until you restore it
Archived components wait in a closed Archived folder at the bottom of Custom components, with the count in its name, such as "Archived (2)". Their page shows the banner "Archived. It is not published or installed." with a Restore button. Restore in the component menu does the same.
Archived components don't count toward your system's limit of custom components, and the archive holds as many as that limit. When the system is full, a restore is refused until you archive or delete another component. When the archive is full, archiving is refused until you delete an archived one.
Drafts
A component that failed its checks is a draft. It has a Draft badge in the left nav and the components table, and a banner above the canvas: "Draft. This component failed its checks, so it is not published."
- Click Show the problems to see each problem with its file and line.
- Click Fix with the agent. The agent reads the component, fixes what the check reported and saves it.
A draft stays in your system but is skipped when you publish.
Publishing
When you publish, each custom component that passed its checks goes into your registry as its own item, next to the built-in components, and installs the same way they do. See Publish and install.
Share links show your custom components, except drafts. To hide them, untick Custom Components under Users can see in the Share popover. See Share links and forks.