currents-dev / playwright-best-practices-skill

The skill itself does no work; it is a router. Depending on what you're building or fixing, it loads one of 57 markdown references grouped into eight areas: core mechanics (locators, assertions, fixtures, Page Object Model), debugging and flaky-test diagnosis, testing patterns (accessibility, API, visual regression, security, i18n, canvas/WebGL, Electron, browser extensions), advanced flows (authentication, multi-user, multi-context OAuth popups, clock mocking), four browser-API references, three architecture-decision guides, four framework-specific references (React, Angular, Vue, Next.js), and nine infrastructure/CI-CD references covering GitHub Actions, GitLab, Docker, sharding, and coverage reporting.

This is for anyone writing or maintaining Playwright tests in TypeScript, from a first end-to-end test to a niche case like WebSocket reconnection or RTL layout testing; the router design means the skill stays relevant across that whole range instead of front-loading everything at once. It needs nothing beyond the skill's own files — no account, no API key, no external service.

READ THE FULL ANALYSIS＋

Published by a vendor, but the skill itself doesn't pitch their product. The repository belongs to currents-dev, whose currents.dev product is a Playwright test dashboard; the readme opens with a link to it. The skill's own trigger description and reference-file index make no further mention of currents.dev — what we have is the readme and the table of contents, and neither reads as a pitch for their platform, though we did not read all 57 reference files line by line to confirm the same is true throughout.