e2e-ui-execute

Implements Playwright UI E2E tests sequentially with bilingual bug reporting.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/cine-mirror --skill e2e-ui-execute-kubrickcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-ui-execute
Source: https://github.com/kubrickcode/cine-mirror/tree/main/.agents/skills/e2e-ui-execute
Command: npx skills add https://github.com/kubrickcode/cine-mirror --skill e2e-ui-execute-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying UI behavior and then writing Playwright test code for every scenario is slow and error-prone, and bugs discovered mid-testing often derail the whole run. This Skill automates sequential UI E2E test implementation using Playwright MCP, documenting bugs without stopping the workflow. ## Core Features & Use Cases - Sequential Test Execution: Runs each planned test scenario one at a time, manually verifying behavior with Playwright MCP before writing any test code. - Bilingual Bug Reporting: When a bug is found (page load failure, missing elements, console errors), it creates both Korean and English bug reports and continues to the next test instead of stopping. - Config-Aware Code Generation: Reads playwright.config.ts and package.json to place test files in the correct directory and follow the project's naming conventions. - Use Case: After running e2e-ui-research to plan test scenarios, invoke this Skill to verify each scenario in a real browser, generate Playwright test code for passing flows, and produce bug reports for failures. ## Quick Start Run the e2e-ui-execute skill to implement the planned UI E2E tests from docs/e2e-ui/test-targets.md using Playwright MCP.

Frequently Asked Questions about e2e-ui-execute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Playwright E2E tests from planned test scenarios?▼

Run this Skill after generating test scenarios with e2e-ui-research. It reads docs/e2e-ui/test-targets.md, verifies each scenario manually with Playwright MCP, and writes test code only for scenarios that pass verification.

What happens when a bug is found during E2E test execution?▼

The Skill creates bilingual bug reports (bug-report-test-N.ko.md and bug-report-test-N.md) documenting the issue, then continues to the next test instead of stopping. Test code is skipped for scenarios with bugs.

Does this work with existing playwright.config.ts settings?▼

Yes, it reads playwright.config.ts to extract the test directory from testDir or testMatch and the base URL from webServer.url or use.baseURL. Test files are written following the project's existing naming conventions and directory structure.

What prerequisites are needed before running UI E2E test implementation?▼

You must first run e2e-ui-research to generate docs/e2e-ui/test-targets.md containing the planned test scenarios. The project also needs a playwright.config.ts (or .js) file and Playwright MCP access for browser automation.

Why does the Skill run tests sequentially instead of in parallel?▼

Sequential execution ensures each scenario is manually verified with Playwright MCP before code is written, preventing unverified behavior from being codified. It also allows bugs to be documented individually without affecting other tests.