e2e-ui-execute

Execute UI E2E tests sequentially with Playwright MCP and report bugs bilingually.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/specvital --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/specvital/tree/main/.claude/skills/e2e-ui-execute
Command: npx skills add https://github.com/kubrickcode/specvital --skill e2e-ui-execute-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the sequential implementation of UI End-to-End tests, ensuring thorough testing and bug detection without manual intervention.

Core Features & Use Cases

  • Sequential Test Execution: Runs UI E2E tests one by one, following a defined order.
  • Automated Bug Reporting: Detects and documents bugs with bilingual reports (Korean/English) upon discovery.
  • Code Generation: Writes Playwright test code for scenarios that pass verification.
  • Use Case: After researching potential test scenarios for a web application, use this Skill to systematically implement and verify each test case, generating the necessary Playwright code and documenting any issues found along the way.

Quick Start

Use the e2e-ui-execute skill to implement the planned test scenarios for the user authentication flow.

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 sequentially?

To implement Playwright E2E tests sequentially, you can execute UI test scenarios one by one, stopping immediately upon bug discovery to perform manual verification and generate bilingual bug reports.

What is sequential UI test execution with bug detection?

Sequential UI test execution with bug detection is an automated process that runs E2E test scenarios individually, performs manual verification, and halts execution to document bugs when they are discovered.

How does Playwright MCP generate bug reports during E2E testing?

Playwright MCP generates bug reports during E2E testing by detecting issues during sequential test execution and automatically creating bilingual documentation in Korean and English upon bug discovery.

Do I need playwright.config.ts and package.json to automate UI test implementation?

Yes, you need playwright.config.ts and package.json to automate UI test implementation, as the process reads these project configurations to determine test directories and frameworks before executing scenarios.

Can Playwright MCP write test code for passing E2E scenarios?

Yes, Playwright MCP can write test code for passing E2E scenarios by executing tests sequentially, performing manual verification, and automatically generating Playwright test code for successful scenarios.

What is the best way to automate E2E testing and document bugs?

The best way to automate E2E testing and document bugs is using sequential test execution that halts on failure, performs manual verification, and generates bilingual bug reports for discovered issues.