# Playwright Documentation Bdd

> Legacy Playwright-specific alias for BDD case formatting. Prefer the standalone `test-artifact-export-skill` skill for Gherkin, BDD, and export-ready case rendering, and use this only when Playwright-local conventions must be preserved explicitly.

- Skill: `jovd83/playwright-documentation-bdd` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jovd83/playwright-documentation-bdd`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovd83/playwright-documentation-bdd/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: jovd83 (https://skillmd.com/u/jovd83)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jovd83/playwright-documentation-bdd

---


# Playwright BDD Documentation

Use this skill when the user wants executable-style behavioral documentation in Gherkin form.

## Output Contract

Produce a `.feature`-style artifact with:

- `Feature`
- optional `Background`
- `Scenario` or `Scenario Outline`
- `Examples` when data-driven coverage adds value
- requirement or suite tags when traceability matters

## Writing Rules

- Write behaviors, not UI implementation trivia.
- Keep steps declarative and reusable where possible.
- Use `Scenario Outline` only when the variation is genuinely the same behavior with different data.
- Add negative or resilience scenarios when the requirement carries real risk beyond the happy path.

## Scope

- Stop at documentation unless the user also asked for step definitions or Playwright implementation.
- If the source requirements are incomplete, record assumptions in comments or a short note outside the Gherkin body.