Works with
Packaged from the source skill for Claude, Codex and 4 more.
What this skill does
Set up Playwright testing around an existing web application and its framework, language and CI environment.
Workflow and deliverables
It inspects package configuration, creates browser projects, example tests, folders, package scripts and a GitHub Actions workflow, then verifies the setup. The instructions contain inline configuration examples.
Requirements and limits
Requires package installation, browser binaries and a running application. Generated selectors and CI settings must be adapted to the project; the skill does not ship a tested application fixture.
What is inside the skill
Section headings from the original SKILL.md (about 270 words of instructions). Read the full text in the source repository before installing.
- Steps
- 1. Analyze the Project
- 2. Install Playwright
- 3. Generate playwright.config.ts
- 4. Create Folder Structure
- 5. Generate Example Test
- 6. Generate CI Workflow
- 7. Update .gitignore
- 8. Add npm Scripts
- 9. Verify Setup
- Output
Bundled files
LICENSE
Example prompts
- Initialize TypeScript Playwright tests for our Next.js app with GitHub Actions.
- Add Chromium, Firefox and WebKit projects to an existing Vue test setup.
How to install Pw Init
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Pw Init FAQ
What does the Pw Init skill do?
Set up Playwright testing around an existing web application and its framework, language and CI environment.
Which AI agents can use Pw Init?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Pw Init in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Pw Init and what is the license?
Pw Init is published by Alireza Rezvani under the MIT license. The source is https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/playwright-pro/skills/pw-init. The catalog keeps the original attribution.
What permissions does Pw Init need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.