Stack

Adams forReact apps.

Components pass in the demo and fail on real data. Adams checks the rendered page at three widths.

Lite and Pro
// the problem

What goes wrong

Demo data is kindA card with a short name fits. The customer with a long name pushes the layout apart. The empty list shows nothing at all.
Reviewing JSX is not seeing the pageA diff of components does not show a wrapped button label. Only the rendered page does.
// what adams does

What Adams does

Looks at the rendered resultPro: the running app is opened at 375, 768 and 1280 pixels and faults are named.
Reviews the change separatelyPro: a second agent ranks findings such as missing states and unchecked input.
Guards keys in client codeLite: anything bundled to the browser is public, and a key there is caught at commit.
// worked example

An example

A list with a long name

Illustrative output.

~/project~/your-project · example
$ adams check http://localhost:5173/customers
375px: long customer name overflows the card
768px: rows have different heights
Truncating the name, fixing row height
✓ 3 widths checked, no problems
// faq

Questions

Does it understand my components?

Your AI does. Adams checks the result in the browser.

Can it test state logic?

No. Use your own tests for that. Adams can run the project checks you already have.

Is the page check free?

It is Pro.

// related

Keep reading