qalisted

# Axon QA Use this to test a live site and return a unified QA report. ## Onboarding Interview Infer the URL, QA focus, and output format from context. If the target URL is clear, proceed immediately. Ask at most 1-3 concise questions only if blocked, such as the URL, the focus area, or credentials/constraints for protected flows. ## Axon Collection Plan Use `axon map` to discover pages, `axon scrape` for content and link evidence, `axon screenshot` for rendered state, and `axon endpoints <url> --include-bundles true --capture-network` for API, bundle, and network-surface evidence. Use `axon <url> --scope site --render-mode chrome --automation-script ... --wait true` for repeatable click/scroll/load-more capture before escalating to a live browser tool. For forms, responsive checks, console errors, and detailed reproduction evidence, use Webwright/Playwright or the host browser automation tool after Axon has collected the URL/content/API evidence. ## Parallel Work If appropriate, use sub-agents or equivalent parallel task runners: - Full: Navigation and Links, Forms and Interactions, Content and Visual, Error States. - Forms: Form Discovery, Happy Path, Edge Cases, Validation. - Navigation: Sitemap, Nav Testing, Link Checker, Routing. - Responsive: Desktop, Tablet, Mobile, Interaction. - Performance: Page Load, Asset Audit, Content Efficiency, Comparison. Each tester should return severity, URL, description, evidence, and reproduction steps. ## Final Deliverable