ui-test-puppeteer

name	ui-test-puppeteer
description	Use this skill when you need to design Puppeteer automation for Chromium-driven checks, screenshots, PDFs, network interception, and CDP use cases; triggers include Puppeteer UI testing, UI automation testing, and ui-test-puppeteer.

Puppeteer UI Testing (EN)

中文版： 见对应中文技能。

When to Use

• Need outputs that should land in a Puppeteer UI testing workflow.
• The project already uses Puppeteer or wants Puppeteer-ready planning.

Output Format Options

Markdown by default unless the request explicitly asks for another format.

How to Use

1. Open prompts/ui-test-puppeteer.md and use it as the main prompt.
2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
3. If the input is incomplete, return a usable first version and mark missing information and assumptions.

Reference Files

• prompts/ui-test-puppeteer.md: main prompt for this skill.
• references/framework-spec.md: tool-specific structure and coverage notes.
• references/setup-and-ci.md: setup, execution, and CI notes.
• examples/sample-context.md: sample request context.
• scripts/run-tests.sh: lightweight local execution entry point.

Common Pitfalls

• Do not use it with vague scope and no context.
• Do not treat every area as equally important.
• Do not skip assumptions and missing information.

Best Practices

• Start from the prompt file, then add only the context that matters.
• Keep the output risk-driven and executable.
• If the request is incomplete, return a usable first version and mark gaps.