Request a component

General guideline

Always install from @clinia. When the component you need isn't in Components, ask for it instead of installing it straight from shadcn.

Why ask for new components instead of installing from shadcn?

A component installed straight from shadcn will miss the overrides the Clinia design guidelines add:

• Colour fixes: to align the selected colours with specific component parts.
• Icons: it imports Lucide, which Clinia's lint rules reject once you add them (Migration, step 8).
• Both styles: a @clinia component ships in Luma and Sera, and the style in your components.json picks the right one.
• Testing: every @clinia component passes an automated accessibility check in both styles and both themes before it ships.

How to ask

Open a component request on the clinia/ui repository. You will need access to the private Clinia repository and have the following information on hand:

• The shadcn component name, or a link to its page on ui.shadcn.com.
• The surface: product app, marketing site or both.
• Where you'll use it: the app or site, and the screen or section.
• When you need it.
• Anything that differs from upstream: a variant, a size, a state or a behaviour.

Icons

The same form covers a utility icon the set doesn't have. Name the glyph from Material Symbols and where you'll use it. The icon generator runs in clinia/ui only, so an app can't add an icon to the set itself.

What happens next

A maintainer will add the component to the registry in a reasonable amount of time. The component will then appear in the theme after review and sign-off.