QA

Step 1: Load Context

1. Read verbs config from CLAUDE.md or AGENTS.md (whichever the project uses). Resolve {learnings_dir} from it (default docs/learnings).
2. Search {learnings_dir} for type: pitfall related to UI or the changed components. The type: pitfall shape is defined in lib/learning-format.md.
3. Read the brief (if exists in docs/briefs/) to understand expected behavior.

Step 2: Plan Tests

From the diff, brief, or user instructions, identify what to test.

Round 1 - Functional: What are the core user flows? Write each test as: action -> expected result.

• Which pages/URLs changed?
• What should work after this change?

Round 2 - Adversarial: Re-read Round 1. What did you miss?

• Error paths, empty states, loading states
• Edge inputs (empty, huge, special chars, rapid clicks)
• Double-submit, Escape mid-flow, keyboard-only nav