You can still call it a banana in Tailwind, but you'd do it with a component in your framework rather than a class name. If you plan on using bananas multiple

You can still call it a banana in Tailwind, but you'd do it with a component in your framework rather than a class name. If you plan on using bananas multiple times throughout your app, aren't you going to be pulling that out into a component anyway? So define that it's curved and sweet and yellow in that one place, and then insert an instance of it wherever necessary.