A UI component library telling you not to reinvent the wheel by reinventing the wheel.
@matuzo If you wanted to style a link like a button, say a "View" link that takes you elsewhere, this could be a decent approach, no? Whereas actual buttons (the kind that trigger an action _on the page_, or submit a form) might not need these classes (or maybe in your app they do, to keep things consistent). Like "View," "Edit," "Delete" "buttons" that you may want to style similarly (and where Edit and Delete trigger a POST/PATCH/PUT/DELETE request rather than a GET request)?
@matuzo (In the same vein, I often have, e.g., "Mark as Read" "links" that are in fact buttons triggering a POST request. [Because GET requests shouldn't change state, yadda yadda.])
@janboddez That's what I do, my understanding is that it's correct. It's more important to keep the meaning of buttons-as-action for screen readers, even if they are styled without a background/border or padding.