All pages
When to use it
View Markdown
For agents
This page is also Markdown. llms.txt lists every page, and llms-full.txt holds them all in one file. The skill teaches a coding agent to run ra by itself.
A browser check costs more than a unit test: each look loads the page in a real browser and waits for it to settle, and browser tests flake more than most (how it compares). So ra is worth running when the answer depends on what a browser paints.
Use ra when:
- The question is “what does a person see here?” For example, whether this fits at 320px, whether dark mode keeps the text readable, whether anything covers the button, and whether the long name spills out of its card. Only the layout engine knows, because the answer depends on the fonts, the cascade, and the width of the screen.
- The state is expensive to reach by hand. Examples are an empty inbox, a failed payment, a 3,000-row table, an upstream returning 500, a name 80 characters long, or a clock just before midnight. You name each one once as a URL plus a fake world, and from then on one command reaches it.
- A change has a visual blast radius. Examples are a CSS refactor, a design-token change, or a dependency bump. Run
ra snap, make the change, then runra diff. It tells you which elements moved, resized, appeared, or vanished, which outline lines changed, and which findings are new. - An agent is changing UI. It works from text it can act on, and opens a picture only when the text is not enough.
Do not use ra for:
- Logic. If it can be tested without a browser, test it without one.
- Restating the implementation. Asserting
toHaveCSS("color", "rgb(…)")or a class name proves that you wrote what you wrote. ra asks what a person would ask instead: whether the text can be read, whether the control can be reached, and whether it fits. - Proving a live system works. ra closes the world on purpose. Smoke tests and monitoring against real services do that job.
ra check --url https://…against a deployment checks what the deployment shows, and the outside world stays closed even then. - Pixel baselines in CI, or coverage ledgers. Rendering varies from host to host, so a baseline holds only where it was made (design decisions). Snapshots in ra live on your machine for the length of one change. CI runs
ra check, which has no baselines. - Cross-browser matrices. ra drives Chromium only. Use Playwright Test when WebKit- or Firefox-specific behaviour matters.
- A full accessibility audit. ra reports what a person would trip over: unnamed controls, missing alt text, low painted contrast, and small tap targets. Run axe or a manual audit for the rest.
Limits
- ra drives Chromium only, on macOS and Linux.
- It is not a full accessibility audit.
- Placeholder text is not checked for contrast yet.
- Contrast is read from painted pixels, so text close to a threshold can pass under one system's font rendering and fall short under another's.
- Pictures and contrast cover at most the first 12,000px of a page. ra says so when a page is taller.
- When a page scrolls inside an element rather than as a whole, its pictures show that element's first screen, and ra says so.