Thanks for your feedback. I will copy+paste below my response to a similar feedback to my post. --- start excerpt --- The main intention/purpose of the librar

Thanks for your feedback. I will copy+paste below my response to a similar feedback to my post. --- start excerpt --- The main intention/purpose of the library is to provide a well-defined structure to guide the developer in crafting their color system. Especially when using TypeScript, this benefit is immediately felt. Since this is the very first release of the lib, it only includes this core functionality. Based on feedback from users, I intend to build up the library to include more things that users would say are useful to them. Based on your comment, it looks like one such enhancement could be to add functionality to generate additional base colors based on a single "seed" color (e.g. the main brand color), e.g. a triad of base colors (primary, secondary, tertiary) based on Triadic Palette from the primary's base. This is where feedback like yours will help make this library more helpful to more developers. --- end excerpt --- To address your specific example, the pattern you pointed out is not really equivalent to c(a, b). The color mapping function "c" is applied internally when building the individual palettes, not to (a, b). I will try to make my example in the README a little less contrived, as I can see where the confusion is coming from. Also when in the future versions this library will bundle various color mapping functions (again, based on user feedback), the structure provided by the library will make more sense because the "c" part there would be any one of the pre-built functions that you can just pass to the `colorScheme()` helper. Again I appreciate your insights.