Standardize browser-focused BDD authoring and execution with Playwright and TypeScript steps.
npx skills add https://github.com/pure-golang/level85 --skill x-bdd-browser
Please help me install this Agent Skill. Skill: x-bdd-browser Source: https://github.com/pure-golang/level85/tree/main/.agents/skills/x-bdd-browser Command: npx skills add https://github.com/pure-golang/level85 --skill x-bdd-browser
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.
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.
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?”
High-intent search queries and answers about installing and using this skill.
To structure Playwright BDD in a monorepo, keep Gherkin feature files in a shared features/NN_epic directory while placing the runner code and TypeScript step definitions in a separate runner directory. This enforces separation between shared product features and runner-owned test code.
The best way to run specific browser UI scenarios is to tag targeted Gherkin features with @browser and filter execution by that tag. This approach ensures only scenarios intended for Playwright automation are executed via the browser BDD runner.
Organize fixtures and page objects by separating browser context into fixtures, while placing stable UI operations into page objects. Avoid turning page objects into oracles by keeping them focused on UI interactions rather than asserting complex business logic.
Playwright BDD does not require API mocks as the default execution path for frontend testing. It enforces UI-visible assertions using Playwright actions to validate real user outcomes directly against the interface without relying on mocked API responses.
Yes, you can generate Playwright tests from Gherkin feature files using the playwright-bdd framework with TypeScript. This process converts your feature files located in the features/NN_epic directory into executable Playwright test scripts.
You should not use API mocks as the default execution path when writing Playwright BDD browser tests. The approach requires enforcing UI-visible assertions to validate actual outcomes, ensuring tests reflect real user behavior rather than bypassing the interface.
fahchenGuide interactive BDD discovery sessions and generate Gherkin .feature files.
HsnSaboorAutomate local web application testing with Playwright scripts.
michaelayoadeScaffold Playwright end-to-end tests with page objects and fixtures.
ssiumhaGenerate Gherkin .feature files from software requirements for BDD workflows.
