x-bdd-browser

What problem does it solve?

This Skill removes the confusion and inconsistencies in browser-focused BDD by defining how to author, place, and implement Playwright BDD runners for @browser scenarios across monorepos and frontend-only projects.

Core Features & Use Cases

• Consistent Browser BDD structure: Keeps Gherkin features in the shared features/NN_epic folder while placing Playwright runner code in the correct runner directory.
• TypeScript step definitions that reflect real UI behavior: Enforces When/Then rules using Playwright actions and assertions against visible outcomes.
• Proper use of fixtures and page objects: Separates environment/browser context (fixtures) from stable UI operations (pages) without turning page objects into oracles.

Use case: You need to add a new UI flow and its scenarios to a monorepo where product features are shared, and you want only @browser-tagged scenarios to run via Playwright BDD with TypeScript steps, fixtures, and page objects.

Quick Start

Tell the AI: “How should I structure my new browser BDD feature under features/NN_epic and implement matching Playwright TypeScript steps/fixtures/pages for @browser scenarios?”