5 10 min

QA: check the site

Role
QA
Outcome
Your site, checked and fixed, legal page included
Time box
10 minutes

QA finds what is wrong with your site, explains it in plain words, fixes it and proves each fix. It checks the look, accessibility (whether everyone can use the site), how fast it loads on a phone, and your legal page.

Get ready 1:00 min

QA lists what is wrong with your site, fixes it and shows the evidence for each fix. Your part: read its findings, and ask for the evidence when it does not show it.

Work with QA 5:00 min

QA leads you through this Block in the chat and says when it is done. Read this part first, then start QA at its end, under Now start QA. Keep this page open next to the chat.

Let it look and audit

QA works for a few minutes. It takes screenshots of your pages, measures your home page on a slow phone connection and runs the Check (the script that tests your site). Your part:

Then it fixes one finding at a time and shows the evidence for each fix. It also reports two numbers: LCP, how long until the main content shows (good: 2.5 seconds or less), and CLS, how much the page jumps while it loads (good: 0.1 or less).

Now start QA

In the Antigravity CLI, type /clear and press Enter. It resets the context window, so this Role starts in a fresh chat.

Then type:

Agent chat

Start the QA step.

When QA says it is done, check its work yourself in Check and accept below.

Check and accept 4:00 min

Run the Check yourself

Even if QA says everything passes, run the Check yourself: an agent can say "fixed" without checking. Open a second terminal window, next to the Antigravity CLI. Type cd YOUR-REPO and press Enter. Then paste this (Cmd+V on a Mac, Ctrl+V on Windows, Ctrl+Shift+V on Linux) and press Enter:

Terminal · same on Mac, Windows and Linux

node tools/check.mjs

It prints one line per item, PASS or NEEDS ATTENTION:

What you see (the end of it)

  PASS             Content file matches the schema
  PASS             Accessibility (the axe rules Lighthouse scores)
  PASS             No errors in the browser console
  PASS             What an agent sees: your content without JavaScript
  PASS             Legal page written

5 of 5 items pass.
This Check only reports. It never stops you from publishing.

Two more lines after it, starting with Clock: and Pace:? That is QA's clock: how much time QA has left, for the agent. Nothing to do.

Look at the screenshots

Open the folder qa inside your YOUR-REPO folder (Finder, File Explorer or Files) and double-click a screenshot, for example index-phone-dark.png. Text cut off, overlapping or hard to read? Tell QA in one sentence.

In the preview, click Legal notice & privacy at the bottom of your site (Note legali e privacy on an Italian site). The page has three parts: a legal notice (who runs the site and how to reach them), a privacy notice and an accessibility statement. It is not legal advice: for a site that sells services, have it checked by someone who knows the law in your country.

If something goes wrong

Ask your agent first. In a fresh chat, type the question below: it reads your repo and tells you what is done and what comes next. Got an error message? Paste it into the chat.

Agent chat

Where am I?
"Google Chrome was not found"

Fix: install Chrome from google.com/chrome, then run the command again.

"Cannot find module" when you run the Check

Cause: the terminal is not in your YOUR-REPO folder.

Fix: type cd YOUR-REPO and press Enter, then run the command again.

QA goes round in circles on one finding

Fix: after two attempts, stop it. Start a fresh chat, type Start the QA step. again and name the one finding to fix.

Fell behind?

The QA Block's time is up and QA is not done? Look at your page in the preview first.

  1. The agent is still working? Press Esc in the Antigravity CLI to stop it.
  2. Open a second terminal window, next to the Antigravity CLI. Type cd YOUR-REPO and press Enter. Then paste this command (Cmd+V on a Mac, Ctrl+V on Windows, Ctrl+Shift+V on Linux) and press Enter:

Terminal · same on Mac, Windows and Linux

node tools/checkpoint.mjs qa

Use the Block that has just ended, not the one that starts now.

It lists what it kept and what it changed, and ends with what to do next. Nothing to change means you were already there. Two Blocks behind? This one checkpoint includes the earlier Blocks.

Or start a fresh chat and let the agent run it:

Agent chat

Catch me up: the room just finished the QA block.