Essential cookies keep Huevex running. With your permission we also measure how the site is used. Nothing optional loads until you choose. Cookie Policy
A palette can look right in a screenshot and still fail the moment it meets a real interface: the contrast disappears in a form field, the hover state is guesswork, and every shade under the primary gets derived by hand. Huevex exists to close that gap.
I built Huevex because I got tired of the same two hours at the end of every project: picking a palette I liked, then hand-deriving a dozen shades, guessing the hover color, checking contrast pair by pair, and hoping nothing fell apart in dark mode.
The tools I was using stopped at generation. They gave me a pretty set of swatches and left the part that decides whether the work ships to me. Huevex goes the other way: score the palette on the things that decide whether it survives as a system, then turn the one you keep into the tokens a build actually consumes.
So the library is scored rather than just sorted, the score breaks down into six measures you can argue with, and the system output is real CSS variables and Tailwind tokens, not a picture of them.
Questions, bugs, a measure you think is wrong: it all reaches me directly. There is no support queue between you and the product.
