10x-e2e

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

Updated May 24, 2026
One-click install
npx skills add https://github.com/DevMachaj/Projekt-certyfikacyjny --skill 10x-e2e-devmachaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-e2e
Source: https://github.com/DevMachaj/Projekt-certyfikacyjny/tree/main/.claude/skills/10x-e2e
Command: npx skills add https://github.com/DevMachaj/Projekt-certyfikacyjny --skill 10x-e2e-devmachaj

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 technical plan's browser-level phases one risk at a time, ensuring each Playwright test actually protects a named risk from the test plan rather than chasing coverage. ## Core Features & Use Cases - Risk-driven test generation: Picks browser-level risks from the plan and test-plan.md, maps the user flow against the running app, 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 feature with /10x-implement, run /10x-e2e to add a Playwright test proving that flashcard data survives a full page reload across auth, routing, API, and database boundaries. ## Quick Start Run /10x-e2e with a change-id like "/10x-e2e save-session phase 6" to drive that plan's browser-level E2E phases one risk at a time.

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. It reads the plan's Progress section, picks each browser-level risk, maps the flow against the running app, and generates one reviewed test per risk following the seed test and E2E rules.

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 via /10x-tdd.

Does this skill set up Playwright from scratch?

No. It assumes Playwright is already installed with a config, a way to run a single spec, and an auth pattern like storageState. If no Playwright config or spec files exist, it stops and tells you to install Playwright first.

Why do agent-generated Playwright tests become flaky?

Common causes are brittle CSS selectors, waitForTimeout instead of state-based waits, shared state between tests, and missing cleanup. This skill reviews every generated test against these five anti-patterns and re-prompts by name to fix them.

Can I run a single E2E test without a full plan?

Yes. Running /10x-e2e with a risk-id or no argument triggers standalone mode, which reads test-plan.md, picks the top browser-level risk, and produces one reviewed, break-verified test without phase tracking or commit rituals.

What happens if the feature under test is not built yet?

The skill stops and redirects you to /10x-implement or /10x-tdd. E2E tests drive a running application, so the implementation must exist before the browser can exercise it.