These kind of palettes always struggle with brighter yellows like #ffe400 because of the necessary normalization across hues to make it a full palette in first place, which of course prevents some colors to fulfill their potential (which is often at their peak chromacity). No AI can solve this problem because it's how colors work.<p>I think it's best to keep the palette separate from the code (e.g. store palettes in an app like Sip), and not insist on the replaceability of colors across a range. E.g. instead of blue-500 use functional names like btn-color or brand-color and alias the colors that way in code.
This does pick some pleasing palettes but I’m not clear how they are utilized in the page. A quick scan of Tailwindscss docs shows a bit of discussion about naming colors and picking a primary and secondary color but I don’t see much discussion about the other colors in their palettes. Anyone explain?
This is a lovely app but it really <i>needs</i> to generate grays as well. You just can't randomly drop in a color palette without changing the default TW grays. (they are pretty blue)
So what exactly is AI about it? It just looks like a common algorithm that matches colors together and not some AI that has been trained to find matching color palettes.
i've added it to my list of color palette generation tools - sharing in case it helps someone else <a href="https://github.com/sw-yx/spark-joy/blob/master/README.md#color-picking" rel="nofollow">https://github.com/sw-yx/spark-joy/blob/master/README.md#col...</a>