gmira-verify

Execute Playwright audits across five viewports to detect layout, accessibility, and performance regressions.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/OthmanAdi/gmira --skill gmira-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmira-verify
Source: https://github.com/OthmanAdi/gmira/tree/main/skills/gmira-verify
Command: npx skills add https://github.com/OthmanAdi/gmira --skill gmira-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, playwright-core, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of inconsistent, unverified, and poorly performing web interfaces by enforcing a strict, multi-viewport audit process that catches regressions before they reach the user.

Core Features & Use Cases

  • Multi-Viewport Audit: Automatically captures screenshots and collects console errors, contrast failures, and layout issues across five critical device sizes.
  • Mechanical & Manual Checks: Combines automated Playwright-driven data collection with mandatory manual verification steps like keyboard navigation and canvas-deleted testing.
  • Use Case: Use this before deploying any new web surface to ensure that your design direction is maintained, accessibility standards are met, and GPU-intensive effects do not leak memory or fail on specific viewports.

Quick Start

Run the gmira-verify skill against your local development server at http://localhost:3000/route to generate a full audit report and screenshot set.

Frequently Asked Questions about gmira-verify

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

FAQPage Schema
How do I automate web accessibility and layout audits across multiple viewports with Playwright?

Multi-viewport audits capture screenshots and collect console errors across five critical device sizes to detect layout and accessibility regressions. They combine automated Playwright-driven data collection with mandatory manual verification steps like keyboard navigation testing.

How do I detect GPU performance regressions and memory leaks in my frontend application?

To detect GPU performance regressions and memory leaks, you execute automated Playwright audits against your local development server. This validates that GPU-intensive effects do not leak memory and adhere to strict performance budgets across viewports.

Can I use Playwright to verify contrast ratios and monitor console errors during web testing?

Yes, Playwright can verify contrast ratios and monitor console errors during web testing. The automated audit process collects contrast failures and console errors alongside layout issues across five critical device sizes.

Does automated web testing replace manual keyboard-only accessibility checks?

Automated web testing does not replace manual keyboard-only accessibility checks. The audit process combines automated Playwright-driven data collection with mandatory manual verification steps to ensure strict adherence to accessibility standards.

How do I validate adherence to design contracts before deploying a new web surface?

You validate adherence to design contracts by running a multi-viewport audit process against your local development server. This generates a full audit report and screenshot set to catch any visual or performance regressions before deployment.