[Feature request] Discourage developers from creating custom classes with same name as existing Tailwind classes

[ssalib-aamc]

Is your feature request related to a problem? Please describe.
It's easy to create a css class that has the same name of existing Tailwind class because most developers don't have all Tailwind classes memorized.

Describe the solution you'd like
We would like to show a warning (possibly an error) when developers attempt to add a new template css class with the same name of a Tailwind utility class. Example: "container" or "p-0" in our .scss files should trigger a linting warning/error.

Describe alternatives you've considered
We do not want to use a Tailwind pre-fix to respect the advantages of atomic css classes terse short-hand nature.

Additional context
We can start with the obvious one to one match such as "container" and then move to more complex cases such as "p-" or "m-" followed by a number.
It would be great if we have control to set this rule as a warning OR error based on our code state and preference.

[TheElegantCoding]

This is good but I think don't fit this package, this is more for css files or other files where you can create that class, it's more hard to implement