Ask an agent to “make the pricing card feel tighter” and you often get a className novel: spacing, colors, type scale, shadows, and a responsive grid rewrite in one PR. Reviewers can’t tell which change fixed the density problem and which ones were drive-by taste.

I’ve started capping agent Tailwind work to one utility family per PR . Spacing or color or typography or layout — not all four because the model felt creative.

What counts as a “family”

Group the way reviewers actually skim class strings:

Spacing — p-* , m-* , gap-* , space-* , and related inset padding/margin

Sizing — w-* , h-* , min-* , max-* , size-*

Color — bg-* , text-* , border-*-* (color), ring-* , fill-* , stroke-* , opacity modifiers on those

Typography — text-* sizes/weights ( text-sm , font-medium ), leading-* , tracking-* , font-* families

Layout — flex , grid , items-* , justify-* , col-span-* , order / place utilities

Effects — shadow-* , opacity-* , blur-* , transitions / animations

Pick one family as in-scope.…