If I was developing it I wouldn’t support DaisyUI. I look at Daisy as its own thing. It’s a way to quickly augment HTML. Chelekom is its own library so go your own way.

Use Daisy UI if you want as a base to build a base style for the library but don’t depend on it. Look how it supports its themes for example.

I would suggest you not to care about what the Phoenix include by default. At the end of the day, you have to maintain your code and the leaner the easier.

Design Systems is probably one of my favourite topics and I have probably “studied” hundreds of different systems, CSS frameworks and such! But you know why there are so many options? You can never please everybody. Some people will prefer something that looks good out of the box, some prefer something bare bones to style it themselves. It depends on the direction you want to go. Probably the option with the highest appeal is “looks good out-of-the-box but it is easy to customize”. This is what DaisyUI does well for example, since TailwindCSS isn’t really easy to build themes on top of out of the box (other than supporting light/dark theme of course). At the end of the day, you can achieve a lot by changing base/brand colour, fonts, radii, etc.