Clean up class strings.
Tailwind's utility classes are fast to write and miserable to read once a className string runs forty tokens long. Everyone on the team orders them differently, so diffs churn on nothing and nobody can find the one margin utility in the pile. There is an official recommended order, but applying it by hand is exactly the kind of tedious no one keeps up. This blueprint builds the sorter so the string organizes itself.
A Tailwind class reorderer. You give it a class string and it returns the same classes in the official recommended order: Layout first, then Box Model, then Typography, then Visuals, then everything else. Nothing is added or removed, the utilities are just sorted into a predictable sequence, so every string across your codebase reads the same way and the important classes sit where you expect them.
You watch it come together in the task workspace: the agent scaffolds the tool, wires the ordering logic against the recommended groupings, and runs a messy class string through it to confirm the output before handing you a live preview. The code lands on a branch in your repository with a pull request ready.
The first version sorts one string at a time and grows with plain follow-up messages:
Each follow-up wakes the same repository and the agent continues on its own code.
Does it change what my classes do? No, it only reorders; the exact same utilities come out, just sorted into the recommended sequence, so nothing about your styling changes.
What order does it follow? The official recommended grouping, Layout, then Box Model, then Typography, then Visuals, then miscellaneous, applied consistently to every string.
Can it handle a whole file? One string is the starting point; ask it to process a full file and it sorts every class attribute it finds.