10x-e2e

Generates and verifies risk-driven Playwright E2E tests against a running application.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-e2e-michaail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-e2e
Source: https://github.com/michaail/hybrid-logs-analyzer/tree/main/.cursor/skills/10x-e2e
Command: npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-e2e-michaail

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent-generated E2E tests often pass today but break on the first refactor or fail to catch real regressions. This Skill drives an approved plan's browser-level phases one risk at a time, producing Playwright tests that are reviewed against known anti-patterns and verified to actually fail when the protected risk materializes. ## Core Features & Use Cases - Risk-driven test generation: Picks browser-level risks from a test plan, maps the user flow against the running app via accessibility snapshots, and generates one focused Playwright spec per risk. - Quality levers and review: Bootstraps a seed test and E2E rules file, then reviews every generated test against five agent anti-patterns (hallucinated assertion, brittle selector, shared state, wait-for-time, no cleanup). - Deliberate-break verification: Confirms each test goes red when the protected behavior is broken, then reverts the break before committing. - Use Case: A team has an approved implementation plan with phases touching auth, routing, API, and database. Run this Skill to add one hardened E2E test per cross-boundary risk, with per-phase commits and progress tracked in the plan. ## Quick Start Run /10x-e2e with a change-id like "save-session phase 6" to drive that plan's browser-level E2E phases against the running app.

Frequently Asked Questions about 10x-e2e

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

FAQPage Schema
How do I generate Playwright E2E tests from a test plan?

Provide a change-id or plan path, and the Skill picks each browser-level risk, maps the flow using accessibility snapshots of the running app, and generates one spec per risk modeled on a seed test. Each test is reviewed and verified before the phase commits.

What makes an AI-generated E2E test reliable?

Reliable tests use role-based locators like getByRole, run independently with their own setup and cleanup, wait for state instead of time, and assert a business outcome tied to a named risk. The Skill enforces these through a seed test, rules file, and a five anti-pattern review.

When should I use E2E tests instead of unit tests?

Use E2E when a risk crosses several system boundaries such as auth, routing, API, and database, or exists only in the rendered UI. Pure functions, endpoint contracts, and business logic are better covered by unit or integration tests, and this Skill redirects those phases accordingly.

Does this work if the feature is not built yet?

No. E2E tests drive a running application, so the feature under test must already exist. If it is missing, the Skill stops and redirects you to build the feature first with an implementation or TDD workflow.

Can I use this with Cypress or Selenium instead of Playwright?

The shipped seed, rules, and prompt template are tuned for Playwright, but the principles transfer. You encode your tool's locator, waiting, and isolation idioms into your own seed and rules variants and drive its own runner.

Why does the Skill deliberately break the app during verification?

The deliberate-break check temporarily inverts the behavior a test protects to confirm the test actually goes red. A test that stays green after the break protects nothing; the break is reverted immediately and never committed.