Agent skill
cucumber-cypress
Cucumber BDD with Cypress policies. Use when writing Gherkin scenarios with Cypress step definitions. Do NOT use for Playwright-based BDD -- use cucumber-playwright instead. Do NOT use for non-BDD Cypress tests.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/cucumber-cypress
SKILL.md
Cucumber + Cypress Policies
Use @badeball/cypress-cucumber-preprocessor for Cypress + Cucumber.
Project Structure
cypress/
├── e2e/
│ ├── features/*.feature
│ └── step_definitions/*.steps.ts
├── support/
cypress.config.ts
Gherkin Best Practices
Use Scenario Outline for Multiple Cases
Scenario Outline: Login validation
Given I am on the login page
When I enter "<email>" as email
And I enter "<password>" as password
Then I should see "<message>"
Examples:
| email | password | message |
| [email protected] | valid | Welcome |
| [email protected] | wrong | Invalid credentials |
Keep Steps Reusable
Write steps that can be shared across features.
Step Definition Policies
Use data-testid Selectors
// GOOD
cy.get('[data-testid="email-input"]').type(email)
// BAD: Brittle CSS selectors
cy.get('.input-field-xyz').type(email)
Import from Correct Package
import { Given, When, Then } from '@badeball/cypress-cucumber-preprocessor'
Hooks for Setup/Cleanup
import { Before, After } from '@badeball/cypress-cucumber-preprocessor'
Before(() => {
cy.clearCookies()
cy.clearLocalStorage()
})
Tagged Hooks for Specific Scenarios
Before({ tags: '@login' }, () => {
cy.fixture('users').as('users')
})
Commands
npx cypress run
npx cypress run --spec "cypress/e2e/features/login.feature"
npx cypress open # Interactive
Configuration
For setup details, use context7 to query @badeball/cypress-cucumber-preprocessor documentation.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?