Agent skill

Quality Engineering Playwright Pom Generation

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture.

MITAuto-check passedTesting & QA

Install Quality Engineering Playwright Pom Generation

skills CLI
$ npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-playwright-pom-generation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard quality-engineering-playwright-pom-generation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/quality-engineering/quality-engineering-playwright-pom-generation .claude/skills/quality-engineering-playwright-pom-generation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quality-engineering-playwright-pom-generation
GitHub stars
572
Token cost
~805 tokens
SKILL.md length
345 words
Files
5 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture.

  • Works in 5 steps: Read the scenario block and the screen's… → Map each plan step to an existing or new… → Write locators per the ladder; list… → …
  • A web scenario needs a page object that does not exist yet
  • SKILL.md covers Priority: P1 (HIGH), Input, Layout and Locator Rules, plus 4 more sections
  • Calls npx

What it does

Quality Engineering Playwright Pom Generation is an agent skill from HoangNguyen0403/agent-skills-standard. Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture. Use when a web scenario needs a page object that does not exist yet, or when locators drift and the page object must be rebuilt.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `evals/evals.json`, `references/fixture-wiring.md` and `references/page-object-template.md`).

It sits in Testing & QA, covering Browser testing and Test generation. It works with Playwright. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.

When your agent uses it

  • A web scenario needs a page object that does not exist yet
  • Locators drift and the page object must be rebuilt

