e2e-ui-research

Analyzes frontend code and browser exploration to generate bilingual E2E test scenario documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of researching and documenting End-to-End (E2E) UI test scenarios for frontend applications, ensuring comprehensive test coverage.

Core Features & Use Cases

  • Automated Test Planning: Generates detailed E2E test scenarios by analyzing application code and performing actual browser exploration.
  • Bilingual Documentation: Creates test documentation in both English and Korean.
  • Use Case: A QA engineer needs to create a new E2E test suite for a complex web application. This Skill can analyze the application's routes, components, and user flows, then generate a comprehensive set of test scenarios to guide the test development process.

Quick Start

Use the e2e-ui-research skill to research UI E2E test targets for the current project.

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

To generate E2E test scenarios, this Skill analyzes frontend code and performs actual browser exploration via Playwright MCP to identify routes, components, and user flows for prioritized test documentation.

Can I automate UI test documentation for existing web projects?

Yes, you can automate UI test documentation by analyzing project configuration and existing tests, then performing browser exploration to create fresh, comprehensive E2E test scenarios.

Does this tool perform actual browser exploration or just static code analysis?

This tool performs actual browser exploration via Playwright MCP in addition to static code analysis, allowing it to identify real user flows and generate accurate E2E test targets.

What is the best way to research E2E test targets for complex web applications?

The best way to research E2E test targets is to analyze the application's project type, routes, and components, then validate user flows through actual browser exploration to create prioritized scenarios.

Does the generated test documentation support multiple languages?

Yes, the generated test documentation supports multiple languages, specifically producing bilingual test scenario documentation in both English and Korean.

How do I identify which user flows need E2E coverage in my project?

To identify user flows needing E2E coverage, this Skill analyzes your frontend components and routes, then maps actual browser interactions to create prioritized test scenarios.