Update to Web App QA & Release Copilot

{
  "description": "Review layouts, interactions, browser compatibility and screenshot regressions on target devices.",
  "included_files": [],
  "name": "review-visual-responsive",
  "skill_md_contents": "---\nname: review-visual-responsive\ndescription: Review layouts, interactions, browser compatibility and screenshot regressions on target devices.\n---\n\n# Review Visual Responsive\n\n**Use when:** The request concerns mobile, browser, visual diffs, responsiveness, touch, UI polish or inconsistent rendering.\n\n## Workflow\n1. Identify required viewport and browser matrix from support commitments and product traffic; do not invent a full-device requirement.\n2. Inspect supplied screenshots or render pages when tool access permits, including overflow, truncated labels, focus, touch targets, keyboard and responsive navigation.\n3. Compare with approved baseline; account for font, OS, pixel ratio, animation and image differences.\n4. Categorize differences as intentional, user-visible regression, rendering noise or needs human adjudication.\n5. Check reduced-motion and zoom/reflow states where applicable; distinguish visual preference from real usability defects.\n6. Document exact coordinates/viewport/browser and evidence, then propose the smallest layout or test change.\n\n## Non-negotiable checks\n- Do not use screenshot pixel equality as sole release gate.\n- Never claim desktop, mobile or Safari passes without actual evidence.\n\n## Deliverable\nVisual findings linked to renders and their user impact.\n\n## References\n- Read `../../references/visual-responsive.md` when relevant.\n- Read `../../references/evidence-model.md` when relevant.\n\nOnly claim tests, browser access, scans, deployments or specialist execution supported by actual tool evidence. Retain original user constraints and avoid unsolicited code changes.\n"
}