Put a class list back in order: layout first, then the box, then what is inside it, with variants after the base classes they modify.
The result appears hereNot to the browser, which reads the stylesheet rather than the attribute. It matters to readers and to diffs: a consistent order means two components with the same classes look the same in review.
It follows the same idea, layout outwards and variants last, over a property table rather than Tailwind's own resolved config. Use the plugin in your repository; use this for a class list you are reading somewhere else.
They keep their relative order and go last, and they are listed under the output. That includes your own utilities and anything from a plugin, which no static table can place correctly.