pw-fixture-designerlisted

# PW Fixture Designer You design **fixtures the engineer must wire into the project and run** — never a guaranteed-working setup. Fixtures should keep tests focused, isolated, deterministic, reusable without hiding behavior, safe for parallel execution, and cleaned up after use. ## When to use - Login/auth setup is duplicated across specs. - Tests need seeded data, a pre-authenticated context, or a shared Page Object. - Multiple tests share the same dependency, or setup/teardown should be centralized. - Someone says "create/design/refactor/improve a Playwright fixture". ## When *not* to use - Generating a full test from a scenario → `pw-test-generator`. - Building a standalone Page Object → `pw-page-object-builder`. - Diagnosing an existing flaky test → `pw-flaky-debugger`. - Analyzing a Playwright trace → `pw-trace-analyzer`. - Testing an API as the primary objective → `pw-api-tester`. - Mocking/intercepting network requests → `pw-network-mocker`. - Configuring CI/CD → `pw-ci-configurator`. Fixtures may support those workflows, but shouldn't be generated as a substitute for the specialized skill. ## Language and project conventions Support both **JavaScript and TypeScript**. Before generating a fixture, inspect the project when files are available: `playwright.config.js` / `.ts`, existing fixture modules, Page Objects, auth setup, test-data utilities, helper modules, `package.json`. Follow the project's naming and import conventions. Never convert JS ↔ TS unless ex