E2E
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
Install
npx skills add NeverSight/learn-skills.dev --skill e2egit clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git /tmp/learn-skills.dev
mkdir -p ~/.claude/skills
cp -r /tmp/learn-skills.dev/data/skills-md/0xbigboss/claude-code/e2e ~/.claude/skills/e2ePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# E2E Testing ## Principles (Always Active) These apply whenever working with e2e tests, test failures, or test flakiness: ### Failure Taxonomy Every e2e failure is exactly one of: **A. Flaky** (test infrastructure issue) - Race conditions, timing-dependent assertions - Stale selectors after UI changes - Missing waits, incorrect wait targets - Network timing, mock setup ordering - Symptom: passes on retry, fails intermittently **B. Outdated** (test no longer matches implementation) - Test asserts old behavior that was intentionally changed - Selectors reference removed/renamed elements - API contract changed, test wasn't updated - Symptom: consistent failure, app works correctly **C. Bug** (implementation doesn't match spec) - Test correctly asserts spec'd behavior, code is wrong - **Only classify as bug when a spec exists to validate against** - If no spec exists, classify as "unverified failure" and report to the user ### Fix Rules by Category **Flaky fixes:** - Replace `waitForTimeout` with auto-waiting locators - Replace brittle CSS selectors with `getByRole`/`getByLabel`/`getByTestId` - Fix race conditions with `expect()` web-first assertions - Fix mock/route setup ordering (before navigation) - **Never add arbitrary delays** - fix the underlying wait - **Never weaken assertions** to make flaky tests pass - **Never add retry loops around assertions** - use the framework's built-in retry **Outdated fixes:**
Details
- Skill name
e2e- Repository
- NeverSight/learn-skills.dev
- Path
data/skills-md/0xbigboss/claude-code/e2e/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the E2E skill do?
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
How do I install the E2E skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add NeverSight/learn-skills.dev --skill e2e. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is E2E popular?
It lives in NeverSight/learn-skills.dev, which has 223 GitHub stars and 42 forks.
Related skills
Council
223NeverSight/learn-skills.dev
Convene the Council of High Intelligence — multi-persona deliberation with historical thinkers for deeper analysis of complex problems.
Megaeth Developer
223NeverSight/learn-skills.dev
End-to-end MegaETH development playbook (Feb 2026). Covers wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync (EIP-7966) for instant receipts, JSON-RPC batching, real-time mini-block subscriptions, storage-aware contract patterns (Solady RedBlackTreeLib), MegaEVM gas model, WebSocket keepalive, bridging from Ethereum, and debugging with mega-evme. Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts.
Openclaw Stock Skill
223NeverSight/learn-skills.dev
使用 data.diemeng.chat 提供的接口查询股票日线、分钟线、财务指标等数据,支持 A 股等市场。
Playwright Best Practices
223NeverSight/learn-skills.dev
Provides Playwright test patterns for resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking. Must use when writing or modifying Playwright tests (.spec.ts, .test.ts files with @playwright/test imports).
Data Driven Testing
223NeverSight/learn-skills.dev
DEPRECATED: Use testing-best-practices instead. This skill has been retired.
Playwright Expert
121theguysudo/ENZO
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.