The issue #2 mentioned syntax sugar. It would definitely be nice to have a toggle-anim if simply toggling to and from a certain state. It may even serve as a better solution for the original existence of #2 in the first place.
Whether it does or not, though, #2 does at least reveal if/else changes need to be solved at some point for more complex use-cases than Tabs.
In a scenario such as tabs with 3 or more tabs, all tabs would need to have the group class for all tab buttons.
However, this starts to make the class attribute more bloated than it already could be in TailwindCSS.
So, a solution is either:
Simply let the class attribute get bloated from multiconditional animations like Tabs
Create more logic for some kind of class called main-group-anim:[unique_id] where a default like from-anim:hidden and to-anim:block could be applied in a broad stroke where the button overrides the default of from-anim:hidden or something.
Option number 2 would only work for Tabs and Tab-like use-cases. Option number 1 would be a lot more versatile. In that sense, I tend to favor Option 1. On the other hand, Option 2 is a sort-of syntax sugar that would make use cases like Tabs a lot less annoying to implement.