qa-element-extraction

Extract UI element screenshots with Playwright and organize them in a visual glossary.

14|1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/jpoutrin/product-forge --skill qa-element-extraction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-element-extraction
Source: https://github.com/jpoutrin/product-forge/tree/main/plugins/product-design/skills/qa-element-extraction
Command: npx skills add https://github.com/jpoutrin/product-forge --skill qa-element-extraction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves?

Providing clear visual references for UI elements in QA test steps is essential for unambiguous testing, but manually capturing and organizing these can be tedious and inconsistent. This Skill automates the extraction and capture of specific UI element screenshots.

Core Features & Use Cases

  • Element Screenshot Directory: Standardized directory structure (qa-tests/screenshots/{test-id}/elements/) for organizing extracted UI elements.
  • Element Extraction Process: Identifies actionable elements from test steps, uses Playwright to locate and capture specific UI elements.
  • Screenshot Specifications: Defines image requirements (format, padding, background, state) and capture states (default, hover, focus, disabled).
  • Element Reference Table: Generates a visual reference table in the test procedure, linking elements to their screenshots and selectors.
  • Playwright Commands: Provides specific Playwright commands for capturing elements by role, name, text content, or test ID.
  • Use Case: Generating visual references for a new QA test procedure, capturing screenshots of specific buttons or input fields, building a reusable UI element glossary, or integrating element extraction into an automated testing workflow.

Quick Start

Use the qa-element-extraction skill to generate Playwright code to capture a screenshot of a 'Login button' by its accessible name.

Frequently Asked Questions about qa-element-extraction

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

FAQPage Schema
How do I capture screenshots of specific UI elements for QA test documentation?

Capture screenshots of UI elements by using Playwright to locate and extract targeted components like buttons, fields, and checkboxes, then save them as PNG images with standardized padding and dimensions to a qa-tests directory for visual test references.

What's the best way to create a visual glossary of UI elements for testing procedures?

Extract actionable elements from test steps using pattern-based detection and Playwright, capture them in multiple states (default, hover, focus, disabled), and assemble a standardized element reference table linking screenshots to selectors within your test documentation.

Can I automate UI element screenshot collection in Playwright-based tests?

Yes. Automate element extraction by identifying UI components through accessible names, roles, text content, or test IDs, then use Playwright commands to capture and organize screenshots with enforced specifications like 8-16px padding and 400px max width.

How do I organize extracted UI element screenshots for reproducible QA artifacts?

Use a standardized directory structure (qa-tests/screenshots/{test-id}/elements/) to store element screenshots with consistent naming conventions, making visual references reusable across test procedures and maintainable for long-term QA documentation.

Do I need Playwright to extract and document UI elements for QA tests?

Playwright is the extraction mechanism used to locate and capture specific UI elements by role, name, or selector. It enables precise targeting and automation of element screenshot capture within the qa-tests workflow.