visual-qa
/visual-qa
Weryfikuje zmiany interfejsu w przeglądarce Playwright: zrzuty przed i po, motywy jasny i ciemny, kontrole układu i testy e2e.
- Autor
- lemramimel ↗
- Repozytorium
- agent-team ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 06.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Weryfikuje zmiany interfejsu w przeglądarce Playwright: zrzuty przed i po, motywy jasny i ciemny, kontrole układu i testy e2e.
Oryginalny opis (EN)
Verify UI changes in a real browser with Playwright: before/after screenshots, light/dark themes, layout checks, e2e specs that stay green. Use for any change that affects what the user sees. Tests only, never edits production code.
Jak działa
- Before you start
- Capture
- Look at the pictures
- Pitfalls seen in practice
- Reporting
Podgląd SKILL.md
--- name: visual-qa description: Verify UI changes in a real browser with Playwright: before/after screenshots, light/dark themes, layout checks, e2e specs that stay green. Use for any change that affects what the user sees. Tests only, never edits production code. --- # Visual QA with Playwright Code review and unit tests do not catch visual regressions. This skill is the procedure for checking them in a real browser. It uses the project's own Playwright setup (`@playwright/test`, its `playwright.config.*`, its existing mocks); it does not need a Playwright MCP server. ## Before you start 1. Read the project's `playwright.config.*` and two existing specs: port, base URL, viewport, how the server starts, how the API is mocked. 2. Check the port is free: `ss -ltnp | grep <port>`. Stop only servers you started yourself. 3. If the project has a CI mode (for example `CI=1` serving the production build), use it: build first, then `CI=1 npx playwright test`. Do not run `next dev` or any dev server at the same time as a build: they share the build folder and break each other. ## Capture - Temporary capture specs go under the project's e2e folder with a `zz-` prefix and are deleted afterwards (`ls e2e | grep zz` must print nothing). - Screenshots go to the session scratchpad, never into the repository. - Fixed viewport (use the project's, e.g. 1920x1080). Wait for fonts and images before shooting: for images, wait until `img.complete && img.naturalWidth > 0`; a missing logo on a capture is often just timing. - Set the state before page load (`page.addInitScript`: localStorage theme, cookies), not after. - Mock the API with the project's existing full mocks. Empty mocks crash pages that expect arrays or nested objects, and a crashed page is not a result. ## Look at the pictures Open every screenshot with the image reader and describe it. A green test proves the assertions passed, not that the screen is right. - **Before/after**: capture the same screen on the base branch and on the change. The base build comes from a temporary worktree of the base branch, created and removed by Gita; Quinn only builds and captures there. State what differs, and whether each difference is intended. - **Themes**: light and dark side by side. Look for white blocks, unreadable text, low contrast, invisible logos or icons, borders that vanish. - **Light must stay identical** when the change only targets dark: text sizes, wrapping, spacing, colors of statuses. - **Overlays**: dev-server error overlays and indicator bubbles are not product defects, but note them. ## Pitfalls seen in practice - A utility class may not mean what its name says if the project overrides the scale (for example `text-sm` set to 15px while the old inline style was 14px). A converted style can wrap text or shift layout. Compare computed sizes, not class names. - A dev server that dies mid-run gives `ERR_CONNECTION_REFUSED` and looks like a flaky test. Prefer the built app in CI mode. - A second server on the same port makes the next run fail with "already used". Check ports before and after. - Flash-of-wrong-theme tests: abort the JS chunks, load the page, and assert the state on `domcontentloaded`. ## Reporting - Verdict PASS or FAIL. - Per screenshot: file, what you see, defects with severity and the suspected file. - Spec runs: command, and the result of each of at least 3 consecutive runs for a new or rewritten spec. - Full suite once at the end, in CI mode: pass count. - Confirmation that no server or `zz-` file is left behind.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · lemramimel/agent-team | 100 | MIT |
| mcorbett51090/ravenclaude | 100 | MIT |
| code-yeongyu/lazycodex | 100 | MIT |
| KILN-skills/kiln | 100 | MIT |
| nimadorostkar/Claude-Skills-collection | 100 | MIT |
| dylanfeltus/skills | 100 | MIT |
| Lrinvl1203/world-class-web-design-os | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 7c6882440d17 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100visual-proof
Robi zrzuty ekranu strony przed i po zmianie w punktach 375, 768 i 1440 px w motywach jasnym i ciemnym przez Playwright, aby udowodnić różnicę wizualną. - 100playwright
Uruchamia testy E2E w Playwright z widocznym Chrome, robi zrzuty ekranu, sprawdza przepływy użytkownika, układ responsywny i dostępność w prawdziwej przeglądarce. - 100game-e2e-integration-qa
Uruchamia w przeglądarce scenariusze Playwright, zrzuty ekranu i testy regresji całych przepływów po zmianach w grze. - 100playwright-e2e
Testuje aplikację webową end-to-end w Playwright: pisze specyfikacje, obsługuje strony wymagające logowania, robi zrzuty ekranu i uruchamia testy w CI, aby zmianę sprawdzić w prawdziwej przeglądarce. - 100playwright-testing
Automatyzuje testy UI i E2E z Playwright MCP: sprawdza stronę, robi zrzuty ekranu, uruchamia Playwright i pisze testy przeglądarkowe. - 90verify-ui
Sprawdza zmianę interfejsu w przeglądarce: uruchamia serwer, robi zrzuty ekranu w telefonie i na komputerze oraz szuka błędów układu.