Hi and thank you for a such funny plugin!
I just started to use it and the first disadvantage i found is permissions.
F.e. craftbook.mech.bridge.use - if I'd like to give USE ALL mechanics permission to the player I need to create a huge list of craftbook.mech.XXXXX.use (craftbook.mech.[asterisk].use wildcard doesn't work)
Would it be possible to move mechanic's name to the end? In this case my task will be much easier - craftbook.mech.use.[asterisk]

My main issue with this is that "use" is conceptually different between many of the mechanics, and allowing a blanket "use" permission would encourage people to not understand what they're giving their players the ability to do. Plus, many mechanics do not have a use permission, or have multiple permissions that make up the concept of usage.

As for craftbook.mech.[asterisk].use wildcard, wildcards are handled by the permissions plugin, not plugins that check for permissions. If you want wildcards within the middle of a permission node your permission plugin would need to support it.

I'm using LuckPerms which is quite powerful but wildcards with asterisk in the middle don't work. Maybe I'm doing something wrong...

I wasn't saying your permission plugin would support it, I was saying that it's up to the permissions plugin to support it