E2e Cucumber Playwright

OrganizationPopular

langgenius

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.

Overview

Publisher	langgenius
Repository	`dify`
Skill name	`e2e-cucumber-playwright`
Stars	157.6K
Forks	24.9K
Bundled files	3
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by langgenius on GitHub. Read the source before you install it.

Installation

Install the E2e Cucumber Playwright AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/langgenius/dify.git /tmp/dify
mkdir -p .claude/skills
cp -r /tmp/dify/.agents/skills/e2e-cucumber-playwright .claude/skills/e2e-cucumber-playwright

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable E2e Cucumber Playwright in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads E2e Cucumber Playwright on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so E2e Cucumber Playwright is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Cucumber owns scenario and hook execution and reporting. Playwright provides browser automation, contexts, pages, locators, actions, assertions, request, and tracing APIs; protocol exceptions remain with the package-defined owner. Their timeout domains remain separate, and importing from @playwright/test does not make Playwright Test runner configuration, fixtures, or retries applicable to this suite.

Topic Routing

Read only the bundled reference required by the change:

Locator, assertion, isolation, or waiting decisions: references/playwright-best-practices.md
Scenario wording, step granularity, expressions, World state, hook visibility, or tag design: references/cucumber-best-practices.md

Check current official Playwright or Cucumber documentation before introducing a framework pattern that local code and references do not already establish.

Workflow

Add E2E coverage only for a critical user journey with a cross-boundary outcome that cheaper owner-level tests do not already prove.
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.
Read the target scenario, matching step definitions, and lifecycle files only when session or shared state matters.
Reuse an existing step when wording and behavior match; add one coherent scenario or step when they do not.
Keep browser actions and assertions at the public user boundary; keep setup, seed, polling, and cleanup at their package-defined owners.
For changes, run the narrowest tagged scenario and package checks documented in e2e/AGENTS.md; broaden only for shared hooks, tags, or support changes.

For review requests, lead with reproducible correctness failures, flake sources, or demonstrated architecture drift. Report the behavior verified and any external-runtime, browser, or environment gap.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the E2e Cucumber Playwright AI skill do?

Why use E2e Cucumber Playwright on TypingMind?

Because you install it once and use it with any model. E2e Cucumber Playwright is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install E2e Cucumber Playwright in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use E2e Cucumber Playwright?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with E2e Cucumber Playwright?

As many as you like. As long as a model supports skills, you can use E2e Cucumber Playwright with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the E2e Cucumber Playwright AI skill free?

It is published on GitHub by langgenius. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Documentation Lookup

affaan-m

CommunityPopular

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React,…

Mle Workflow

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML…

Diagnosing Bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

E2e Testing

Patrones de pruebas E2E con Playwright, Page Object Model, configuración, integración CI/CD, gestión de artefactos y estrategias para pruebas inestables.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

E2E Cucumber And Playwright

Topic Routing

Workflow

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now