Run cross-browser QA for websites and apps. Use before production or after CSS, media, forms, animation, canvas, layout, or interaction changes to test Chromium, WebKit/Safari-like, and Firefox behavior, browser-specific CSS/media issues, focus/keyboard differences, and responsive rendering.
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Run cross-browser QA for websites and apps. Use before production or after CSS, media, forms, animation, canvas, layout, or interaction changes to test Chromium, WebKit/Safari-like, and Firefox behavior, browser-specific CSS/media issues, focus/keyboard differences, and responsive rendering.
Cross Browser QA
Use this skill to catch browser-specific issues that one local Chromium pass will miss.
Workflow
Inspect the project, scripts, routes, local/deployed URL, production surfaces, and available QA/deployment tooling.
Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.
Always Protect
Inspect before changing or shipping: framework, package scripts, build output, routes, forms, media, animation stack, deployment target, environment variables, analytics, SEO metadata, accessibility risks, and available browser QA tooling.
Do not claim something was tested unless it was actually tested; report exact commands, URLs, screenshots, viewports, failures, skipped checks, and remaining risk.
Verify desktop and mobile rendered output, not only source code. For visual or motion work, inspect screenshots, browser behavior, console errors, network failures, and responsive layout.
Treat forms, checkout, booking, CMS content, analytics, environment variables, and deployments as production surfaces with error, loading, empty, success, and rollback states.
Respect accessibility, performance, reduced-motion, and no-JavaScript/no-WebGL/no-autoplay fallbacks where relevant.
Keep secrets out of code, logs, screenshots, summaries, widgets, and committed files.
Prefer project-local tooling and existing scripts before adding dependencies. Explain any new dependency before installing it.
End with a concise handoff: changed files, commands run, checks passed, checks not run, deployment URL if any, and next risks.
