Entry point for any Playwright-shaped question in dean-stack. Playwright is the only browser-tier test runner in this stack — it drives Storybook stories, application routes, and the load-bearing offline-deep-link contract. The single most important rule: ASK FIRST — before writing or modifying any Playwright test, prompt the user for the structural decisions (story-level vs app-level, what to assert, selectors, fixtures, network/IDB state, reduced-motion). The user owns those decisions per case. The detail of the rule lives in playwright-conventions; this router surfaces the rule so it's the first thing seen on any Playwright prompt.

When to invoke

The user types playwright with no further specifier and you need to route them.
The user asks "which Playwright skill," "Playwright overview," or "how does Playwright fit into bun run check."
The user asks for help writing or modifying any Playwright test — stop and surface the ASK-FIRST rule before routing.
A question mixes story-level + app-level + offline (e.g. "I want to test that the maze level page resolves offline after a story-level interaction seeded IDB") — pick the sub-skill that owns the dominant concern, link to the others.
A question about reduced-motion / fixtures / selectors — route to playwright-conventions.

Owns

Entry point that routes Playwright questions to the story-tests, app-tests, PWA-offline, or conventions sub-skill; enforces the ASK-FIRST rule before writing any Playwright test.