e2e-ui-research

Analyze frontend projects to identify UI E2E testing targets and generate bilingual documentation.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/specvital/infra --skill e2e-ui-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-ui-research
Source: https://github.com/specvital/infra/tree/main/.claude/skills/e2e-ui-research
Command: npx skills add https://github.com/specvital/infra --skill e2e-ui-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to researching and documenting UI end-to-end test targets, enabling teams to generate comprehensive test scenarios before automation begins.

Core Features & Use Cases

  • Guided UI E2E research: methodically explores frontend apps to identify routes, components, and user flows.
  • Brainstorm and document scenarios: creates bilingual test-target documentation for planning and alignment.
  • Playwright MCP integration: leverages actual browser exploration to validate flows and edge cases.
  • Use case: plan tests for a new feature by mapping pages, interactions, and expected outcomes, then produce a structured target doc.

Quick Start

Use this skill to outline E2E test targets for a frontend feature. Start by providing the app URL and key user paths, then run the research workflow to generate test targets.

Frequently Asked Questions about e2e-ui-research

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

FAQPage Schema
How do I identify UI E2E testing targets for a frontend project?

Generate bilingual test-target documentation by methodically exploring frontend apps to identify routes, components, and user flows, creating structured scenarios for planning and team alignment.

How to plan Playwright E2E tests for new frontend features?

Infer URLs, routes, and framework details for E2E test planning by combining codebase analysis with Playwright MCP exploration, using project config files like playwright.config.ts and package.json to produce target documentation.

Do I need a playwright.config.ts file to generate E2E test plans?

Playwright MCP integration is leveraged to validate flows and edge cases during UI E2E research by using actual browser exploration alongside codebase analysis to identify testing targets.

What's the best way to document E2E test scenarios before automation?

Yes, this skill delivers bilingual test-target documentation, creating structured test scenario documents in two languages to facilitate planning and alignment across diverse development teams.

Can I use Playwright MCP to explore and validate user flows for testing?

Yes, the skill combines codebase analysis with Playwright MCP exploration to identify routes, pages, components, and user flows, producing comprehensive test-target documentation for frontend projects.

How does codebase analysis help find E2E testing targets in frontend apps?

Codebase analysis identifies UI E2E testing targets by examining project config files and frontend source code to infer URLs, routes, and framework, mapping routes, pages, components, and user flows across the app.