All pages
How it works
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.
Mocking
The world
Replies you write.
Anything else is stopped.
Real browser
Your app
Unchanged, at each screen size you list.
Perception
The look
Measures the page, with no AI model.
What your agent reads
cut-off "Subscribe to updates" is cut off on the right by its own box (84px hidden).
covered button "Pay now" is covered by span.veil; a click or tap on it would land on that instead.
ra has two halves, and your app runs unchanged between them. Nothing runs inside your app: there is no SDK, bridge, test build, or fixtures database.
The world: the mocking half
The world is everything outside your app, and you describe it in ra.config.ts. It decides what each request gets, in this order:
- A reply you wrote (
replies) answers in the server's place. - A host you block (
block), such as analytics, is dropped quietly. - The app itself answers its own paths.
- A host you allow (
allow), such as a font CDN, is really reached. - Anything else is stopped and reported as an
outsidefinding.
The broken fixture page makes seven requests. The app answers five, and the two to api.example.com and analytics.example.com, which nothing in its world answers, are stopped and reported.
Beneath those rules the browser itself is closed, so what routing never sees, such as a redirect hop, an IP address, or a WebRTC connection, is stopped too (the browser says how). ra doctor tries four ways out, and each must be stopped. The world stays closed when ra looks at a deployment, too.
A state is a URL into a world: a path, plus the replies, storage, cookies, and clock that go with it, and optional steps. You name each state once, such as an empty inbox, a failed payment, or a name 80 characters long, and ra looks at it through every view you list, such as desktop, a phone, and dark mode. Stand-in servers (upstreams) answer what your app's server calls.
The look: the perception half
The look reads the page five ways, and no model takes part in any of them:
| Reading | How ra takes it | What it finds |
|---|---|---|
| Boxes | The layout engine's own rectangles for each element and each line of text, set against the screen, the boxes that clip them, each other, and each image's own size. | page-scroll, cut-off, spill, overlap, small-target, image, blank |
| What is on top | The element the browser reports on top at the centre of each control, tested as ra scrolls down the page in half-screen steps, up to 40 screens. | covered |
| Two pictures | The page as it is, and the page with every glyph made transparent, which shows the true background under each line of text, whatever painted it: a gradient, a photo, an overlay, or a blend. | contrast |
| Roles, names, and the document | Each control's role and accessible name, which ra also prints as the outline, and the page's title, viewport, and response status. | no-name, document, error-overlay |
| The console and the network | Every error logged and every request made, until the network has been quiet for 200 ms or 5 seconds have passed. | console, request, outside, load, busy |
Your own checks add the last two kinds, expect and steps.
What comes out is text first, with two pictures for when the words leave a doubt. ra check takes the same look at every state through every view, and exits 1 when anything is wrong.