ui-delivery

Automate UI delivery verification with Playwright-driven visual, accessibility, and QA checks.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/mmcmedia/openclaw-agents --skill ui-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-delivery
Source: https://github.com/mmcmedia/openclaw-agents/tree/main/skills/ui-delivery
Command: npx skills add https://github.com/mmcmedia/openclaw-agents --skill ui-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI delivery and verification often lack a standardized, repeatable process, leading to inconsistent quality, missed accessibility issues, and late discovery of defects. This Skill provides a structured protocol to ensure visual checks, console health, builds, accessibility, QA gates, and adversarial reviews are completed before delivery.

Core Features & Use Cases

  • Visual verification across mobile, tablet, and desktop breakpoints using Playwright-driven screenshots.
  • Automated console/error monitoring with explicit guidance on which issues block delivery and how to document exceptions.
  • Build verification and automated accessibility checks to catch regressions before merge.
  • QA Gate and Adversarial Review workflows that certify readiness for delivery and provide a remediation path when issues are found.
  • Clear completion templates, artifact guidance, and a reusable completion message for traceability.

Quick Start

Use the UI delivery protocol to standardize UI verification and ensure consistent quality before PR merge.

Frequently Asked Questions about ui-delivery

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

FAQPage Schema
How do I automate UI delivery verification with Playwright before merging?

Set up a standardized UI delivery pipeline that enforces mandatory checks including visual verification, console cleanup, zero critical accessibility violations, successful builds, QA gating, and adversarial reviews before certifying a release.

How does automated accessibility testing fit into the UI delivery pipeline?

Console error monitoring identifies blocking issues that halt delivery, requiring explicit remediation or documented exceptions before the UI delivery pipeline can advance to the QA gate certification stage.

Can I use this UI delivery protocol for responsive web projects across different breakpoints?

The pipeline produces traceability artifacts, completion templates, and a standardized completion message that certify the UI passed visual checks, accessibility scans, QA gating, and adversarial reviews.

What happens if the QA gate or adversarial review finds issues during UI verification?

When the QA gate or adversarial review identifies issues, the pipeline provides a structured remediation path, blocking delivery until the defects are resolved and all mandatory verification checks pass successfully.