Menu
Playwright 浏览器与 E2E 测试。需要加跑调前端测试，或 runtime-verify 要验证 UI 流程时触发。
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/WenJunDuan/Rlues --skill playwrightThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Based on SOC occupation classification
| name | playwright |
| description | Playwright 浏览器与 E2E 测试。需要加跑调前端测试，或 runtime-verify 要验证 UI 流程时触发。 |
Use Playwright when the acceptance signal depends on a real browser: routing, forms, auth flows, rendering, navigation, API-backed UI state, responsive layouts, downloads/uploads, or regressions that unit tests cannot see.
For Athena v9.8.0, this skill is the frontend/E2E test arm of athena-runtime-verify. It complements the enabled playwright-skill@anthropic-official plugin and gives Athena-specific evidence rules.
Official references:
Detect project setup before adding anything:
playwright.config.*, tests/, e2e/, package.json scripts.@playwright/test and a minimal config/test file that fits the repo.Start or reuse a deterministic app target:
package.json.baseURL in config or pass it via PLAYWRIGHT_BASE_URL.Write tests through user-visible behavior:
await expect(locator).toBeVisible().runtime-verify.Run and iterate:
npx playwright test.npx playwright test --headed, npx playwright test --ui, or npx playwright codegen <url> when exploring selectors.npx playwright test --trace on then inspect with npx playwright show-trace <trace.zip>.npx playwright install or the narrower browser install requested by the repo.Record evidence:
athena-runtime-verify, write a row in runtime-verify.md with scenario, type, command, actual output, and verdict.Feature: use when UI/API behavior is risky or user-visible.Refactor/System: use for browser-facing flows before review; this is part of runtime verification.Bugfix: use when the bug is reproducible in the browser, even though full runtime-verify is usually skipped.Hotfix/Quick: run only the smallest smoke path needed.Read references/runtime-patterns.md when you need concrete command patterns, config snippets, or evidence table examples.