e2e

Generate end-to-end test plans and Playwright spec files for web applications.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MoeGolibrary/moego-ai-plugin --skill e2e-moegolibrary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/MoeGolibrary/moego-ai-plugin/tree/main/skills/e2e
Command: npx skills add https://github.com/MoeGolibrary/moego-ai-plugin --skill e2e-moegolibrary

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill streamlines the creation of end-to-end (E2E) automated tests by providing both planning and code generation capabilities, ensuring comprehensive UI test coverage for your applications.

Core Features & Use Cases

  • E2E Test Planning: Generates structured test plans based on feature requirements, code changes, or existing pages.
  • E2E Test Code Generation: Writes Playwright-based .spec.ts files and Page Objects, adhering to best practices.
  • Use Case: When developing a new user flow, use this skill to automatically generate a test plan outlining necessary scenarios and then generate the corresponding Playwright test code to validate the implementation.

Quick Start

Use the e2e skill to plan and generate E2E tests for the new user registration feature.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I generate Playwright test code for new web application features?

To generate Playwright test code, provide a feature description or codebase for analysis. The skill automatically produces structured .spec.ts files and Page Objects, ensuring your UI testing adheres to established best practices.

What is the best way to plan E2E testing scenarios for a web UI?

The best way to plan E2E testing scenarios is to input your feature requirements or code changes. The skill generates a structured E2E test plan outlining necessary user interactions and test data strategies before writing code.

Can I automate test planning and spec file generation from existing code?

Yes, you can automate test planning and spec file generation by analyzing existing code. The skill reads your web application code to automatically create test scenarios, Page Objects, and Playwright spec files.

Does the generated Playwright test code include page objects and data strategies?

Yes, the generated Playwright test code includes page objects and data strategies. It automates the creation of spec files while implementing data strategies and enforcing UI interaction testing best practices.

When do I need to generate E2E test plans versus writing test code directly?

You need to generate E2E test plans when outlining necessary scenarios for new user flows. Once the plan validates your testing coverage requirements, you can proceed to generate the corresponding Playwright test code.

What are the limitations of automating UI interaction testing with generated specs?

A limitation of automating UI interaction testing is that generated specs depend heavily on accurate feature descriptions or code analysis. Complex, highly dynamic web UI interactions may require manual refinement of the generated Playwright spec files.