Pom
End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/playwright-skill --skill pomAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Test-architecture skill for Playwright page objects, fixtures, and helpers. Use when Codex needs to decide whether to introduce a Page Object Model, how to structure page objects, and how to separate browser state, UI behavior, and stateless utilities cleanly.
SKILL.md
1.9 KB, as published. Nobody here has run it
Playwright POM
Use this skill when the main decision is architectural rather than tactical.
Decision Model
- Use fixtures for setup, teardown, shared state, and authenticated contexts.
- Use page objects to encapsulate repeated or complex UI behavior.
- Use helpers only for stateless utilities such as data generation, formatting, or pure transformations.
- Do not force page objects for every one-off interaction.
Practical Rules
- Reach for a page object when the same UI behavior appears in multiple tests or when the page flow is complex enough to deserve a named abstraction.
- Keep assertions close to the test unless a reusable page-level assertion adds clarity.
- Avoid helpers that accept a
Pageor mutate browser state. - Keep the testing support code organized with the tests it serves.
Read by Need
| Need | Guide |
|---|---|
| Page object design | page-object-model.md |
| POM vs fixture vs helper tradeoffs | pom-vs-fixtures-vs-helpers.md |
| Broader architecture decisions | ../core/test-architecture.md |