skills/quality-engineering/quality-engineering-playwright-cli/SKILL.md
Standardizes token-efficient browser automation via playwright-cli. Use for web verification, navigation, and capturing snapshots/logs.
npx skillsauth add hoangnguyen0403/agent-skills-standard quality-engineering-playwright-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
[!IMPORTANT] Tier 0 (Infrastructure): Browser process management, named sessions, network/console logs. Tier 1 (Core Interactions): Clicks, fills, and navigation (
openvsgoto). Tier 2 (Verification): Snapshot-based assertions and auth state persistence.
Triggers: playwright-cli, browser automation, web verify, snapshot, auth-state.json.
| Step | Command | Purpose |
| :--- | :--- | :--- |
| 1 | playwright-cli -s={ID} open <url> | Start named session. (Mandatory -s=). |
| 2 | playwright-cli -s={ID} snapshot --aria | Aria Snapshot: YAML-like view for LLM reasoning (Best for assertions). |
| 3 | playwright-cli -s={ID} console | Check for JS errors/warnings. |
| 4 | playwright-cli -s={ID} screenshot | Visual evidence. Use --mask <ref> for dynamic content. |
| 5 | playwright-cli -s={ID} close | MANDATORY Cleanup. |
snapshot --aria as primary way to "see" page. Filters noise.button[name="Submit"]) over fragile CSS classes.document.body.style.animation = 'none' to freeze animations before capture.-s=. Bare commands collide across concurrent runs.open for first run; goto for mid-session navigation.close session, even on failure.snapshot rather than pixels.state-load for multi-step flows.development
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
development
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
development
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
testing
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.