Your own styles

A family is a starting point, not a cage. From the lightest touch to the heaviest: tune a parameter, use a hook, override a class, write a family.

Tune a parameter

The family's parameters are custom properties: set them after the theme, on the whole page or on one part of it. The theme generator does it with a preview and gives you the file.

<section style="--color-primary: oklch(60% 0.18 150)">
  <Button color="primary">Green here</Button>
</section>

Use a hook

Some components expose custom properties of their own, listed as hooks on the DOM tab of their page. Set one on an element and that element changes, nothing else.

/* A hook: a custom property the component exposes */
.avatar.team { --avatar-bg: var(--color-accent); }

Override a class

Most of a family's rules are one class, so a rule of yours loaded after the family wins without !important. A variant that reacts to states weighs more (.btn-ghost:not(:hover)): there, set a parameter or a hook rather than fight the selector.

/* Loaded after the family: one class against one class, yours wins */
.btn { text-transform: uppercase; }
.card-title { letter-spacing: -0.02em; }

When your classes meet the kit's

The kit's classes are plain: btn, chip, title. If your project already has a .title, a Vite plugin renames the kit's while you build: see Class prefix.

Write a family

When the look you want is not a theme away, write a family. The Create a family page gives the reference, loads your stylesheet into this site and checks it against every component.