Example prompts

  • “Use the quality-engineering-playwright-pom-generation skill to generate Playwright page objects from an executable test plan, one class per screen…”
  • “/quality-engineering-playwright-pom-generation”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read the scenario block and the screen's existing page object, if any; extend rather than duplicate.
  2. Map each plan step to an existing or new action method; map each Expected to a state getter.
  3. Write locators per the ladder; list unresolved elements under Selector Gaps in the output.
  4. Register the page object in the pages fixture.
  5. Run npx tsc --noEmit -p tests (or the repo's typecheck) and the seed spec once.

What it can do on your machine

Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quality Engineering Playwright Pom Generation loads about 805 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 345 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~805
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 345 words, ~805 tokens.

Download SKILL.mdSave it as .claude/skills/quality-engineering-playwright-pom-generation/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
quality-engineering-playwright-pom-generation
description
Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture. Use when a web scenario needs a page object that does not exist yet, or when locators drift and the page object must be rebuilt.

Quality Engineering: Playwright Page Object Generation

Priority: P1 (HIGH)

Input

A web-lane scenario block from docs/srs/test-plan-[slug].md (Steps, Expected, @AC-n) plus the resolved SELECTOR_GAPS for that screen. Generate from the plan, never from a live DOM crawl alone: the plan says which elements matter.

Layout

  • One file per screen: tests/pages/<screen>.page.ts, class <Screen>Page (e.g. CheckoutPage).
  • One locator getter per element the plan touches, named after the element (submitButton, emailInput).
  • One action method per plan step verb (fillShipping(data), submit()); actions return void or the next page object.
  • A pages fixture in tests/fixtures.ts exposes every page object; specs import test from there, never from @playwright/test directly.

Locator Rules

Follow the web ladder in quality-engineering-selector-stability: getByRole / getByLabel first, then getByTestId using the <screen>-<element>-<role> id, then attribute CSS. Never XPath, nth, text on translated strings, or generated class names. When the element has no stable locator, do not invent one: record it as a selector gap for specialist-testid-inserter.

No Assertions in Page Objects

Page objects expose state (orderId(), isVisible()), specs assert on it. An expect inside a page object hides the assertion from the scenario and breaks reuse across positive and negative cases.

Workflow

  1. Read the scenario block and the screen's existing page object, if any; extend rather than duplicate.
  2. Map each plan step to an existing or new action method; map each Expected to a state getter.
  3. Write locators per the ladder; list unresolved elements under Selector Gaps in the output.
  4. Register the page object in the pages fixture.
  5. Run npx tsc --noEmit -p tests (or the repo's typecheck) and the seed spec once.

Anti-Patterns

  • No assertions in page objects: expect belongs in the spec.
  • No DOM-crawl page objects: a class with forty getters nobody's scenario uses is noise, not coverage.
  • No duplicate page object: search tests/pages/ before creating; extend the existing class.
  • No raw page in specs: every interaction goes through a page object or the seed.
  • No renamed test ids: ids are a public contract; a rename is a selector gap, not a refactor.

References

© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/quality-engineering/quality-engineering-playwright-pom-generation of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/fixture-wiring.md
  • references/page-object-template.md
  • references/playwright-mcp-authoring.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Quality Engineering Playwright Pom Generation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quality Engineering Playwright Pom Generation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Engineering Playwright Pom Generation this skillHoangNguyen0403/agent-skills-standard572—~805Automated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
Chamilo Feature Test Authorchamilo/chamilo-lms1k—~3.6kAutomated safety check: PassGPL-3.0
Dev Webtest Planclassmethod/tsumiki974—~4.2kAutomated safety check: PassMIT
Testing Orcaqcin12211/orca-q224—~1.6kAutomated safety check: PassMIT
Replica TestJakeschincariol/replica-skill1.4k—~819Automated safety check: PassMIT

Similar skills

  • Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Chamilo Feature Test Author

    chamilo/chamilo-lms

    Turns a plain-language Chamilo feature description into a Playwright and Gherkin test suite confirmed against the live app, not just the source code.

    1k GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Dev Webtest Plan

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-webtest-plan", "Webテスト計画を生成", "テスト計画を作成", "webtest plan", "E2Eテスト計画", "画面テスト計画", "generate webtest plan", "create test plan from requirements"…

    974 GitHub stars~4.2k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Testing Orcaq

    cin12211/orca-q

    OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.

    224 GitHub stars~1.6k tokensUpdated 19 days ago
    Testing & QAAuto-check passed
  • Replica Test

    Jakeschincariol/replica-skill

    Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser…

    1.4k GitHub stars~819 tokensUpdated 8 days ago
    Testing & QAAuto-check passed
  • Playwright Stealth Verify

    liarjsdev/liarjs-skills

    Check whether a Playwright, Puppeteer, Selenium or CDP-driven browser presents a coherent fingerprint, using liarjs as a library against a Page you already have - navigator.webdriver, HeadlessChrome…

    4 GitHub starsUsed in 1 repo~1.3k tokens
    Testing & QAAuto-check: notes

More from HoangNguyen0403/agent-skills-standard

All 211 skills in this repo
  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • draw.io Architecture Diagramming

    HoangNguyen0403/agent-skills-standard

    Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Android Navigation 3 Guide

    HoangNguyen0403/agent-skills-standard

    Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.

    572 GitHub stars~687 tokensUpdated yesterday
    Auto-check passed
  • Angular HttpClient Standards

    HoangNguyen0403/agent-skills-standard

    Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.

    572 GitHub stars~652 tokensUpdated yesterday
    Auto-check passed
  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

    Angular CLI usage, code generation, build configuration, and bundle optimization.

    572 GitHub stars~743 tokensUpdated yesterday
    Auto-check passed
  • Common Code Review

    HoangNguyen0403/agent-skills-standard

    Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.

    572 GitHub stars~772 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Quality Engineering Playwright Pom Generation

What does Quality Engineering Playwright Pom Generation do?

Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture. Quality Engineering Playwright Pom Generation is an agent skill from HoangNguyen0403/agent-skills-standard. Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture.

When should I use Quality Engineering Playwright Pom Generation?

Quality Engineering Playwright Pom Generation fits situations like: A web scenario needs a page object that does not exist yet; locators drift and the page object must be rebuilt.

How do I install Quality Engineering Playwright Pom Generation in Claude Code?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-playwright-pom-generation -a claude-code`. Or copy the skill folder (skills/quality-engineering/quality-engineering-playwright-pom-generation in HoangNguyen0403/agent-skills-standard) into .claude/skills/quality-engineering-playwright-pom-generation in your project. Claude Code loads it when a task matches its description.

How do I install Quality Engineering Playwright Pom Generation in Codex?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-playwright-pom-generation -a codex`. Or copy the skill folder (skills/quality-engineering/quality-engineering-playwright-pom-generation in HoangNguyen0403/agent-skills-standard) into .agents/skills/quality-engineering-playwright-pom-generation in your project. Codex loads it when a task matches its description.

Can I use Quality Engineering Playwright Pom Generation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-playwright-pom-generation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-engineering-playwright-pom-generation, .gemini/skills/quality-engineering-playwright-pom-generation, .github/skills/quality-engineering-playwright-pom-generation and .opencode/skills/quality-engineering-playwright-pom-generation in your project.

What does Quality Engineering Playwright Pom Generation need to run?

Going by SKILL.md and its folder, Quality Engineering Playwright Pom Generation needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Quality Engineering Playwright Pom Generation access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Quality Engineering Playwright Pom Generation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quality Engineering Playwright Pom Generation use?

Quality Engineering Playwright Pom Generation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quality Engineering Playwright Pom Generation use?

About 805 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Quality Engineering Playwright Pom Generation?

Skills that share tags, products or a category with Quality Engineering Playwright Pom Generation: Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars), Chamilo Feature Test Author (chamilo/chamilo-lms, 1k stars), Dev Webtest Plan (classmethod/tsumiki, 974 stars) and Testing Orcaq (cin12211/orca-q, 224 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Engineering Playwright Pom Generation?

HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.

Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.