Skip to main content
skill CX Codex

playwright-pom — Claude Code skill: Playwright Page Object Model

A skill that hands your coding agent two guides on Page Object Model in Playwright: how to structure page objects and when fixtures or helpers fit better.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add testdino-hq/playwright-skill --skill playwright-pom -a claude-code
npx skills add testdino-hq/playwright-skill --skill pom -a claude-code
Open on GitHub

What playwright-pom does

The skill ships two guides. One covers Page Object Model patterns — how to lay out page objects and what belongs inside them. The other gives you a decision framework for picking between POM, fixtures and helpers, so you don't drag a page object into a test that never needed one.

Both live as markdown files: page-object-model.md and pom-vs-fixtures-vs-helpers.md. No scripts, no generators. It's reference material the agent reads when you ask it to restructure Playwright tests, which means it only pays off if your suite actually runs on Playwright — advice about fixtures and page objects is wasted on another runner.

Install works through npx skills add across six platforms, each with its own SKILL.md path. MIT licensed, so forking the guides to match your project's conventions is fair game.

What it helps with

  • split page objects into files across a Playwright suite
  • decide whether a test needs POM or just a fixture
  • move an oversized page object into helpers
  • brief the agent on your test layout before a refactor
  • pick between POM and fixtures when starting a new suite

Example prompts for the agent

  • restructure my Playwright tests using Page Object Model
  • look at this page object and tell me if it should be a fixture instead
  • help me choose between POM and helpers for a new test suite

How to install playwright-pom

1Skills CLI (Vercel)

npx skills add testdino-hq/playwright-skill --skill playwright-pom -a claude-code
npx skills add testdino-hq/playwright-skill --skill pom -a claude-code

2Manually: put the files in place

~/.claude/skills/pom/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pom/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about playwright-pom

How do I install playwright-pom in Claude?

Run npx skills add testdino-hq/playwright-skill --skill playwright-pom -a claude-code. The skill lands at ~/.claude/skills/pom/SKILL.md.

What does playwright-pom do?

It gives the agent two guides: Page Object Model patterns for Playwright, and a framework for choosing between POM, fixtures and helpers.

Which platforms does the skill support?

Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode, each with its own install command and SKILL.md path.

Source text

SKILL.md · MIT
---
name: playwright-pom
description: Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
---

# Playwright Page Object Model

> Structure your test code for maintainability — know when POM helps and when simpler patterns win.

**2 guides** covering Page Object Model implementation and the decision framework for choosing between POM, fixtures, and helpers.

## Guide Index

| Topic | Guide |
|---|---|
| Page Object Model patterns | [page-object-model.md](page-object-model.md) |
| POM vs fixtures vs helpers | [pom-vs-fixtures-vs-helpers.md](pom-vs-fixtures-vs-helpers.md) |

© testdino-hq · MIT · testdino-hq/playwright-skill

Similar skills

Everything for Testing and QA →

From the same set4

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor