Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.
playwright-pro
Security Scan Summary
Status: Safe
Source: Syntic Skills registry
Automated security scan completed with no high-risk patterns detected. Manual review is still required.
About This Skill
Use when creating, fixing, or migrating Playwright tests; end-to-end testing; browser automation; or evaluating test coverage across frameworks.
Downloadable SKILL.md
Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.
--- name: playwright-pro description: Use when creating, fixing, or migrating Playwright tests; end-to-end testing; browser automation; or evaluating test coverage across frameworks. category: Engineering version: 1.0.0 tools: [] --- # Playwright Pro **Tier:** POWERFUL **Domain:** Testing Production-grade Playwright testing toolkit. ## Available Workflows | Task | Workflow | |---|---| | Initialize | Detect framework, generate config, CI pipeline, first smoke test | | Generate tests | From user story, URL, or component spec | | Review tests | Validate quality and flag anti-patterns | | Fix tests | Diagnose and repair failing or flaky tests | | Migrate | Convert from Cypress or Selenium to Playwright | | Coverage | Analyze what's tested vs. missing | | Sync | Integrate with TestRail (read cases, push results) | | Cross-browser | Run on BrowserStack, pull cross-browser reports | | Report | Generate test report in preferred format | ## Quick Start Recommended sequence: 1. Initialize — scaffolds config, CI pipeline, first smoke test 2. Generate — create tests from spec or URL 3. Review — validate quality and flag anti-patterns (always run after generate) 4. Fix — diagnose and repair failing/flaky tests (run when CI turns red) ## Golden Rules 1. `getByRole()` over CSS/XPath — resilient to markup changes 2. Never `waitForTimeout()` — use web-first assertions 3. `expect(locator)` auto-retries; `expect(await locator.textContent())` does not 4. Isolate every test — no shared state 5. `baseURL` in config — zero hardcoded URLs 6. Retries: `2` in CI, `0` locally 7. Traces: `'on-first-retry'` — rich debugging without slowdown 8. Fixtures over globals — use `test.extend()` for shared state 9. One behavior per test — multiple assertions fine 10. Mock external services only — never mock your app ## Locator Priority ``` 1. getByRole() — buttons, links, headings, form elements 2. getByLabel() — form fields with labels 3. getByText() — non-interactive text 4. getByPlaceholder() — inputs with placeholder 5. getByTestId() — when no semantic option exists 6. page.locator() — CSS/XPath as last resort ``` ## What's Included - 55+ test templates (auth, CRUD, checkout, search, forms, dashboard, accessibility) - 3 specialized agents (architect, debugger, migration-planner) - TestRail and BrowserStack integrations - 6 reference docs: golden rules, locators, assertions, fixtures, pitfalls, flaky tests - Migration guides for Cypress and Selenium
Bundle Download
Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.
Install Targets
Syntic App
- 1. Create a dedicated folder for this skill in your local skills library.
- 2. Place SKILL.md into that folder.
- 3. Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1. Save SKILL.md in your local Syntic Code skills directory.
- 2. Keep related files in the same skill folder.
- 3. Run in a safe environment and validate outputs.
Source
https://github.com/alirezarezvani/claude-skills/blob/main/engineering-team/playwright-pro/skills/pw/SKILL.md
Open Source LinkRelated Skills
a11y-audit
Use when auditing WCAG 2.2 Level A/AA accessibility, fixing violations in React, Next.js, Vue, Angular...
Engineeringadversarial-reviewer
Use when reviewing recent code changes or a PR before merge and you want a genuinely critical review, not...
Engineeringagent-designer
Use when architecting multi-agent systems, selecting orchestration patterns, or evaluating agent performance.
Engineeringagent-harness
Use when building bounded agentic loops with verified task execution and state machines.