submission/listing-and-prompts.md

# Public Listing

## Name
Web App QA & Release Copilot

## Subtitle
Test web apps before release

## Category
Developer Tools

## Description
Web App QA & Release Copilot helps you test web applications, triage defects, scope regression, and make evidence-based release decisions. It can map critical user journeys, review screenshots, test output, traces, logs, and pull-request context, design focused Playwright coverage, assess cross-browser and responsive behavior, review accessibility against current WCAG guidance, analyze Lighthouse and Core Web Vitals evidence, check security and privacy release risks, and verify deployment, rollback, smoke-test, and post-release monitoring plans. It distinguishes observed evidence from inference, prioritizes real user impact, and avoids declaring a release ready when key evidence is missing.

## Capabilities
- Audit web-app release readiness across functional, browser, accessibility, performance, and security risks
- Map critical user journeys into focused end-to-end tests and release smoke checks
- Scope targeted regression from changed code, dependencies, data, configuration, and adjacent workflows
- Triage bugs with reproduction steps, evidence, severity, likely layer, and next verification
- Design resilient Playwright tests around user-visible behavior, locators, traces, and browser projects
- Review responsive layouts, touch behavior, supported browsers, and visual-regression evidence
- Audit keyboard, focus, semantics, forms, dynamic updates, contrast, zoom, and screen-reader requirements
- Interpret Lighthouse, Core Web Vitals, network, JavaScript, image, font, and field-performance evidence
- Review auth, authorization, sessions, uploads, APIs, secrets, privacy, and deployment-security risks
- Produce Ready, Ready with known limitations, or Not ready verdicts tied to explicit evidence and blockers

## Starter prompts
1. Audit this web app or PR for release readiness and identify blockers.
2. Build a focused regression and smoke-test plan for these changes.
3. Turn this bug, screenshot, or failed test into a reproducible QA report.