AI TOOLS RADAR
Todos los Skills / TESTDINO-HQ
testdino-hq/playwright-skill

playwright-migration

Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/testdino-hq/playwright-skill --skill playwright-migration

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Playwright Migration Guides

Move to Playwright with confidence — side-by-side command mappings, architecture translations, and incremental migration strategies.

2 guides covering complete migration paths from the most popular testing frameworks.

Guide Index

Migrating fromGuide
Cypressfrom-cypress.md
Selenium / WebDriverfrom-selenium.md

Relacionados por tarea

morluto
Comunidad

rea-ci-tests-audit

Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.

instalaciones
3
GitHub Stars
385,7 mil
Actualizado
25 oct
MIT3 Archivos
Ver detalles →

Motivo de la selección: Pruebas y seguridad

mattpocock
Comunidad

code-review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".

instalaciones
796,7 mil
GitHub Stars
303,4 mil
Actualizado
22 oct
MIT2 Archivos
Ver detalles →

Motivo de la selección: Pruebas y seguridad

affaan-m
Comunidad

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

instalaciones
3
GitHub Stars
286,1 mil
Actualizado
20 oct
MIT1 Archivos
Ver detalles →

Motivo de la selección: Pruebas y seguridad

obra
Comunidad

diagnosing-superpowers

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

instalaciones
500
GitHub Stars
305,1 mil
Actualizado
23 oct
MIT20 Archivos
Ver detalles →

Motivo de la selección: Pruebas y seguridad

del mismo repositorio

Más Skills

Todos los Skills
testdino-hq
Comunidad

playwright-ci

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

instalaciones
2
GitHub Stars
397
Actualizado
12 oct
MIT10 Archivos
Ver detalles →
testdino-hq
Comunidad

playwright-cli

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or have explicit authorization to test.

instalaciones
2
GitHub Stars
397
Actualizado
12 oct
MIT11 Archivos
Ver detalles →
testdino-hq
Comunidad

playwright-core

Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.

instalaciones
2
GitHub Stars
397
Actualizado
12 oct
MIT51 Archivos
Ver detalles →
testdino-hq
Comunidad

playwright-frontend

For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable data-testid attributes (naming convention, uniqueness in lists, stability rules) for React, Vue, Angular, and Svelte. Use when writing or reviewing components, or when an agent needs durable locators.

instalaciones
2
GitHub Stars
397
Actualizado
12 oct
MIT3 Archivos
Ver detalles →