playwright-skill

You can automate browser tasks by describing your testing scenario, which triggers auto-detection of your localhost dev server, generates a Playwright script in /tmp, and executes it via a universal wrapper to perform cross-viewport tests and checks.

By default, this Playwright automation executes with a visible browser rather than headless mode, ensuring easier debugging and visual validation during local development and QA testing scenarios.

You can inject context headers by parameterizing URLs and environment headers via environment variables, leveraging helper modules to handle header injection and context creation dynamically for traceability.

Yes, Playwright installation is required to use this automation skill, as it generates scripts in /tmp and executes them through a wrapper without bundling the framework itself.

The best way to keep generated web testing scripts separate is to write them to the /tmp directory and run them via a universal executor, ensuring your project files and directories remain clean.

Yes, you can parameterize URLs and environment headers to support dynamic targets and traceability in cross-viewport web testing, utilizing helper modules to manage server detection and context creation.