pom

A set of standards for Page Object Model test code, a way to represent web pages and their controls as code. It also defines how automated test steps and helper methods should be structured.

In plain words
What is it for?
Use it when creating or reviewing browser-test page objects, selectors, Gherkin step definitions, and reusable test helpers.
Why use it?
It removes guesswork about where page objects, selectors, and test steps belong. Consistent names and initialization make the test code easier to review and maintain.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/m3au/playwright-bdd-cursor-template/pom
Clone the repo
git clone --depth 1 https://github.com/m3au/playwright-bdd-cursor-template

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 937 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00937
Opus 5 $0.00000 $0.00468
Sonnet 5 $0.00000 $0.00187
Haiku 4.5 $0.00000 $0.00094

Measured 2d ago against content hash 609681d4e624, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pom scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/pom.mdc · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Page Object Model Standards

Structure

  • Use @Fixture decorator with PascalCase name matching class name (e.g., @Fixture('CableConfiguratorPage'))
  • Export class with descriptive name (e.g., CableConfiguratorPage)
  • Constructor receives Page as protected page: Page or private page: Page
  • Organize POMs into pages/ (full pages) or components/ (reusable components) subdirectories
  • All locator selectors must be initialized in the constructor - no inline locator creation in methods
  • Declare all locator properties at the top of the class (before constructor)
  • Use descriptive locator names ending with Locator (e.g., cableBeginningButton, popupLocator)
  • Child locators can be derived inline when needed (e.g., parentLocator.locator('.child')) but parent locators must be defined at top

Step Definitions

  • Use @Given, @When, @Then decorators from @world for step definitions that match Gherkin scenarios
  • Step text must match Gherkin scenarios exactly
  • All step methods must be async
  • Step methods can optionally receive fixtures parameter: async stepMethod(_fixtures?: PageFixtures)

Internal Helper Methods

  • Use @Step decorator for internal helper methods that should appear in Playwright test reports
  • All methods with @Step decorator must start with "i" following BDD naming convention:
    • iSee... for visibility checks
    • iClick... for click actions
    • iSelect... for selection actions
    • iNavigate... for navigation actions
  • Examples: iSeeTheCableSelectorPopup(), iClickCableBeginning(), iSelectRandomCableType()
  • Use Playwright assertions and waiting patterns - see playwright.mdc for guidance

Imports

  • Import everything from @world: import { Fixture, Given, Then, When, Step, expect, type Page, type Locator } from '@world'
  • Import components: import { ComponentName } from '@components/component-name'
  • Import pages: import { PageName } from '@pages/page-name'
  • Import data: import { getEnvironment } from '@data/config'
  • Import utils: import { getRandomIndex, isValidTextItem } from '@utils'
  • N: use relative imports - A: use path aliases

Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 69 lines · 0 tokens per session scan A 609681d4e624

Subscribe to this mod's changes

pom is a cursor rule published in the GitHub repository m3au/playwright-bdd-cursor-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 937 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.