القائمة
Use for committed deterministic browser tests, reusable assertions, and CI-safe regression coverage. Do not use for live browser attach, design-review passes, or exploratory-only browser work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | playwright-e2e |
| description | Use for committed deterministic browser tests, reusable assertions, and CI-safe regression coverage. Do not use for live browser attach, design-review passes, or exploratory-only browser work. |
Use this skill when the task should end with checked-in browser coverage that can run locally and in CI.
/hyperopen/AGENTS.md/hyperopen/docs/BROWSER_TESTING.md/hyperopen/docs/tools.md/hyperopen/docs/FRONTEND.md when UI surfaces changeHYPEROPEN_DEBUGdata-parity-id, data-role, and HYPEROPEN_DEBUG seams before adding new hooks.expect.poll over timing sleeps or a second scenario framework.npm run test:playwright:smoke for the quick local suite and npm run test:playwright:ci for the full committed suite.Use when acting as `acceptance_test_writer` to propose happy-path acceptance and integration coverage from an approved spec or ExecPlan. Do not use to materialize tests directly or to edit production code.
Invoke explicitly with `$bug-flow` for unclear bugs, regressions, or failure investigations that need structured diagnosis, regression tests, the smallest fix, and findings-first review. Do not use for obvious one-line fixes or planned feature work.
Use when acting as `edge_case_test_writer` to propose adversarial, boundary, and invariant coverage that complements acceptance coverage. Do not use to materialize tests or edit production code.
Invoke explicitly with `$feature-flow` for complex features, significant refactors, or multi-file behavior changes that need an ExecPlan, proposed test coverage, RED-phase failing tests, implementation, and review. Do not use for tiny fixes, doc-only work, or purely local cleanup.
Use when acting as `spec_writer` to create or refresh the active ExecPlan, clarify scope, and record acceptance criteria for a multi-agent ticket. Do not use for production-code edits or standalone prose cleanup.
Use Browser MCP for exploratory browser debugging, live-session inspection, parity compare, design review, and selector or flow discovery before converting stable paths into Playwright.