e2e-cucumber-playwright
Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags, locators, and assertions. Do not use for Vitest, React Testing Library, backend tests, or generic browser automation outside the E2E suite.
Profile →npx skills add langgenius/dify --skill e2e-cucumber-playwright --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# E2E Cucumber And Playwright `e2e/AGENTS.md` owns the suite architecture, lifecycle, commands, tags, generated-client boundaries, fixtures, and cleanup contracts. Read the nearest feature-scoped `AGENTS.md` when one exists. This skill adds no parallel package policy. ## Topic Routing Read only the bundled reference required by the change: - Locator, assertion, isolation, or waiting decisions: [`references/playwright-best-practices.md`][playwright] - Scenario wording, step granularity, expressions, or tag design: [`references/cucumber-best-practices.md`][cucumber] Check current official Playwright or Cucumber documentation before introducing a framework pattern that local code and references do not already establish. ## Workflow 1. Add E2E coverage only for a critical user journey with a cross-boundary outcome that cheaper owner-level tests do not already prove. 2. Identify the user-visible behavior and its feature owner. Start from real product defaults and actor roles; setup may establish preconditions but must not manufacture the opposite state to make the scenario meaningful. 3. Read the target scenario, matching step definitions, and lifecycle files only when session or shared
- Topic Routing
- Workflow
What does the e2e-cucumber-playwright skill do?
Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags, locators, and assertions. Do not use for Vitest, React Testing Library, backend tests, or generic browser automation outside the E2E suite.
How do I install it?
Run `npx skills add langgenius/dify --skill e2e-cucumber-playwright --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From langgenius/dify, a repository with 151,326 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.