setup-playwright

Automate Playwright end-to-end testing setup with TypeScript configuration and example tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kirillshilin/instructions --skill setup-playwright-kirillshilin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-playwright
Source: https://github.com/kirillshilin/instructions/tree/main/obsolete/claude/skills/setup-playwright
Command: npx skills add https://github.com/kirillshilin/instructions --skill setup-playwright-kirillshilin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing setup can be time-consuming and error-prone for teams adopting Playwright. This skill provides an official bootstrap workflow to install Playwright in a project, set up TypeScript, create the recommended folder structure, base fixtures, and a working example test to get started quickly.

Core Features & Use Cases

  • Install Playwright with the official initializer in the project root and generate a working example test.
  • Configure a standard project structure including tests/, fixtures, and a base page object to enable scalable tests.
  • Integrate a CI workflow by including GitHub Actions and recommended config and ensure tests run reliably in CI.

Quick Start

Run the official Playwright initialiser in the project root and verify the generated example test to bootstrap an E2E test suite.

Frequently Asked Questions about setup-playwright

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

FAQPage Schema
How do I bootstrap Playwright e2e testing in a TypeScript project?

Bootstrapping Playwright e2e testing involves running the official initializer to install dependencies, generate a TypeScript configuration file, and create a working example test. This establishes a scalable folder structure with base fixtures and page objects to start automating browser workflows immediately.

What is the recommended folder structure for Playwright tests?

The recommended Playwright folder structure includes a dedicated tests directory, base fixtures for shared logic, and a base page object for scalable interactions. This layout separates test logic from page navigation, ensuring maintainable end-to-end test suites as the project grows.

How do I configure Playwright for CI workflows?

Configuring Playwright for CI workflows involves adding a GitHub Actions configuration file to the repository. This ensures end-to-end tests run reliably in continuous integration by executing the generated test scaffolding and applying environment variable guidance.

Can I use this Playwright setup to migrate from a minimal test configuration?

Yes, this Playwright setup supports migrating from a minimal test configuration. It applies the official initializer to generate a standard project structure, overwriting minimal setups with ready-to-run test scaffolding, TypeScript settings, and base fixtures.

Do I need environment variables for Playwright test scaffolding?

Environment variables are recommended for Playwright test scaffolding to manage configuration across different stages. The setup provides guidance on defining variables for CI workflows and base fixtures, ensuring tests execute consistently across local and automated environments.