devinschumacher/skills

Overview

This skill is the canonical Playwright hub for end-to-end tests and ad-hoc browser automation. It focuses on @playwright/test suites, debugging flaky UI tests, visual testing, and one-off automation tasks like screenshots and logs. Use it only when Playwright is explicitly requested or referenced in the project context.

How this skill works

The skill routes requests into the right workflow: test suite changes, ad-hoc scripts, debugging with trace viewer, or CI hardening. It enforces patterns that reduce flakiness (locators, web-first assertions, fixtures) and standardizes artifact storage under ./tmp/playwright for predictable cleanup. It also provides verification steps and CI-oriented commands to validate fixes.

When to use it

• User mentions Playwright, @playwright/test, npx playwright, playwright.config.ts, PWDEBUG, trace viewer, or toHaveScreenshot
• Working on E2E or smoke coverage for a web app
• Debugging flaky UI tests, selectors, timing, or waits
• Creating one-off automation: screenshots, console logs, quick flow checks
• Implementing visual testing or storageState-based auth reuse

Best practices

• Prefer getByRole/getByLabel over CSS/XPath; add data-testid only when necessary
• Use web-first assertions like await expect(locator).toBeVisible() rather than boolean checks
• Avoid waitForTimeout() as a permanent solution; only use briefly while debugging and remove before finalizing
• Don’t default to networkidle; choose it intentionally for SPAs or known background activity
• Store artifacts under ./tmp/playwright and use minimal reporters for CLI runs to reduce log spam
• Keep tests independent and avoid shared cross-test state

Example use cases

• Add or maintain @playwright/test suites and fixtures for a web app
• Debug flaky tests using trace viewer, retries, and selector improvements
• Create an auth-once workflow using storageState for repeated test runs
• Run CI-hardening checks and confirm behavior with CI-like environment variables
• Run quick ad-hoc scripts to capture screenshots, console logs, or smoke-check a flow