GenClass

What GenClass measured about the app. local: per-endpoint request counts, median and p95 latency, error rates and failure streaks; per-page runs, errors and overwritten fields; learned relations between fields and learned flows, from pages on this machine. production: the GenClass dashboard's sessions, detections by diagnosis and page, and latest decisions (needs GENCLASS_DASHBOARD, the dashboard's private link; "sample" reads the public sample).

Forget recorded runs and findings on this machine (all, findings or runs), e.g. after a fix to start clean.

Everything about one finding: what happened in causal order (click → request → response → state write), the recorded steps and delivery order, what differed from the request-order baseline, the model's facts, how to replay it exactly, and a Playwright regression test that fails while the bug is there.

Find races before users do. action "start" arms the next page loads: 2 baselines with responses in request order, then `runs` loads where overlapping responses arrive in a seeded different order (optionally slower, or with `focus` endpoints last). Run the same scenario once per armed load, then action "report": each load's final state is compared with the baseline; a difference in what the page shows, its form values, the requests it sent or its errors depends on network timing (a race), and comes with a seed that replays it. Store values that differ while the page is the same are listed apart as internal state. Without `route`, the page of the first armed load is the page under test; set `route` when the scenario loads several pages. Armed loads expire after 30 minutes. "stop" disarms.

What GenClass recorded in pages on this machine, ranked and deduplicated with counts: races found by explore (final state depends on response order), responses that overwrote newer data, uncaught errors (with the click and request before them), the same request sent twice by two clicks, the on-device model's detections, visual checks. Use when the user reports an intermittent bug, after changing data-fetching or submit code, or before saying a UI change is done.

Reproduce one finding exactly. action "arm": the next page load of the finding's route gets the delivery order that produced it; do the same steps (genclass_explain lists them). action "result": whether that replay reproduced it. Use before a fix to confirm the bug and after it to prove the fix.

Audit one page in one step with GenClass's 23 measured visual checks: text you cannot read against its background, images, fonts, stylesheets and media that failed to load, a page that scrolls sideways on a phone, controls stuck under fixed bars, layers that swallow clicks, covered dialogs, template leaks like {{name}} or [object Object]. It loads the URL headless at desktop and phone sizes in Playwright's Chromium on this machine (when that is missing it says how to install it); hosted: true runs it on the genclass.dev page check instead, which adds accessibility, speed and security audits, takes public pages only and is the one case where the URL leaves this machine and returns a score and each problem with its element, selector and a suggested CSS fix, worst first, plus the JSON report. Use it before you call a page or UI change done, after CSS or layout changes, and on a site you do not own. Works on any URL, including the dev server (http://localhost:5173/); no page needs GenClass installed.

The lines to add so this project's dev build connects to GenClass (detects Vite, Next.js and others from package.json), how to check it works, and this MCP client's config lines for keeping the server configured. It changes no file.

Which pages on this machine are connected to GenClass (route, schedule, model state), counts of findings by kind, the explore session and armed replays. Call it first in a web project, and before you test a page.