qa-testing

# QA Testing Verify that a page, feature, or site is working before declaring it shipped. Stack-agnostic. Console-snippet driven for speed. This skill is faster than `accessibility-audit` (which goes deeper on WCAG) and `performance-optimization` (which goes deeper on Core Web Vitals). Use this skill for general QA. Use the specialists for deep audits. --- ## When to use - After every deploy (smoke test) - After launching a new page or feature (standard audit) - Before a major release (full release matrix) - Investigating a "something looks off" report - Pre-launch verification of a site or section ## When NOT to use - Deep accessibility compliance work (use `accessibility-audit`) - Deep performance investigation (use `performance-optimization`) - Code review or debugging (use `code-review-web`) - Initial site setup or technical SEO baseline (use `seo-technical`) --- ## Required inputs - The page URL or site under test - The tier of QA needed (smoke, standard, or full) - Browser dev tools access - Any specific concerns to check beyond the standard tier --- ## The framework: 3 tiers QA scales with the stakes. Pick the tier that matches the context. | Tier | When to run | Time | Coverage | |---|---|---|---| | Smoke | After every deploy | 2 minutes | Critical signals only | | Standard | New page or feature | 10 minutes | On-page basics, accessibility, structure | | Full | Major release, pre-launch | 30+ minutes | Comprehensive across all dimensions | ### Tier 1: S...