mozart-fe-validation

Automate frontend validation with disposable Playwright scripts and audit artifacts.

5|1|Updated Nov 4, 2015
One-click install
npx skills add https://github.com/samjonester/dotfiles --skill mozart-fe-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mozart-fe-validation
Source: https://github.com/samjonester/dotfiles/tree/main/personal/pi/skills/mozart-fe-validation
Command: npx skills add https://github.com/samjonester/dotfiles --skill mozart-fe-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validations for frontend/UI changes with disposable Playwright scripts generate human-auditable artifacts (screenshots, ARIA snapshots, logs) to support reproducible PR reviews.

Core Features & Use Cases

  • Disposable Playwright validation scripts (tmp/validate-*.ts) generate verifiable artifacts.
  • Preflight checks, deterministic data seeding, and PR-ready validation steps.
  • Artifacts include screenshots, ARIA snapshots, and logs for audit and debugging.

Quick Start

Run the disposable Playwright validation workflow to generate artifacts and logs for frontend changes.

Frequently Asked Questions about mozart-fe-validation

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

FAQPage Schema
How do I automate frontend validation with disposable Playwright scripts?

Automate frontend validation by running disposable Playwright scripts stored in tmp/validate-*.ts that execute preflight checks, seed data, and capture screenshots with ARIA snapshots for reproducible PR reviews.

What are ARIA snapshots and screenshots used for in UI validation?

ARIA snapshots and screenshots are human-auditable artifacts generated during frontend validation to support debugging and verify UI changes across preflight, seed, run, and report phases.

How do I generate PR-ready descriptions for frontend UI changes?

Generate PR-ready descriptions by executing a validation workflow that produces explicit validation steps and auditable artifacts, ensuring reproducible reviews for frontend UI updates.

Can I run disposable validation scripts without configuring a base URL?

Disposable validation scripts use a default BASE_URL and ignoreHTTPS settings to streamline execution, requiring no manual configuration to run preflight checks and capture artifacts.

What's the best way to ensure reproducible automated testing for PR reviews?

Ensure reproducible automated testing by generating deterministic data seeding and verifiable artifacts like screenshots and logs through disposable scripts designed for PR validation guidance.