Capture EdgeQuake WebUI routes with Playwright and write artifacts immediately (screenshots + per-page request JSON + capture index). Use when adding/updating Playwright E2E capture specs or when asked to automate UI screenshot collection.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Use this skill when implementing or modifying Playwright E2E to:
edgequake_webui/playwright.config.tsedgequake_webui/e2e/ux_ui_map/ (repo root)Prefer enumerating concrete page.tsx files under edgequake_webui/src/app/**/page.tsx.
(dashboard) do not appear in URL paths.[param], [...param], [[...param]] are not capturable without fixture data.Helper script (no dependencies):
Example:
node .github/skills/playwright-ux-ui-capture/scripts/derive_routes.mjs --format json
Capture exactly these 3 widths (use a reasonable height):
main or h1).waitForLoadState('networkidle') as the primary sync.For each route:
ux_ui_map/screenshots/{page}/desktop.png, tablet.png, mobile.pngux_ui_map/requests/{page}.json from the templateux_ui_map/capture-index.jsonlFrom repo root:
cd edgequake_webui && npm run test:e2eTo run a single spec (preferred while iterating):
cd edgequake_webui && npx playwright test e2e/<spec>.spec.tsEach line is a standalone JSON object:
{"page":"dashboard","route":"/","capturedAt":"2025-12-26T12:34:56.000Z","ok":true}/login first and then attempt the route.ok:false and store a screenshot of the error state.62e6adb
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.