playwright-skill

Automate end-to-end browser tests with Playwright across local dev servers.

1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill playwright-skill-jokken79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/jokken79/YuKyuDATA-app1.0v/tree/main/.agent/skills/playwright-skill
Command: npx skills add https://github.com/jokken79/YuKyuDATA-app1.0v --skill playwright-skill-jokken79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate repetitive, error-prone browser interactions and end-to-end tests by orchestrating Playwright across local dev servers, generating temp scripts in /tmp, and executing them with a visible browser for debugging.

Core Features & Use Cases

  • Auto-detect running dev servers and generate targeted Playwright tests for quick validation.
  • Write test scripts to /tmp (not in project directories) and execute via a universal runner for reproducibility.
  • Validate UI flows, forms, links, login sequences, and responsive behavior across multiple viewports.

Quick Start

Run a simple, concrete task: automatically test your current dev page and capture a screenshot.

Frequently Asked Questions about playwright-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end browser testing with Playwright on a local dev server?

Automate end-to-end browser testing by auto-detecting running local dev servers, generating temporary Playwright test scripts in /tmp, and executing them with a visible browser via a universal run.js wrapper for reproducible validation.

How do I run Playwright tests without adding scripts to my project directory?

Run Playwright tests safely by writing temporary test scripts to the /tmp directory instead of project directories, executing them through a universal runner to maintain a clean project structure while ensuring reproducible automation results.

Can I customize environment headers and parameterize URLs for web automation tasks?

Yes, web automation tasks support parameterized URLs and environment header customization, allowing targeted test execution across local dev servers while injecting necessary headers for accurate browser testing validation.

Does Playwright browser testing work for validating UI flows and responsive viewports?

Playwright browser testing validates UI flows, forms, links, login sequences, and responsive behavior across multiple viewports by orchestrating visible browser execution against local dev servers for comprehensive end-to-end test coverage.

What is the best way to debug browser automation scripts during end-to-end testing?

Debug browser automation scripts effectively by executing generated Playwright tests with a visible browser, allowing real-time observation of UI interactions, form validations, and navigation flows against local development environments.

Why does my Playwright test fail to connect to my local development environment?

Playwright test connection failures may occur if local dev servers are not running or auto-detection fails; ensure the dev server is active and accessible, then use parameterized URLs to target the correct local endpoint for browser testing.