playwright-explore-website

Explore website workflows via Playwright and generate test cases.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/rodoHasArrived/Meridian-main --skill playwright-explore-website-rodohasarrived
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-explore-website
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/plugins/frontend-web-dev/skills/playwright-explore-website
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill playwright-explore-website-rodohasarrived

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly understand a website’s key behaviors by performing structured browser exploration, so you can document flows and derive actionable Playwright test cases instead of guessing what to test.

Core Features & Use Cases

  • Website exploration for core user flows: Navigate to a provided URL and interact with 3–5 core features.
  • UI documentation with locators: Capture which UI elements were used (and their locators) along with what outcome was expected.
  • Test case generation: Produce a concise summary of findings and propose/generate test cases based on the observed behavior.

Quick Start

Provide the target website URL and ask the assistant to explore it, document 3–5 core user flows with locators, and generate Playwright test cases from the results.

Frequently Asked Questions about playwright-explore-website

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Playwright test cases by exploring a website?

Playwright test case generation requires interactively exploring a provided URL via Playwright MCP, logging UI locators and expected outcomes for 3 to 5 core features, and proposing test cases from the discovered interactions.

How do I document UI locators for website automation testing?

Documenting UI locators involves interactively navigating website workflows via Playwright, systematically logging the specific UI elements used and their locators, and capturing the expected outcome for each interaction.

What is website flow discovery for QA and testing?

Website flow discovery for QA involves interactively exploring pages via Playwright to identify 3 to 5 core user functionalities, logging UI locators and expected outcomes, and deriving actionable test cases from the observed behavior.

Do I need a Playwright MCP server to explore website user flows?

Yes, a Playwright MCP server is required to supply the target website URL and facilitate the interactive browser exploration needed to document UI locators and generate test cases.

Can I capture expected outcomes for 3 to 5 core website features automatically?

Yes, the tool interactively explores a provided URL via Playwright, systematically logging interactions with 3 to 5 core features, capturing both UI locators and expected outcomes for test case generation.

What are the limitations of browser automation for website flow discovery?

Website flow discovery via browser automation requires a supplied URL via Playwright MCP and closes the browser context after exploration, limiting its use to systematic interaction logging and test case proposal generation for 3 to 5 core features.