Stack

Adams forTailwind projects.

Utility classes make a layout quick to write and easy to break at one width. Adams checks the result.

Pro
// the problem

What goes wrong

Breakpoints are guessedAn AI adds a class for one breakpoint and forgets the others. The card grid works at 1280 and collapses at 768.
Counts that do not fill the gridFive cards in a three column grid leave a lone card on the last row. It looks unfinished, and the code looks fine.
// what adams does

What Adams does

Measures the rendered gridPro: uneven rows, overlap and wrapped short labels are reported by width and element.
Keeps a rule for next timePro: coach stores "equal cards per row" so the next session starts with it.
Reviews the diffPro: the separate reviewer flags class changes with side effects.
// worked example

An example

Five cards in three columns

Illustrative output.

~/project~/your-project · example
$ adams check http://localhost:3000/features
1280px: last row holds 2 of 3 cards
Moving to 6 cards
✓ 3 widths checked, no problems
// faq

Questions

Does it work with plain CSS?

Yes. It checks the rendered page, whichever way it was styled.

Will it rewrite my classes?

No. It reports. Your AI or you make the fix.

Why is this Pro?

Page checks at three widths are Pro.

// related

Keep reading