Gustavo Fenilli

Maybe add as an modifier to the components that are most likely used for those? Input, Avatar, Button and so on So something like `btn btn-primary skeleton`, skeleton would use...

I think the only problem with the current behaviour is that the value is not set to false by default, so to send a false value to the `required` rule...

I think changing the default to starting at the `off-value` and changing the default behaviour of `required` to need the `on-value` to be set, would make more sense, as if...

Good work around, it works to not break the playground itself, but when trying to add as an input to formkit it also does not work. https://formkit.link/876555d70c15647137e45e5b40d0a5bd

If it works, it works!

Something like compiler transforms? if it detects x code, transform it to y.

I like the idea of passing possible scoped variables as items inside the array and appending the slot name to it so it is indeed scoped and easy to find....

You need to remove the group before you remove the value, otherwise the group is still there to populate the field. if you call your `removeSignDestroy(sign)` inside the `removeSignFilter` it...

This is probably a tailwindcss bug and not ours, we don't really do anything with tailwindcss. I think its related to this https://github.com/tailwindlabs/tailwindcss/discussions/6749

You're correct, the documentation should exclude some of those sections from the button as those are not provided. But you can add to the button using section-schemas like so https://formkit.link/8fd815b22e4fce8bf926d5fa3ba167de