e2e-ui-research

Researches frontend apps via Playwright browser exploration and generates bilingual E2E test scenario documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning UI end-to-end test coverage requires understanding both the codebase and the actual runtime behavior of a frontend app, which is time-consuming to do manually and often misses real user flows. ## Core Features & Use Cases - Browser-Based Exploration: Uses Playwright MCP to navigate pages, capture DOM snapshots, and simulate user flows like login, CRUD operations, and form validation. - Codebase Analysis: Reads playwright.config.ts and package.json to detect framework, routes, and existing test coverage, avoiding duplicate scenarios. - Bilingual Documentation: Generates fresh Korean and English test target documents (docs/e2e-ui/test-targets.ko.md and .md) with prioritized scenarios. - Use Case: Point it at a running Next.js app with Playwright configured, and it produces a prioritized list of Critical/High/Medium E2E test scenarios marking which are new versus already covered. ## Quick Start Run the e2e-ui-research skill against my running frontend app to explore it with Playwright and generate a prioritized E2E test plan in English and Korean.

Frequently Asked Questions about e2e-ui-research

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

FAQPage Schema
How do I generate E2E test scenarios for a frontend app?▼

Run this skill with your frontend server and Playwright MCP server running. It reads playwright.config.ts for the base URL, explores pages in a real browser, analyzes routes and components, then writes prioritized test scenarios to docs/e2e-ui/test-targets.md and test-targets.ko.md.

How to plan Playwright E2E test coverage without duplicating existing tests?▼

The skill reads testDir or testMatch from playwright.config.ts to locate existing spec files, extracts all describe/test case names, and marks each new scenario as new, already implemented, or partially covered.

Does this work with frameworks other than Next.js or React?▼

Yes. Framework detection reads package.json dependencies and supports Next.js, React, Vue, Svelte, and Angular, adapting route discovery patterns to the detected project structure.

What happens if bugs are found during browser exploration?▼

Bugs are intentionally not reported during research. Scenarios are written for how features should work normally, so broken behavior is surfaced later during the actual E2E test execution phase.

What are the prerequisites for running UI E2E test research?▼

The frontend dev server must already be running and the Playwright MCP server must be available. The base URL and port are extracted from playwright.config.ts rather than hardcoded.