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.