Is generated @utility placement *above* built-in utils guaranteed behavior?

[happycollision]

I noticed using the TW playground that when I define a utility, the generated CSS always places that utility above any first-party Tailwind utility that also manipulates the same css properties.

This means, effectively, that any simple utility I define can be overridden by any of the TW utilities.

Is this behavior a guarantee? I would love to use this in a similar way to the components layer, with the added benefit of all the IDE support you get with utilities.

[wongjn]

I think there is some intentionality to the order of utilities, especially if they may share properties. See #16715

[happycollision]

Interesting how it seems like they are counting the properties in that PR, but the behavior I am seeing suggests more than that. (Or perhaps they are counting instances of the same property?)

What I really want to know is if we can, as developers, depend on this ordering logic remaining the same? (I just added a gif to the original post to demonstrate.)

I know there is consternation about the internal order of utilities that manipulate a single property changing in v4 (e.g. flex and inline), but for user-defined utils, it sure seems intentional (though not documented as a guarantee) that they will be hoisted above any first party utils that manipulate any of the included properties.