10x-e2e

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

Updated May 20, 2026
One-click install
npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-e2e-zawilecxd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-e2e
Source: https://github.com/ZawilecxD/trAInR/tree/main/.cursor/skills/10x-e2e
Command: npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-e2e-zawilecxd

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, ensuring each Playwright test actually protects a named risk and fails when that risk materializes. ## Core Features & Use Cases - Risk-driven test generation: Picks browser-level risks from a test plan, maps the user flow via the accessibility tree, and generates one reviewed test per risk using a seed exemplar and E2E quality rules. - Five anti-pattern review: Checks every generated test for hallucinated assertions, brittle selectors, shared state, wait-for-time, and missing cleanup, then re-prompts by name. - Deliberate-break verification: Confirms each test goes red when the protected behavior is broken, proving the assertion is not decorative. - Use Case: After building a flashcard save feature, run the Skill on the plan's E2E phase to produce a Playwright test proving card data survives a full page reload, verified by temporarily breaking the save logic. ## Quick Start Run /10x-e2e with your change-id, for example "/10x-e2e 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?

Run /10x-e2e with a change-id or plan path, and it picks each browser-level risk, maps the flow using the accessibility tree, and generates one test per risk from a seed exemplar. Each test is reviewed against five anti-patterns and verified with a deliberate-break check.

When should I use E2E tests instead of unit tests?

Use E2E when a risk crosses several system boundaries like 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 to /10x-tdd or /10x-implement.

Does this work with Cypress or Selenium instead of Playwright?

The shipped seed, rules, and prompt template are tuned for Playwright, and the browser-driven path assumes a Playwright CLI or MCP server. On Cypress, WebdriverIO, or Selenium you must encode your tool's idioms into your own seed and rules files.

Why do agent-generated E2E tests become flaky?

Flakiness comes from five anti-patterns: hallucinated assertions, brittle CSS selectors, shared state between tests, waitForTimeout instead of waiting for state, and missing cleanup. The Skill reviews every generated test against these and re-prompts by naming the specific anti-pattern.

Can I run it if the feature is not built yet?

No. E2E drives a running app, so the feature under test must already exist. If it is missing, the Skill stops and redirects you to /10x-implement or /10x-tdd to build it first, then you return for the E2E layer.