In order to make the Tailwind preset more approachable for people that already know Tailwind, we should:

• Font sizes should have the same aliases (e.g. lg = 2)
• Colors should be aliased to the same aliases * 100, e.g. purple.5 === purple.500
• Breaking change for a major version: Make the padding scale match Tailwind's

Hi,

I never used your lib yet, but very interested to (as I was starting to do a similar thing).
One thing I noticed is that I don't see dark colors (eg: iOS Colors have light & dark values, which are different, same for grey, see https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/color/)

Is there any plan to handle that? Might be a bit breaking change for color

It just doesn't test anything for the cast majority of fuzzer input. While fuzzer does learn the effective paths, let's help it more.

First, for instruction type, change the switch argument to: instruction.operation % NUM_OPERATIONS.

Then just split the available values into the two sets by looking up one integer from fuzzer and use that module size for set1 and the rest for set2.