---
name: page-testing-memory
description: Use when testing or documenting app pages so guided verification becomes repo-local page test recipes instead of polluted global instructions.
---

# Page Testing Memory

Use this Antigravity CLI skill when the user asks to test, smoke-test, QA, verify, or document a page or workflow.

## Protocol

1. Find the repo-local testing runbook before testing.
   - Check `docs/current/page-test-runbook.md`, `docs/testing.md`, `TESTING.md`, `docs/qa.md`, `.agents/rules/`, `.agents/skills/`, `GEMINI.md`, and project-specific docs.

2. For an undocumented page, prefer a human-guided first pass.
   - Ask the user to direct one action at a time.
   - Capture purpose, role/account, preconditions, success signal, safe actions, unsafe actions, selectors, cleanup, and seed data.

3. Verify with evidence.
   - Prefer local/staging unless production is requested.
   - Stop before destructive, expensive, batch, publish, queue, delete, email, payment, or media-generation actions unless authorized.

4. Update the repo-local recipe.
   - Use `starter`, `guided`, `tested`, or `needs repair`.
   - Include exact repeatable steps, cleanup, checkpoint seed data, and selector lessons.

5. Classify new lessons.
   - Global reusable lesson: improve this skill.
   - Repo lesson: update the repo runbook or rules.
   - Page lesson: update the page recipe.
   - Temporary observation: report only.

## Page Recipe Template

```md
## `<route-or-workflow>`

Status: starter | guided | tested | needs repair

Purpose:

Role/account:

Preconditions:

Safe actions:

- TODO.

Unsafe actions:

- TODO.

Verification steps:

1. TODO.

Cleanup:

- TODO.

Checkpoint seed data:

- TODO.

Known selector/flow lessons:

- TODO.

Last verified:

- Date:
- Environment:
- Evidence:
```